gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()

Bug #1299903 reported by Adam
This bug report is a duplicate of:  Bug #1392954: Handle soname bumps in package names. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just tried to open Gnome settings

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-control-center 1:3.6.3-0ubuntu54
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Mar 30 21:55:31 2014
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2012-11-28 (487 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: /usr/bin/gnome-control-center.real --overview
SegvAnalysis:
 Segfault happened at: 0x409ee1 <gnome_control_center_show+17>: mov 0x20(%rbx),%rdx
 PC (0x00409ee1) ok
 source "0x20(%rbx)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
Stacktrace:
 #0 0x0000000000409ee1 in gnome_control_center_show ()
 No symbol table info available.
 #1 0x0000000000407306 in _start ()
 No symbol table info available.
StacktraceTop:
 gnome_control_center_show ()
 _start ()
Title: gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
UpgradeStatus: Upgraded to trusty on 2014-03-25 (5 days ago)
UserGroups: adm cdrom dip ftp libvirtd lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager 0.9.7-0ubuntu12
 deja-dup 30.0-0ubuntu2

Revision history for this message
Adam (adam-jackman) 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 #1278209, 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.