nautilus crashed with SIGSEGV in pthread_mutex_lock()

[Heinrich Kruger]

Binary package hint: nautilus

I have a directory containing two symlinks, each pointing at the other (created to test a script i'm working on). Nautilus crashes when opening this directory.
After some experimenting it seems nautilus crashes whenever trying to open a directory containing a number of symlinks forming a symlink loop, but only if all the symlinks in the loop are in the same directory. I would have expected nautilus to be able to detect the loop and display the links as broken (as it does when some symlinks in the loop are located in a different directory.

To repeat:
$ mkdir test
$ cd test
$ ln -s s2 s1
$ ln -s s1 s2
Open directory test in nautilus.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Jul 12 17:59:33 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.20.0-0ubuntu7.1
PackageArchitecture: amd64
ProcCmdline: nautilus --sm-config-prefix /nautilus-H8CDYV/ --sm-client-id 117f000101000119711303700000057850002 --screen 0
ProcCwd: /home/heindsight
ProcEnviron:
 PATH=/home/heindsight/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 pthread_mutex_lock () from /lib/libpthread.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in pthread_mutex_lock()
Uname: Linux ceridwen 2.6.22-15-generic #1 SMP Tue Jun 10 08:52:15 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Heinrich Kruger (heindsight-deactivatedaccount)]

I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash.

[Sebastien Bacher (seb128)]

the crash is similar to http://bugzilla.gnome.org/show_bug.cgi?id=545189

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.