GNOME Bugzilla – Bug 157259
Semi-functional trash with homedir in trash-less filesystem
Last modified: 2008-02-03 20:37:55 UTC
1. Start GNOME 2.8 with homedir in AFS. 2. Move a file into the wastebasket. The wastebasket is still empty, but the file is in ~/.Trash. If I enable trash on AFS in gnome-vfs/libgnomevfs/gnome-vfs-filesystem-type.c, the wastebasket works as expected. I suppose the wastebasket should either ask to delete files, or perhaps not be visible at all, if the homedir is in a trashless filesystem. (I will file another bug about enabling trash on AFS.)
Thanks for your bug report! Can you still reproduce this behavior? I've not yet come across that file system, but at least for my trash-less sftp mount, nautilus 2.10 informs me that the file can't be moved to trash and offers me the delete operation.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Christian asked for. Thanks!
I'm sorry about this late comment. I've reproduced this behavior on Fedora Core 5 (gnome-vfs2-2.14.2, nautilus-2.14.1). To reproduce this, I think you need to have the home directory in a trash-less filesystem.
The problem happens on local filesystems which should not support trashing. The reason is that gnomevfs uses a table which says if a filesystem can use a trash or not. As Alexander Bostrom said, it is located in gnome-vfs/libgnomevfs/gnome-vfs-filesystem-type.c, it's the fs_data structure. However this information is not always used and for example Nautilus will not test if the filesystem support trashing and will happily create a Trash and move files in Trash on a filesystem which is not supposed to support it. This lead to this following bug and also this one: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/140968
Created attachment 97526 [details] [review] Test if a filesystem support trash before using it Add the missing test in Nautilus so Trash is not used if the filesystem doesn't support it.
gnome 2.22 will not use gnome-vfs anymore and has a completely rewritten implementation of this (gio/gvfs).
Closing this because it's gnome-vfs related. Please test it with the new gio/gvfs implementation and then you can reopen it.