Whole PC locks up, and in one instance crashed Cinnamon, when trashing a large number of files

[LinuxOnTheDesktop]

 * Nemo version (nemo --version): 5.4.3
 * Is issue with desktop or windowed nemo? Windowed
 * Distribution - (Mint 17.2, Arch, Fedora 25, etc...) Mint 21 Cinnamon
 * Graphics hardware *and* driver used: Intel; Mesa
 * 32 or 64 bit: 64. [Shouldn't this field be removed? _Is_ there a x32 Nemo an more?]

Issue

When deleting - specifically: moving-to-the-bin - some five-hundred (500) small files, Nemo does not respond, in no (other) way indicates busyness, and the whole system locks up: keyboard shortcuts don't work, panels don't work, the mouse can move but no do anything. However, deletion does seem to be in progress, judging by the hard drive light on one of the two PCs that I have that are affected by this (those two PCs both running the same version of Nemo - and one of them is a fast computer: it has an i7 quadCore, 16GB RAM, and nvme). (I can't judge busyness by anything other than that hard drive light because I can't even see my conky - because the conky is behind the unbudging Nemo window.)

This hang has been going on now for some five minutes. Update: on the fast computer (though it was running on battery), the deletion ended, after some ten minutes, with a Cinnamon-crash-to-fallback; on the slower computer, the deletion ended successfully after approximately the same amount of time.

Steps to reproduce

I don't want to lock up my PC again, so I haven't tested reproducibility except in this way: on the aforementioned two PCs, I deleted some 700 files, on each, from /home/<me>/.config/session. Also, I recall the problem from the past.

Expected behaviour

Some indication of busyness, and also no system lock-up.

Other information

I thought there was an issue open on this already, but if there is, I could not find it.

[mtwebster]

Is is possible one or more of the files were in use while you tried to delete them? I have that folder as well (~/.config/session) but the only thing in it is a few of kolourpaint files.

Anything in ~/.xsession-errors?

Any crash info in System Reports?

btw, LMDE still has a 32 bit edition.

[LinuxOnTheDesktop]

Thanks.

~/.xsession-errors, and .xsession-errors.old: there is nothing relevant in there now, but perhaps I have left it too long.

System Reports: nothing there, but on my machines there hardly ever is, even after a crash. Perhaps I have something misconfigured.

Files being in use: I don't know - perhaps. Let's suppose some file(s)-to-be-deleted was indeed open. That should not lead to the results that I described - though possibly the result might have have owed to an Okular process rather than to a Nemo process. (Okular seemed to be the source of many of the files that I was deleting.)

LMDE having a 32-bit version: right.

[LinuxOnTheDesktop]

Actually, I found a crash report. Indeed, I found three, but all of them from the slower computer - which seemed to hang but not actually crash. One report is from the day that I had the problem. (On that day I had the problem on both PCs.) The other two reports are not. All of the reports are about SublimeText.

I have uploaded one of the reports here. The problem does indeed seem to have to do with deleting open files - but I am unsure that I was deleting the files of which the crash report complains.

[MegaV0lt]

Same issue here. After deleting 1300 small icons to trash nemo hangs and only way to recover was to do Ctrrl-F1 and sudo reboot

[Ticonderoga]

Same here. I found an issue with gfvs. Using journalctl to see what's going on ?

$ journactl -r

and I end with hundred of lines like this :

juin 16 16:42:20 Fanfulla gvfsd[1565]: Error calling org.gtk.vfs.MonitorClient.Changed(): Le délai d’attente est dépassé (g-io-error-quark, 24)

and I tried to clean my Trash from the terminal but it doesn't work. I found similar problems

https://gitlab.gnome.org/GNOME/gvfs/-/issues/416 https://forum.manjaro.org/t/brand-new-install-of-xfce-manjaro-gvfsd-1273-crashes-causing-desktop-freeze/85360 https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1239014 https://askubuntu.com/questions/362889/error-calling-startservicebyname-for-org-gtk-vfs-daemon-timeout-was-reached-g https://forum.manjaro.org/t/gvfsd-2588-error-calling-org-gtk-vfs-monitorclient-changed-timeout-was-reached-g-io-error-quark-24/63011

but no real solution yet.