GNOME Bugzilla – Bug 655529
Nautilus cannot change trash location
Last modified: 2013-04-01 01:35:58 UTC
I have a SSD and a RAID0 composed of 2 harddisks (mounted on /data, for the following description). On the RAID0, I have all my photos. When I delete a photo, it is moved to trash. No bug so far. As the SSD wears quickly while copying the files to it and as moving would be much quicker, I wanted to put my trash on the RAID0. I created a link from ~/.local/share/Trash to /data/Trash. Now, when trying to delete a file (for example named xyz), I get a dialog with the message "Cannot move file to trash, do you want to delete immediately?" and "The file "xyz" cannot be moved to the trash." No reason is indicated (already a bug for itself, in my eyes). It's not a problem related to the access rights. I also tried to mount the Trash directory on ~/.local/share/Trash with option --bind. The error message is the same. I consider this to be a bug. Nautilus is able to do this on USB sticks etc., so why not on a partition mounted during boot? As well, it is common in Unix to solve such location problems with links and that should be understood by Nautilus (especially, as the delete operation would result in a "cheap" move instead of an "expensive" copy. And: This bug really causes problems to all users who have a rather small SSD boot device and HDD data devices. The SSD wears quickly. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Tue Jul 26 20:31:17 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to natty on 2011-06-03 (52 days ago)
The trash spec (http://www.ramendik.ru/docs/trashspec.html) says: "It may also choose to provide trashing in the “top directories” of some or all mounted resources. This trashing is done in two ways, described below as (1) and (2)... (1) An administrator can create an $topdir/.Trash directory. The permissions on this directories should permit all users who can trash files at all to write in it.; and the “sticky bit” in the permissions must be set, if the file system supports it. (2) If an $topdir/.Trash directory is absent, an $topdir/.Trash-$uid directory is to be used as the user's trash directory for this device/partition. $uid is the user's numeric identifier." Does that work and solve the problem?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!