libgio's move-to-trash funciton freezes system when trashing files in kerberized, NFS mounted filesystems

[Jan Sanders]

Description: Ubuntu 12.04.1 LTS
Release: 12.04

nautilus:
  Installed: 1:3.4.2-0ubuntu4
  Candidate: 1:3.4.2-0ubuntu4
  Version table:
 *** 1:3.4.2-0ubuntu4 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:3.4.1-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

thunar:
  Installed: 1.2.3-3ubuntu2
  Candidate: 1.2.3-3ubuntu2
  Version table:
 *** 1.2.3-3ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
        100 /var/lib/dpkg/status

The setting is:

- the user joeuser has a home directory which is mounted via NFS Version 4
- the NFS4 mount uses Kerberos (-o sec=krb5) for authentication, which is the only non-default mount option
- the user uses either Nautilus or Thunar as a graphical file manager
- the user moves a small number of files to trash using either Thunar or Nautilus, after at most 20 times (independent on uptime or login time) the bug emerges: when the user moves file ~/foobar_21 to trash the operation takes a very long time (30 secs and longer)
- during the wait we have observerd that nautious/thunar and other applications freeze or will not start
-- top, as joeuser, will not start until the file ~/foobar_21 has been moved to trash
-- cat ~/myfile.txt does not work until the file has been moved to trash
-- the Thunar and Nautilus windows are not redrawn
- ls does work and we can see that the original file ~/foobar_21 is deleted shortly before the end of the wait time

The file managers Dolphin and Xfe work as expected taking well under a second to trash files.
Other file managers have not been tested.

FTR:
dolphin:
  Installed: 4:4.8.4-0ubuntu0.1
  Candidate: 4:4.8.4-0ubuntu0.1
  Version table:
 *** 4:4.8.4-0ubuntu0.1 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     4:4.8.2-0ubuntu2 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

xfe:
  Installed: 1.32.4-3
  Candidate: 1.32.4-3
  Version table:
 *** 1.32.4-3 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
        100 /var/lib/dpkg/status

nfs-common:
  Installed: 1:1.2.5-3ubuntu3
  Candidate: 1:1.2.5-3ubuntu3
  Version table:
 *** 1:1.2.5-3ubuntu3 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

krb5-user:
  Installed: 1.10+dfsg~beta1-2ubuntu0.3
  Candidate: 1.10+dfsg~beta1-2ubuntu0.3
  Version table:
 *** 1.10+dfsg~beta1-2ubuntu0.3 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     1.10+dfsg~beta1-2 0
        500 http://de.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

Linux HOSTNAME 3.2.0-30-generic #48-Ubuntu SMP Fri Aug 24 16:52:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[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/1051952/+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.]

[Jan Sanders (jsanders-t)]

The following will trigger the behaviour, so the common cause seems to be libgio:

#include <gio/gio.h>
#include <stdio.h>

int main(int argc, char **argv)
{ char *path;
   GFile *file;

   g_type_init();

   if(argc != 2) exit(1);

   path=argv[1];

   printf("Moving %s to trash...\n", path);

   file = g_file_new_for_path(path);

   /* The following call hangs for about one minute
      if path points to NFSv4 mounted volumes with
      Kerberos, then succeeds. */

   if (g_file_trash(file, NULL, NULL))
     printf("true\n");
   else
     printf("false\n");
}

[Launchpad Janitor (janitor)]

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

[Sven Heinrich (s-heinrich)]

Just a small contribution to the still unresolved topic.
- The freeze of nautilus can be avoided if the file is deleted permanently (Shift + DEL)
- a problem with MOVING the file (to the trash)??

Associated with that or not it also takes the problem (long temporary freezes) for
- open and save files in Kile
- save files from Okular
- save files from Kate

[Sebastien Bacher (seb128)]

Is that still an issue in current Ubuntu versions?

[Sean Davis (bluesabre)]

Expiring due to lack of confirmation.