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

Bug #1346127 reported by nassem
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-control-center (Ubuntu)
New
Undecided
Unassigned

Bug Description

unity-control-center crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
this error after iupgrade ubuntu 14.10

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 i686
ApportVersion: 2.14.3-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Mon Jul 21 12:20:25 2014
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2014-05-30 (52 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
ProcCmdline: unity-control-center --overview
SegvAnalysis:
 Segfault happened at: 0xb6e2c93d <g_type_check_instance_is_fundamentally_a+45>: movzbl 0xc(%eax),%edx
 PC (0xb6e2c93d) ok
 source "0xc(%eax)" (0x0000000c) 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/i386-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/unity-control-center-1/panels/libappearance.so
 g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: unity-control-center crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: Upgraded to utopic on 2014-07-21 (0 days ago)
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
nassem (nassem1981) 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 #1335438, 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-i386-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.