gnome-control-center.real crashed with SIGSEGV in gnome_control_center_show()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
(gnome-
(gnome-
(gnome-
[1] 6626 segmentation fault (core dumped) gnome-control-
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 28 15:40:42 2014
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-01-28 (59 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017)
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/zsh
SegvAnalysis:
Segfault happened at: 0x409ee1 <gnome_
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-
Stacktrace:
#0 0x0000000000409ee1 in gnome_control_
No symbol table info available.
#1 0x0000000000407306 in _start ()
No symbol table info available.
StacktraceTop:
gnome_
_start ()
Title: gnome-control-
UpgradeStatus: Upgraded to trusty on 2014-03-28 (0 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
XsessionErrors:
(process:2869): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:2869): GLib-GObject-
(firefox:2869): GLib-GObject-
(firefox:2869): GLib-GObject-
(firefox:2869): GLib-GObject-
usr_lib_
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.