When trying to manage trash can from mounted NTFS volumes, I ended up reading FreeDesktop.org's reference on it.
Poking around and doing some tests, I realized Ubuntu/Gnome does not follow the specs 100%. Here's why:
For non-/ partitions, it always uses
<driveroot>/.Trash-<uid>, It never used
<driveroot>/.Trash/<uid>, even when i created it in advance. While this works, it's annoying: if I have 15 users, I end up with 15
/.Trash-xxxfolders in my drive, while the other approach would still give a single folder (with 15 sub-folders). That "pollution" in my drives is very unpleasant. And specs say "If an
$topdir/.Trashdirectory is absent, an
$topdir/.Trash-$uiddirectory is to be used". Well, it is present, so why does it never use it?
root trash does not work, at least not out of the box. Open nautilus as root and click on trash; it gives an error. Try to delete any file, it says "it can't move to trash". Ok, I know this can be fixed by creating
/root/.local/share. But specs says "A “home trash” directory SHOULD be automatically created for any new user. If this directory is needed for a trashing operation but does not exist, the implementation SHOULD automatically create it, without any warnings or delays.". Why the error then? Bug?
Why must I change
/etc/fstabentries for mounted volumes, adding options like uid and guid, if the volumes are already mounted as RW for everyone?
These are just some examples of deviation from the standard. So, the question is:
"If Ubuntu does not adhere 100% to the spec, HOW exactly does the trash work? WHERE can i find a technical reference for Ubuntu's implementation of the trash?"
By the way: if Ubuntu does happen to follow specs, please tell me what I am doing wrong, especially regarding the
Some more info:
If a given fs has no support for the sticky bit (VFAT, NTFS), it probably doesn't have for permissions either (at least VFAT surely doesn't). So what prevents one user from purging
/restoring other users'
./Trash-xxx? If one can read/write his own Trash, one can do the same for the whole drive, including other's trashes, correct? Or does Gnome have some kind of "extra" protection on
./Trash-xxxfolders on VFAT/NTFS fs?
If Linux can "emulate" file permissions on NTFS mounting by editing
/fstabuid and gid options, can it also "emulate" the sticky bit? I would really prefer to use
For the root issue: for the / partition, I can use trash as root, and it goes to
/root/.local/share/Trash. But if I click on Nautilus "Trash" (as root), I get an error. Don't you? So files are correctly trashed, but I can't access it. All I can do is manually "purge" them (by deleting files on
/root/.local/share/Trash), but restoring would be very tricky (opening info files and manually moving, etc.).
For non-/ partitions (or at least for VFAT/NTFS), I can not even use trash as root: it does not create a
./Trash-0folder, it simply says "Cannot trash, want to permanently delete?" Why?
About fstab: i use it for a permanent mount for my NTFS partitions. I have several, and if not "pre-mounted" they really clutter the desktop and/or Nautilus. I'd rather have it pre-mounted, integrated in my file system, in mounts like
/windows/vista, and so on, and leave
/mediaand its "mount/unmount" flexibility just for truly removable drives.
So, if Ubuntu/Gnome truly follows the spec, is there any way to fix the root issues and to "emulate" the sticky bit for (at least) my fstab'ed NTFS fixed partitions?