nautilus crashed with SIGSEGV in g_type_check_instance_cast()

[Jaime Rave]

I was closing all my windows when this error suddenly appear.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Fri Mar 16 00:28:16 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 org.gnome.nautilus.window-state geometry '976x550+225+109'
 org.gnome.nautilus.window-state maximized true
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120213)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=es_CO:es
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6bc50c8 <g_type_check_instance_cast+56>: mov (%eax),%ebp
 PC (0xb6bc50c8) ok
 source "(%eax)" (0x86445240) not located in a known VMA region (needed readable region)!
 destination "%ebp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_cast (type_instance=0xa61a8b8, iface_type=166020552) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:3999
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-gtk3.so.4
 g_cclosure_marshal_VOID__VOID (closure=0xa4b0650, return_value=0x0, n_param_values=1, param_values=0xa59e838, invocation_hint=0xbfefcf20, marshal_data=0x0) at /build/buildd/glib2.0-2.31.20/./gobject/gmarshal.c:85
 g_closure_invoke (closure=0xa4b0650, return_value=0x0, n_param_values=1, param_values=0xa59e838, invocation_hint=0xbfefcf20) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=0x9e01de0, detail=0, instance=0x9d81d40, emission_return=0x0, instance_and_params=0xa59e838) at /build/buildd/glib2.0-2.31.20/./gobject/gsignal.c:3547
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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