nautilus crashed with SIGSEGV in g_main_context_dispatch()

[Brewster Malevich]

Crash report just popped-up. I will update this when I am able to reproduce.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Fri Jul 29 10:09:54 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus -n
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4bff0e: mov 0x390(%rax),%rdi
 PC (0x004bff0e) 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: Upgraded to oneiric on 2011-07-29 (0 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #804724, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.