Gnome Nautilus cannot change trash location

Bug #816600 reported by Murrsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Medium
nautilus (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

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 problems with links and 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 HD 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)

Revision history for this message
Murrsky (murrsky) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this at https://wiki.ubuntu.com/Bugs/Upstream/GNOME . Thanks in advance!

Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
Murrsky (murrsky) wrote :

Ok, I posted this also on bugzilla.gnome.org (bug 655529).

Changed in nautilus (Ubuntu):
status: New → Triaged
importance: Low → Wishlist
Changed in nautilus:
importance: Unknown → Medium
status: Unknown → New
Changed in nautilus:
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream comment

"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?"

Revision history for this message
Murrsky (murrsky) wrote :

Well, the Nautilus version I currently use (3.4.2 on Ubuntu 12.04) seems to do this. Deleted files are moved to
$topdir/.Trash-$uid

So, the problem seems to be solved.

Changed in nautilus:
status: Incomplete → Expired
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thanks, closing.

Changed in nautilus (Ubuntu):
importance: Wishlist → Critical
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.