nautilus crashed with SIGSEGV in g_type_check_instance_cast()

[RdeWit]

nautilus crashed after logging in after reboot after upgrading packages.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
Date: Mon Sep 24 22:39:36 2012
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1165x597+48+24'"
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f9ad078ae8c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7f9ad078ae8c) ok
 source "(%rax)" (0x700000008) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to quantal on 2012-09-15 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
XsessionErrors:
 (gnome-panel:2478): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed
 (indicator-multiload:2493): GLib-GIO-CRITICAL **: GApplication subclass 'Main' failed to chain up on ::startup (from start of override function)
 (gnome-panel:2478): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed
 (nautilus:2473): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `DbusmenuMenuitem'

[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 #1053670, 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.