gnome-control-center crashed with SIGSEGV in gtk_builder_get_object()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
activity-log-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Sorry, not sure what to say here!
This crash happened on a clean install of 13.10 beta 2, (after a full apt-get dist-upgrade) when I was in the system settings and clicked on the 'Power' icon.
The system hung for a second or two, and then the apport stuff kicked in automatically.
The system settings window greyed out and then vanished altogether.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: activity-
ProcVersionSign
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Sat Sep 28 15:27:47 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-09-28 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MarkForUpload: True
ProcCmdline: gnome-control-
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f3b97adf546 <gtk_builder_
PC (0x7f3b97adf546) 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-
StacktraceTop:
gtk_builder_
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Just to add that if I go back into system settings a click on the Power icon, this bug does not happen every time.