nautilus crashed with SIGSEGV in g_main_context_dispatch()

[Anthony Harrington]

Seems to be a duplicate of the difficult to reproduce Bug #821342 (marked as invalid?) which is still occurring even on Ubuntu 11.10 beta 1, so here's some fresh data on it.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 3 15:15:39 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x4c0cbe: mov 0x390(%rax),%rdi
 PC (0x004c0cbe) ok
 source "0x390(%rax)" (0xaaaaaaaaaaaaae3a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Anthony Harrington (linuxchemist)]

That stacktrace isn't very useful either, is it? I've installed nautilus-dbg now so if the error returns, that should help :(