nautilus crashed with SIGSEGV in g_type_check_instance_cast()

[Rigved Rakshit]

Description: Ubuntu precise (development branch)
Release: 12.04

nautilus:
  Installed: 1:3.3.91-0ubuntu4
  Candidate: 1:3.3.91-0ubuntu4
  Version table:
 *** 1:3.3.91-0ubuntu4 0
        500 http://in.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

Expected Outcome: The bluetooth folder should have opened up.

Actual Outcome: I clicked on Browse Folder on my bluetooth-connected phone. Then, this crash was reported.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.91-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Fri Mar 16 20:26:15 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: org.gnome.nautilus.window-state maximized true
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111215)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x5a10c8 <g_type_check_instance_cast+56>: mov (%eax),%ebp
 PC (0x005a10c8) ok
 source "(%eax)" (0x35783020) 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 () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libdbusmenu-gtk3.so.4
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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.