nautilus crashed with SIGSEGV

[Martin Schaaf]

Binary package hint: nautilus

Crashed on gnome session (re)startup.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Sep 29 19:11:51 2008
Disassembly: 0x473212d6:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.22.5.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Title: nautilus crashed with SIGSEGV
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape vboxusers video

[arno_b (arno.b)]

Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/Backtrace and http://live.gnome.org/GettingTraces/Details (you have to install the nautilus-dbg package to use the debugger).

Set to incomplete until we have more a backtrace or more info.

[arno_b (arno.b)]

There is no duplicate here... since we do not have any backtrace... :s

[Sebastien Bacher (seb128)]

that's a duplicate, the retracing bot get the stacktrace using the crash information, look in the database and if the bug is a duplicate it cleans the informations so the bug can be set public without exposing a password or something and then close the bug as duplicate which is what it has been doing there

[arno_b (arno.b)]

Yep, I know that; the problem is that the former stacktrace (http://launchpadlibrarian.net/18084329/Stacktrace.txt) has no symbol so how can it know that it is a duplicate? There is no info about gconf_client_remove_dir() here.

[Sebastien Bacher (seb128)]

the retracer doesn't use the stacktrace sent by apport which is done on the client side but use apport-retrace and install the dbgsym to get a debug stacktrace, then it attachs the retraced stacktrace to the bug if the crash is new or close the bug as duplicate if this new debug stacktrace matches an open bug