First, a work-around: create a folder named '.Trash' with permissions 1777 in the remote folder you're mounting.
However, this doesn't work in my case. A bit more detail: I have a desktop called mabelode and a server called tanelorn. On my Nautilus desktop (the same as my home folder) I have: - a folder called ~/mountpoints - inside this I have an empty set of directories following ~/mountpoints/tanelorn/mnt/corum - a symlink called ~/corum to ~/mountpoints/tanelorn/mnt/corum On tanelorn there's a foldern /mnt/corum, which has a filesystem mounted on it. Both tanelorn:/ and tanelorn:/mnt/corum contain a folder named .Trash, owned by root:root with permissions 1777. My username and uid is the same on both machines. If I use “sshfs -o reconnect,transform_symlinks,allow_other,nonempty,fsname='sshfs#tanelorn:/mnt/corum' tanelorn:/mnt/corum ~mountpoints/tanelorn/mnt/corum” — that is, mount directly the mount-point on the server to the equivalent mount-point on my desktop — then trash works: the folder tanelorn:/media/corum/.Trash is recognized, Nautilus creates a folder called '1000' (my uid on both machines) inside it, and puts trashed files in there. However, if I use “sshfs -o reconnect,transform_symlinks,allow_other,nonempty,fsname='sshfs#tanelorn:/' tanelorn:/ ~mountpoints/tanelorn/” — that is, mount the root of the server rather than a mountpoint on it — then: (a) trash works for files that are on the server's root filesystem, but (b) it doesn't work for files on other of the server's filesystems. Presumably, Nautilus uses a 'move' command that only works inside a filesystem. In the second case, since all of the server's filesystems are accessed through the same sshfs mountpoint, Nautilus can't figure out that they're actually different, and doesn't try to use their respective .Trash folders. I'm not aware of any work-around for this situation, other than mounting each of the server's mount points separately. -- fail to delete directory over sshfs with nautilus https://bugs.launchpad.net/bugs/371289 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
