nautilus crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1055970 reported by Timo Jyrinki
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Just logged out and again in, not sure at which exact moment the crash happened but opened only Firefox.

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
CheckboxSubmission: 1896b893828b4203b948b1eb6546be06
CheckboxSystem: d00f84de8a555815fa1c4660280da308
CrashCounter: 1
Date: Tue Sep 25 09:15:47 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1074x707+524+164'"
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7f1238889e8c <g_type_check_instance_cast+28>: mov (%rax),%rbp
 PC (0x7f1238889e8c) 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 (type_instance=0x1d93760, iface_type=25132496) at /build/buildd/glib2.0-2.33.14/./gobject/gtype.c:3997
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk3.so.4
 g_closure_invoke (closure=0x1d9e8c0, return_value=0x0, n_param_values=2, param_values=0x7fff81c13680, invocation_hint=0x7fff81c13620) at /build/buildd/glib2.0-2.33.14/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x15af530, detail=detail@entry=679, instance=instance@entry=0x161e680, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff81c13680) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=0x161e680, signal_id=<optimized out>, detail=679, var_args=var_args@entry=0x7fff81c138d8) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3300
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to quantal on 2012-09-04 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #1053670. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x1d93760, iface_type=25132496) at /build/buildd/glib2.0-2.33.14/./gobject/gtype.c:3997
 settings_notify_cb (settings=0x161e680, pspec=<optimized out>, data=<optimized out>) at /build/buildd/libdbusmenu-12.10.1/./libdbusmenu-gtk/parser.c:1356
 g_closure_invoke (closure=0x1d9e8c0, return_value=0x0, n_param_values=2, param_values=0x7fff81c13680, invocation_hint=0x7fff81c13620) at /build/buildd/glib2.0-2.33.14/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x15af530, detail=detail@entry=679, instance=instance@entry=0x161e680, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff81c13680) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=0x161e680, signal_id=<optimized out>, detail=679, var_args=var_args@entry=0x7fff81c138d8) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3300

Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.