gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1196619 reported by DonnieD
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Medium
Unassigned

Bug Description

Tried to open Apearance tab. But contents was hidden, only background image was shown and changing it was possible. Then crashed

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu29
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Mon Jul 1 20:02:21 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-07-01 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130701)
MarkForUpload: True
ProcCmdline: gnome-control-center
SegvAnalysis:
 Segfault happened at: 0x7f230d08dfec <g_type_check_instance_cast+28>: mov (%rax),%rdi
 PC (0x7f230d08dfec) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
Stacktrace:
 #0 0x00007f230d08dfec in g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 No symbol table info available.
 Cannot access memory at address 0x7fff78a0d1c8
StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu6.1
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1
 gnome-control-center-unity 1.3daily13.06.14.1-0ubuntu1
 indicator-datetime 12.10.3+13.10.20130628-0ubuntu1

Revision history for this message
DonnieD (donnied) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 g_type_check_instance_cast (type_instance=0x7f2310071490, type_instance@entry=<error reading variable: Cannot access memory at address 0x7fff78a0d1c8>, iface_type=139788569127904, iface_type@entry=<error reading variable: Cannot access memory at address 0x7fff78a0d1c8>) at /build/buildd/glib2.0-2.37.3/./gobject/gtype.c:4008
         is_instantiatable = <optimized out>
         check = <optimized out>
 Cannot access memory at address 0x7fff78a0d1c8
StacktraceTop: g_type_check_instance_cast (type_instance=0x7f2310071490, type_instance@entry=<error reading variable: Cannot access memory at address 0x7fff78a0d1c8>, iface_type=139788569127904, iface_type@entry=<error reading variable: Cannot access memory at address 0x7fff78a0d1c8>) at /build/buildd/glib2.0-2.37.3/./gobject/gtype.c:4008

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → 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.