GNOME Trash doesn't show deleted files on other partitions (ecryptfs / encfs / Private / ntfs-3g)

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

No, this bug hasn't already reported at least in the duplicate bug. On ntfs-3g partitions the files aren't shown at all even if you open the trash manual. The other one (External disk trash not shown by trash applet) is a gui bug but this one seems to be deeper. I guess that Gnome doesn't expect writing support for ntfs but I don't know. Please reopen it or at least check it with an ntfs-3g partition.

This doesn't seem to be a duplicate of bug #32466. There, the files can be found in trash:// - this is not the case here.

Reopening then. The desktop team is overworked at the moment though and ntfs-3g is not current so it bug is low importance

"ntfs-3g is not common"

I don't know what exactly you mean by "not common" but ntfs-3g upstream is buried by all short of Ubuntu specific bug reports for quite long time. If NTFS support is a low priority for Ubuntu then would you please make an official statement somewhere we could point people, so they won't have false expectations. Thank you.

ntfs-3g is distributed to universe at the moment, it's not on the default installation, that doesn't mean we don't want to get bug worked, the desktop team is small though and already has lot to do, you or upstream are welcome to contribute to get that corrected if you know what to change though

I think you are right and people can live with it until Gutsy if it is mentioned somewhere in Wiki. But could you please confirm the bug so it doesn't get lost or is it then a problem for Feisty release?
Anyway I guess that ntfs-3g would be main in Gutsy so it gets more important and btw. thanks for reopening.

no, I've no NTFS volume to test it and I don't know how to use ntfs-3g, the bug should be confirmed by somebody getting it

It's very simple to test, if one is familiar a bit with the command line. No need for existing NTFS or Windows:
http://ntfs-3g.org/quality.html#howtotest

The mount type is a fuse one, there is a bug upstream:http://bugzilla.gnome.org/show_bug.cgi?id=349622

Depending on the kernel version and other issues, the file system type (fstype) can be: fuse, fuseblk, fuse.<userfs> and fuseblk.<userfs>, where <userfs> is FUSE file system type, e.g. ntfs-3g.

The <userfs> sub part of the fstype should stay in the future but it's not available yet in stable Linux kernels, only in Linus' development tree. This FUSE feature was added recently to help the identification of the user space fstype by e.g. mount helpers and make its detection independent of FUSE's internal evolution, e.g. the introduction of the new, additional fuseblk FUSE fstype which was required for safe block devices support.

In fact I suspect that the real problem is that that only the fuse fstype is supported, not yet the others. kernel 2.6.20 introduced fuseblk and 2.6.21 wiwll introduce {fuse,fuseblk}.subfstype.

http://bugzilla.gnome.org/attachment.cgi?id=86561&action=view was committed upstream.

I'm not sure the fix is correct, enough as I explained above. Or does it work with the fuseblk, fuseblk.ntfs-3g and fuse.ntfs-3g file system types too?

Would be nice to have some ntfs-3g upstream working with GNOME guys on it, or could you explain what those things are, how to configure them, etc?

From NTFS-3G upstream: the issue is not NTFS-3G but FUSE specific. I explained it at
https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/106621/comments/12
This should be enough for Gnome developers to make the changes to support all FUSE
file systems on all kernels. Thanks.

there is no 2.6.21 available to Ubuntu yet, look like something to work on later then

As https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/106621/comments/12 explained, kernel 2.6.20 introduced fuseblk and that 's what for example ntfs-3g uses mounting all internal and external disks. Afaik, Ubuntu 7.04 uses kernel 2.6.20, so the problem is not fixed.

I'm under Gutsy uptodate and i can't reproduce your bug.
If i delete files on my usb stick (ntfs), when i open trash (left click on trash applet), my files are shown.

Can you confirm that when you do that, your deleted files are not shown ?

I don't know if I have to fill another bug for that but under Gutsy Beta release, Files are shown if I open the trash, but the trayicon say that there isn't any file in the trash although there are.

I have the same problem on Btrfs,

I have the same problem.

