ParaDice wrote:Most of my efforts to stop it following your tips have failed, though
Quite unsurprised; GVFS is a disaster generally, and an unmitigated one wrt. both configuration and debugging. I could get you one heck of a rant concerning that... but let's not for now, since...
[*] While Cinnamon was frozen, I ran htop from the TTY and got this twice at or near the top of my process list:
Code: Select all
/usr/lib/gvfs/gvfsd-trash --spawner :1.17 /org/gtk/gvfs/exec_spaw/0
... we may have an opportunity to fix things first: this seems to point to the Trash component of GVFS, not a thumbnailer. Do you have a particularly large .Trash-0 folder inside of the root of the mounted filesystems? Note the leading period: it/they would be hidden from normal view; in Nemo you use Ctrl-H to show hidden files, from the terminal
Even if they're not large some may be damaged. You are mounting as root so are primarily looking for .Trash-0 folders it seems; I don't believe other Trash-$(id -u) folders should be involved but if there's no .Trash-0 folders but .Trash-1000 folders, say, also be suspicious of those. You mounting as root also means you won't be able to empty them by "Empty Trash" as your regular user: you can probably open a Nemo window "as root" and do it from there but if you're sure there's nothing in the Trash on a particular filesystem that you may still want to retrieve,
sudo rm -rf /mnt/your/local/dir/.Trash-*
certainly empties it. The folders are automatically recreated when needed.
Added up, these processes use only 25% of my CPU and 10% of my memory, which should hardly be enough to make Cinnamon freeze.
Perhaps not, but add in GVFS and CIFS and it wouldn't surprise me in the slightest in the "Death from I/O" sense. That would've been part of the rant...
[EDIT] Throwing away, commenting out the Exec= line of, or changing the "AutoMount=True" to "AutoMount=false" in, the file /usr/share/gvfs/mounts/trash.mount (the path in 17.3; may differ in 18) and rebooting may also be useful. This would of course have an effect on all of GVFS' Trash handling; you may not want to do so. Rare enough to seemingly have found a bit of GVFS configuration to still warrant an [EDIT] though.