OK, sorry, there's more specificity to this experience: Basically, there is a separate filesystem mounted at /var/tmp
The nautilus Trash can does what you would expect with files that end up in /home/user/.local/share/Trash The nautilus Trash successfully moves files to, but CANNOT DISPLAY OR DELETE files that end up in, /var/tmp/.Trash-1001 ------------------------ There's another (tiny) filesystem mounted at /boot/grub. Further experimentation shows that if the permissions are set appropriately, nautilus can deal with files in /boot/grub/.Trash-1001 the way it's supposed to. By the way, nautilus has been running from a terminal window this whole time, and the only visible error message is ** (nautilus:4105): WARNING **: Unable to add monitor: Not supported which must be irrelevant, but by its lonely presence it implies that no other error messages are being generated. So, why would nautilus be able to move files to a .Trash-*/files folder but not display or delete them afterwards, and why would these particular functions work on some filesystems and not others. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
