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

Bug #1202840 reported by howefield
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
activity-log-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

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

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-log-manager 0.9.7-0ubuntu3
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Thu Jul 18 21:51:18 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-06-11 (37 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611)
MarkForUpload: True
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f3aa4e26546 <gtk_builder_get_object+22>: mov (%rbx),%rdx
 PC (0x7f3aa4e26546) 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 vboxusers

Revision history for this message
howefield (howefield) wrote :
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 #1201700, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
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.