Trash doesn't work on NFS mounted partitions

Bug #1035843 reported by Victor Engmark
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Low
Unassigned

Bug Description

As reported elsewhere <http://askubuntu.com/questions/172620/how-to-enable-trash-for-nfs-mounts>:

The /home/users directory on my host is an NFS mount connected to a server which is not in my control. When deleting files in $HOME (/home/users/foo) with Nautilus I get the following message:

    Cannot move file to trash, do you want to delete immediately?

    The file "..." cannot be moved to the trash.

Is there some way to enable trash for this mount point? I have write access to the partition, but even after creating the expected /home/users/.Trash-$(id -u) and setting the sticky bit, Nautilus still fails to use the trash.

When reading this question <http://askubuntu.com/questions/27176/how-does-the-trash-can-work-and-where-can-i-find-official-documentation-refer> and the Trash Specification <http://www.ramendik.ru/docs/trashspec.html> I found that $HOME/.local/share/Trash is the standard location (unless $XDG_DATA_HOME is set), and it looks like Nautilus is only half-aware of this: It does indeed write a $HOME/.local/share/Trash/info/[filename]<.number>.trashinfo every time I try to delete a file, but the files are all empty and I still keep getting the error message.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-applets (not installed)
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Sun Aug 12 12:12:47 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: gnome-applets
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Victor Engmark (victor-engmark) wrote :
Revision history for this message
Stéphane Gourichon (stephane-gourichon-lpad) wrote :

Thank you for submitting this bug.

Can you please read http://ubuntuforums.org/showthread.php?t=1996729 and tell if, as written there, "the user does not have permission to access to the root of the partition that is mounted" ?

Then please update this bug accordingly.

Thank you.

Revision history for this message
Victor Engmark (victor-engmark) wrote :

The user does not have access to write to the root of the partition, but it does have read access to the root (obviously) and write access to $HOME/.local/share/Trash and $HOME/.local/share/Trash/info/[filename]<.number>.trashinfo, as mentioned. But why should this matter? A normal user doesn't need access to the root directory of the local root partition to use trash properly.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-applets (Ubuntu):
status: New → Confirmed
Revision history for this message
Julien (jlab) wrote :

Hi,

I have a Seagate Blackarmor NAS that I used to access via NFS. I think I have the same problem.

For a while the trash worked fine. But with upgrades I get now an error message when I try to move a file to the trash :
"Impossible to find or create the directory trash directory for /mountpoint/file"

The mountpoint is not in my home directory. I use NFS version 3 (the NAS doesn't accept NFS v. 4). I can create files and dirs. The problem is only with the trash.

It's strange because the trash worked previously with older Ubuntu release (I'm now on Ubuntu Gnome 16.10, I don't remember since when the trash doesn't work).

Regards, Julien.

affects: gnome-applets (Ubuntu) → nautilus (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

Is that still an issue in newer Ubuntu versions?

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
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.