nautilus crashed with SIGSEGV in g_thread_create_proxy()

[Steffen Röcker]

Binary package hint: nautilus

I logged out and nautilus crashed after I logged in again.

ProblemType: Crash
Architecture: i386
Date: Sun Jun 28 21:01:54 2009
Disassembly: 0x4143a30:
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.2-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.30-9.10-generic
SegvAnalysis: Failure: list index out of range
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_thread_create_proxy (data=0x62ed)
 start_thread () from /lib/tls/i686/cmov/libpthread.so.0
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: nautilus crashed with SIGSEGV in g_thread_create_proxy()
Uname: Linux 2.6.30-9-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:?? ()
g_thread_create_proxy (data=0x62ed)
start_thread () from /lib/tls/i686/cmov/libpthread.so.0
clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

[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.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[MrWoo (laxix-deactivatedaccount)]

I've made a backtrace, though I don't think that helps because on my system the crash appears right after login.