nautilus crashed with SIGSEGV in pthread_mutex_lock()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nautilus |
Expired
|
Critical
|
|||
nautilus (Ubuntu) |
Invalid
|
Medium
|
Ubuntu Desktop Bugs |
Bug Description
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
NonfreeKernelMo
Package: nautilus 1:2.20.0-0ubuntu7.1
PackageArchitec
ProcCmdline: nautilus --sm-config-prefix /nautilus-H8CDYV/ --sm-client-id 117f00010100011
ProcCwd: /home/heindsight
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
pthread_mutex_lock () from /lib/libpthread
g_signal_
g_signal_emit () from /usr/lib/
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in pthread_
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
Changed in nautilus: | |
status: | Incomplete → New |
Changed in nautilus: | |
status: | Unknown → Confirmed |
Changed in nautilus: | |
importance: | Unknown → Critical |
Changed in nautilus: | |
status: | Confirmed → Expired |
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/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.