nautilus crashed with SIGSEGV in g_timeout_dispatch()

[Jean-Baptiste Lallement]

I plugged a (low quality) usb key and clicked on the Files launcher to open nautilus since it didn't automatically opened.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Jul 6 00:38:17 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
ProcCmdline: nautilus -n
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x810e88d: mov 0x308(%eax),%eax
 PC (0x0810e88d) ok
 source "0x308(%eax)" (0xaaaaadb2) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_timeout_dispatch (source=0x97f0e80, callback=0x810e880, user_data=0x9467168) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:3955
 g_main_dispatch (context=0x925f530) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:2477
 g_main_context_dispatch (context=0x925f530) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:3050
 g_main_context_iterate (context=0x925f530, block=8827904, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:3128
Title: nautilus crashed with SIGSEGV in g_timeout_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout 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.