nautilus takes long time to move to rubbish bin on Kerberos/NFS4 fileshare

[Mark Dickie]

I have an Ubuntu 12.04 LTS server providing NFS home shares for a few Ubuntu 13.10 desktop computers. I'm finding that everything is working fine until I try to move a file to the rubbish bin from my home folder, when I do the progress bar sits at 0% for a very long time in Nautilus and eventually the file is deleted. If I use rm from the command line or I use the delete file option in Nautilus I get no errors and no pause. In the server logs I get the following during this process.

Oct 23 10:41:42 office kernel: [406568.806179] RPC: AUTH_GSS upcall timed out.
Oct 23 10:41:42 office kernel: [406568.806179] Please check user daemon is running.
Oct 23 10:42:00 office kernel: [406586.839669] RPC: AUTH_GSS upcall timed out.
Oct 23 10:42:00 office kernel: [406586.839669] Please check user daemon is running.
Oct 23 10:42:18 office kernel: [406604.883364] RPC: AUTH_GSS upcall timed out.
Oct 23 10:42:18 office kernel: [406604.883364] Please check user daemon is running.

Incidentally the same was happening when the desktop machines were running Ubuntu 13.04.

I set my system up using the instructions from this blog post http://www.danbishop.org/2012/06/02/...-server-guide/

/etc/exports (on server)
Code:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/export *(rw,fsid=0,crossmnt,insecure,async,no_subtree_check,sec=krb5p:krb5i:krb5)
/export/home *(rw,insecure,async,no_subtree_check,sec=krb5p:krb5i:krb5)
/export/Maven *(rw,insecure,async,no_subtree_check,sec=krb5p:krb5i:krb5)
I'm using autofs as per the blog post on the client machines to mount the home shares

/etc/auto.master (On client machines)
Code:
## Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#
#/misc /etc/auto.misc
#
# NOTE: mounts done from a hosts map will be mounted with the
# "nosuid" and "nodev" options unless the "suid" and "dev"
# options are explicitly given.
#
#/net -hosts
#
# Include /etc/auto.master.d/*.autofs
#
#+dir:/etc/auto.master.d
#
# Include central master map if it can be found using
# nsswitch sources.
#
# Note that if there are entries for /net or /misc (as
# above) in the included master map any keys that are the
# same will not be seen as the first read key seen takes
# precedence.
#
#+auto.master
/home /etc/auto.home
/nfs /etc/auto.nfs
/etc/auto.home (On client machines)
Code:
* -fstype=nfs4,rw,hard,intr,sec=krb5 office.mavennetwork.co.uk:/home/&

[Mark Dickie (mark-dickie)]

Sorry I seem to have done something wrong. This is obviously not a Launchpad bug. I was trying to submit a bug for the version of Nautilus in Ubuntu 13.10 which I believe is just called File now.

Does anyone know how I can correct this bug report?

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1247407/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Launchpad Janitor (janitor)]

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