nautilus crashed with SIGSEGV

[Walter_Wittel]

Binary package hint: nautilus

A couple of nautilus windows appeared hung so I clicked the close x on the title bar and OK'ed killing them, then got the prompt to upload a bug report. Here is the version info from terminal:

walter@waltwld3:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
walter@waltwld3:~$ dpkg -l nautilus | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==========================================-==========================================-============================================
ii nautilus 1:2.21.90-0ubuntu1 file manager and graphical shell for GNOME
walter@waltwld3:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

ProblemType: Crash
Architecture: i386
Date: Sat Feb 2 22:31:44 2008
Disassembly: 0xb75ee837:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: cdrom
Package: nautilus 1:2.21.90-0ubuntu1
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcCwd: /home/walter
ProcEnviron:
 PATH=/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
Stacktrace: #0 0xb75ee837 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: nautilus crashed with SIGSEGV
Uname: Linux waltwld3 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Walter_Wittel (wittelw)]

Pedro, thanks for your pointers. I'm a nubie but was able to figure out that I needed to install nautilus-dbgsym to get a backtrace. If I run "gdb nautilus" and set a breakpoint at main I can get a backtrace with symbols, however if I unzip CoreDump.gz and run "gdb nautilus ~/Desktop/CoreDump" I get the following error: "Cannot access memory at address 0xb7fac658". Backtrace produces a similar error:

#0 0xb75ee837 in ?? ()
Cannot access memory at address 0xbfdfbb64

Unfortunately when I installed nautilus-dbgsym I think it also upgraded nautilus, so the symbols probably no longer match CoreDump at the time of the crash, and I haven't seen this crash repeat. Are we SOL or is there some way to recover a backtrace at this point? If you could give me a pointer to forcing load of old symbols or some other technique I will be happy to try again after work tomorrow (machine is at home).

[Sebastien Bacher (seb128)]

The bug might be fixed with the new versions, closing this one if you run into the issue again could you open a new one using apport so it's retraced?

[Walter_Wittel (wittelw)]

Will do. Thanks!