gnome-control-center crashed with SIGSEGV in gtk_hbox_get_type()

Bug #1189034 reported by userDepth
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Privacy setting fails to start.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-control-center 1:3.6.3-0ubuntu24
ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13
Uname: Linux 3.8.0-24-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sat Jun 8 17:05:54 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-04-25 (44 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: gnome-control-center activity-log-manager
SegvAnalysis:
 Segfault happened at: 0x7f841b98237a <gtk_hbox_get_type+138>: movabs %rax,0x245c8948c35b10c4
 PC (0x7f841b98237a) ok
 source "%rax" ok
 destination "0x245c8948c35b10c4" (0x245c8948c35b10c4) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 gtk_hbox_get_type () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_hbox_get_type()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 26.0-0ubuntu1
 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1
 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1
 indicator-datetime 12.10.3daily13.03.26-0ubuntu1

Revision history for this message
userDepth (binarydepth) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_hbox_get_type () at /build/buildd/gtk+3.0-3.6.4/./gtk/deprecated/gtkhbox.c:59
 _gtk_builder_resolve_type_lazily (name=0x7f841c78bc70 "GtkHBox") at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkbuilder.c:423
 gtk_builder_real_get_type_from_name (builder=<optimized out>, type_name=0x7f841c78bc70 "GtkHBox") at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkbuilder.c:444
 _gtk_builder_construct (builder=0x7f841c76f000, info=info@entry=0x7f841c787dc0, error=0x7fff69369f60) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkbuilder.c:591
 builder_construct (error=<optimized out>, object_info=0x7f841c787dc0, data=<optimized out>) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtkbuilderparser.c:195

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug hasn't seen any activity in years and there has been no recent similar reports, the code also changed quite a lot since and it's likely the issue doesn't exist anymore. Closing, feel free to open a new report if you still get problems in recent Ubuntu versions

Changed in gnome-control-center (Ubuntu):
status: New → Invalid
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.