nautilus should not create a "trash" folder on removable media

Bug #14551 reported by Adam Lydick on 2005-03-26
8
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Medium
Sebastien Bacher

Bug Description

I filed a debian[1] bug on this issue a while back and upstream is also aware of
the issue[2], but I wanted to raise it again before hoary releases because I
think it causes some fairly serious usability problems WRT devices that appear
as USB drives. It is actually a bit worse than previously reported, as (1)
emptying the only visible "trash" (on the panel) has no effect on that of the
mounted drive and (2) you have to know that there is a hidden ".user-trash"
directory to ever find it. This seems very unlikely to be discovered without
prompting.

Severity is "minor" for me (easy workaround), but "major" for anyone who doesn't
understand how trash works in nautilus (eg: my archetypical grandmother).

I imagine this would be a fairly simple fix (special-case removable media the
same way network drives are, this is done already by the volume manager which
mounts it with synchronous I/O).

=== Original bug report follows

Nautilus does not create .trash-<username> folders on network drives,
but it does on removable media. This is somewhat annoying when working
with portable media players, usb-drives, etc because I need to locate
and delete the .trash folder at the root of the drive after removing
files.

I suspect this would be quite confusing to a novice. It took me a few
moments to figure out why my drive was still full after deleting all of
the media files on the device.

Suggested behavior:
Treat removable media like remote drives and delete file permanently.

=== References

[1]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277482
[2]http://bugzilla.gnome.org/show_bug.cgi?id=138058

http://bugzilla.gnome.org/show_bug.cgi?id=138058: http://bugzilla.gnome.org/show_bug.cgi?id=138058

Sebastien Bacher (seb128) wrote :

right, that's a known upstream bug. I'm not sure of the best way to fix that,
should probably be discussed upstream.

Daniel Robitaille (robitaille) wrote :

This bug has been marked as a duplicate of bug 12893.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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