I just deleted an item on my ntfs partition. I made a mistake and went to find it but couldn't find it anywhere. Finally i found this bug report and found it in .Trash-$user on the ntfs partition.

Was not listed in normal trash at all.

Now that ntfs-3g is by defaul in gutsy, I would say it will be *very* common.

I've no clue what reports I could post to assist. If someone lets me know, I'll try.

Gutsy is still not able to manage Trash-Folder on ntfs-3g/Fuse-Devices. I think this is important.

As unggnu commented in https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/140968/comments/5 , this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/140968 (or rather it's the same origin behind these 2 bugs).

I don't think fuse is the problem as, from what I saw, the filesystem is detected as ntfs in gnomevfs.

I explained the reason and gave patches in https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/140968/comments/4 and https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/140968/comments/3

I put fixed packages in my personal archive: http://ppa.launchpad.net/yann-pleiades/. Tests are welcome.

Yann,
I tested your gnome-vfs/nautilus packages from http://ppa.launchpad.net/yann-pleiades/ but sadly they don' t work as expected. When I login now there aren't any computer, home and trash folders on my desktop and deleting something from an NTFS volume now a warning appears telling me that the file can't be moved to trash, so it will be deleted.

Luca: are you sure you used last gnome-vfs packages (~ppa4) ?

Because it seems you got the nautilus fix (nautilus now correctly handles the fact that a filesystem doesn't support trash), but that NTFS trash usage is not enabled and I've enabled it in the ~ppa4 gnomevfs package.

I'm under Gutsy and i CAN reproduce the bug.

Same here. Gutsy 32 bits, files deleted in the NTFS partition do not appear in the Trash. Can someone try this on Gutsy with a FAT32 partition? Do not have any here, so cannot tell whether the bug is valid for that filesystem too.

Well, I tried it on a Gutsy with a FAT32 partition. It works fine. Since I converted it to NTSF I can reproduce the bug.

Well I can assure that the bug is not reproducibile with KDE 3.x - trash
management works fine there. One has to wonder then where the bug is,
whether in GNOME or ntfs-3g... :(

the conclusion: its a obviously a Gnome / Nautilus problem.

Yes it is, see https://bugs.edge.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/140968

obviously there are patches.

I just deleted a file from a FAT32 partition and a couple of files from an NTFS partition on Hardy Alpha 2, fully updated.

See the attached file - the file deleted from the FAT32 partition (test.txt) displays if the Trash is clicked, but the icon for the trash applet does not change and the files cannot be cleared by selecting right-click "Empty Trash" (it is inactive). The files deleted from NTFS have the same effect as the one deleted from the FAT32 partition, but they do not even show when the Trash icon is clicked.

Should the description for this bug be changed to reflect that it applies to more than just NTFS-3G, or do the problems with other filesystems belong in separate bugs?

have the same issue here. My ntfs partition is my main data partition (my work there is shared with my windows partition).

choosing file -> empty trash in nautilus wont empty my ntfs trash

It seems to be fixed in Hardy since files aren't moved to Trash anymore on NTFS partitions and Gnome shows an extra warning.

so, they fixed the bug eliminating the feature?

Is it a try to convince me to swith back to windows?

Well, they did not technically eliminate the feature...rather they
implemented it in a different way. But for the end user you are right:
unless you know what to do, you're pretty much stuck.
Could someone modify the ntfs-3g package so that the hack is directly
implemented when the fstab is written?

Paulo Pontes ha scritto:
> so, they fixed the bug eliminating the feature?
>
> Is it a try to convince me to swith back to windows?
>

> Is it a try to convince me to swith back to windows?

you are welcome to use whatever os you want, such comments are not really useful there though

> Could someone modify the ntfs-3g package so that the hack is directly
> implemented when the fstab is written?

Sadly we can not do anything in NTFS-3G because, as it was earlier
explained and patches submitted, this is not an NTFS-3G bug but a Gnome
one. When it's possible we always workaround in bugs in applications but
I'm sorry to say, we can't do it this time.

We also think it's fairly unfortunate how Gnome works because it's not the
behavior many Ubuntu users expect and they do keep losing files because
of this.

Regards, Szaka

==
NTFS-3G Lead Developer: http://ntfs-3g.org

why would users delete files exactly? when there is no trash available nautilus display a dialog explaining that and ask for confirmation to the users

> why would users delete files exactly? when there is no trash
> available nautilus display a dialog explaining that and ask for
> confirmation to the users

By accident. Childen. Elder people. Users who think they can recover
from the Trash if they still change their mind. Software bugs. Hung
then recovered X/OS/etc and when people desperately hitting/clicking
everything to happen something during the temporary freeze time.
People in hurry. People in panic. Visually impaired people. And so on.

let's stop this discussion there, those comments are not constructive there is no reason that software bugs should trigger there, the bug is about user interactions, there is also no reason that people should not be able to read the delete confirmation dialog if they know enough to use a computer and gnome-vfs is not used in hardy by nautilus anyway

closing this bug it's obsolete now than gvfs is used in GNOME

This is still broken with gvfs. I can confirm it on Intrepid with the new ~/Private directory. Anything you trash under ~/Private is properly put into ~/Private/.Trash-$UID, but it does not show up in Nautilus's trash. This bug may be in the gvfs package rather than nautilus, but since I'm seeing it in Nautilus, let's start there.

Upstream is thinking this is gvfs.

Adding ecryptfs-utils for tracking purposes, since we've gotten a few reports.

:-Dustin

the corresponding code has been rewritten in jaunty, could you try if that's still an issue?

did anybody try on jaunty?

In jaunty a dialog box pops out telling me that the file can't be moved to trash and asking if I want to delete it instead. I'm testing an ntfs-3g partition on a external usb disk.

I'm running with my entire home directory encrypted (ecryptfs)

I created a new file using Nautilus. Saved that file. Deleted that
file. It was successfully deleted, and did not go to my Trash bin.

:-Dustin

I commented on the upstream bug report saying that this is still an issue with the latest trash backend in Jaunty now.

Confirming a similar problem on Ubuntu Jaunty amd64:

The user with encrypted (ecryptfs) home directory can successfully "delete" files in his home directory in Nautilus and these appear in his Trash.

However, deleting files outside of the encrypted home directory (but on same partition with ext3), a message that the file cannot be moved to Trash appears as reported by Luca Cavalli on 27 Feb 2009.

A use case for me is that I have a separate "public" directory with photos - these are not encrypted and are writeable to selected users. A user without encrypted home directory can "delete" the files to Trash successfully.

I'm having the same problem on Ubuntu Jaunty.
I have an ecryptfs mounted on ~/Private . When I delete an encrypted file it is moved in to the trash but it won't show up in Gnome Trash so it took me an hour to figure it out when I wanted to recover it...

FYI, KDE applications seem to work correctly when deleting files outside of encrypted home directory but on the same disk partition (in opposite to Nautilus and other Gnome apps as reported earlier by me https://bugs.launchpad.net/gvfs/+bug/106621/comments/53 ) and move the files to Trash (and these are then visible also in Gnome Trash). In particular, digiKam and dolphin work fine.

This particular bug looks a bit different to what was reported originally, should I open a new one?

hi folks, just wondering if this will be fixed in karmic? i use ecryptfs and encfs a lot so this is quite important

From an eCryptfs perspective, this is a limitation of using Encrypted-Private, rather than Encrypted-Home.

In both Jaunty and Karmic, you now have the ability to encrypt your entire home directory, which includes your Trash folder. Thus you can protect your Trash through Encrypted-Home.

Truly, the Encrypted-Home feature was developed to handle situations like this, where users had to painstakingly identify what was to be marked Private.

I'm switching the ecryptfs-utils task from invalid to wont-fix, since there's a viable, well-supported alternative.

:-Dustin

Confirmed for ecryptfs on Maverick.

Same problem with Oneiric and encrypted ~/Private (this is quite common setup I guess).

find ~/Private/.Trash-1000/
show deleted files after emptying trash

Sorry, I'm lost here: I still see the bug in Nautilus 3.20.4. Is it supposed to be fixed ?