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

Bug #1226812 reported by Randy Allen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Unbuntu 13.10. Was in system settings in the network settings. Clicked on Wired Network after program opened in Wireless showing local wireless networks and program locked up and initiated bug report.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 17 15:15:10 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-09-08 (9 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130729)
MarkForUpload: True
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3302888496 <gtk_builder_get_object+22>: mov (%rbx),%rdx
 PC (0x7f3302888496) ok
 source "(%rbx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: activity-log-manager
StacktraceTop:
 gtk_builder_get_object () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/control-center-1/panels/libactivity-log-manager.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Randy Allen (rcallen7957) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_builder_get_object (builder=0x4, name=0x7f32cf4d4711 "submit_error_reports") at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkbuilder.c:1266
 on_properties_changed (interface=0x2e04780, changed_properties=<optimized out>, invalidated_properties=<optimized out>, user_data=<optimized out>) at diagnostics-widget.c:154
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=0x7fff527dcbe0, fn=0x7f32cf4d03a0 <on_properties_changed>, rvalue=0x7fff527dcb50, avalue=0x7fff527dcaf0) at ../src/x86/ffi64.c:522
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in activity-log-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in activity-log-manager (Ubuntu):
status: New → Confirmed
information type: 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.