nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

[jpgrms]

Binary package hint: nautilus

tried to run maverick netbook live usb in my box, went well, then, this error....

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Jan 22 04:18:12 2011
ExecutablePath: /usr/bin/nautilus
LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x808a882: mov (%esi),%eax
 PC (0x0808a882) ok
 source "(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
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 #705233, 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.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 630884, so it 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.