unity-control-center crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1335432 reported by ventrical
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
unity-control-center (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Attempting to adjust Screen power options in System Settings. Also 'Appearance' tool .. then bug came up.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-control-center 14.10.0+14.10.20140604-0ubuntu2
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 28 09:48:38 2014
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2014-05-14 (44 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140514)
ProcCmdline: unity-control-center
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fcb842e0ab7 <g_type_check_instance_is_fundamentally_a+39>: movzbl 0x14(%rax),%edx
 PC (0x7fcb842e0ab7) ok
 source "0x14(%rax)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libappearance.so
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-control-center crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_unity-control-center:
 activity-log-manager 0.9.7-0ubuntu14
 deja-dup 30.0-0ubuntu6

Revision history for this message
ventrical (dale-f-beaudoin) wrote :
information type: Private → Public Security
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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 unity-control-center (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libnspr4 version 2:4.10.2-1ubuntu1 required, but 2:4.10.6-1ubuntu1 is available
libpulse-mainloop-glib0 version 1:4.0-0ubuntu15 required, but 1:4.0-0ubuntu16 is available
outdated debug symbol package for libevdev2: package version 1.2.2+dfsg-1 dbgsym version 1.0.99.2+dfsg-2ubuntu2
libpulse0 version 1:4.0-0ubuntu15 required, but 1:4.0-0ubuntu16 is available
no debug symbol package found for libgudev-1.0-0
outdated debug symbol package for libxshmfence1: package version 1.1-3 dbgsym version 1.1-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

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