GNOME Bugzilla – Bug 672257
nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Last modified: 2012-03-16 19:35:21 UTC
Hello I was having a normal session, nothing intensive, system normally loaded, when I click the nautilus icon in the launcher system became heavy loaded then the apport popup. Thanks fabio --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad 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 x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Fri Mar 16 19:26:03 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: org.gnome.nautilus.window-state geometry '854x662+65+24' InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: nautilus -n SegvAnalysis: Segfault happened at: 0x7f8721119e9c <g_type_check_instance_cast+28>: mov (%rax),%rbp PC (0x7f8721119e9c) ok source "(%rax)" (0xaaaaaaaaaaaaaaaa) 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 precise on 2012-03-13 (3 days ago) UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
Others logfiles in the linked Launchpad report. thanks Fabio
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! It's also missing a link to the original report on Launchpad.
the issue is in libdbusmenu, not a GNOME bug