random crashes (seg fault) when deleting files from NFS

[ericc]

Binary package hint: nautilus

From time to time (sometimes multiple times in a raw), Nautilus crashed when deleting files from a NFS folder. I do not know how to get more information (no more information when starting Natulius from a terminal), but I can see errors with dmesg, like "[ 1236.135826] nautilus[4347]: segfault at 18 ip 00000000004cf79e sp 00007fffcddf1d10 error 4 in nautilus[400000+1b6000]".

The behaviour is totally reproducible: select multiple files, delete them and sometimes Nautilus crashes, always at the end of the on-going processing (files have been actually deleted).

Same problem with NFS3 or NFS4 shares. The client (my ubuntu 10.04 for which I'm filling this bug) is the only client.

Same problem with NFS share mount with auto.fs or manually.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nautilus 1:2.30.1-0ubuntu1
Uname: Linux 2.6.33-020633-generic x86_64
Architecture: amd64
Date: Sun Jun 6 17:29:03 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: nautilus

[Robert Roygaard (ubuntu-robroyal)]

Same problem here:

$ dmesg|tail:
[19839.906696] nautilus[2802]: segfault at 18 ip 00000000004cf79e sp 00007fff07d3e460 error 4 in nautilus[400000+1b6000]
[19863.667233] nautilus[4742]: segfault at 18 ip 00000000004cf79e sp 00007fff5e3e0b60 error 4 in nautilus[400000+1b6000]
[19903.323760] nautilus[4783]: segfault at 18 ip 00000000004cf79e sp 00007fff83b8e4f0 error 4 in nautilus[400000+1b6000]
[20219.816955] nautilus[4814]: segfault at 18 ip 00000000004cf79e sp 00007ffff819bc30 error 4 in nautilus[400000+1b6000]
[21207.683299] nautilus[4906]: segfault at 18 ip 00000000004cf79e sp 00007fff300cebb0 error 4 in nautilus[400000+1b6000]
...

Nearly the same config (64 Bit Ubuntu 10.04)
Kernel: 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux

I'm also using autofs and tried manual mounts but It doesn't change the behaviour.

BTW: The servers are NFS4 Ubuntu-Servers (8.04) and a NFS4 OpenFiler NSA 2.3 - all servers are 64bit too.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[ericc (eric-cheminot)]

Yes, same problem with standard kernel.

I have not found the way to add apport information to an existing bug except from the summary search, but this search fails, saying it's taking too long. Then I've just created a new bug: # 590896.

Thanks!