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

Bug #1206169 reported by nico
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

tjrs pareil

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-control-center 1:3.6.3-0ubuntu30
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Mon Jul 29 17:55:32 2013
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2013-07-23 (6 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130414)
MarkForUpload: True
ProcCmdline: gnome-control-center background
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa8949edfec <g_type_check_instance_cast+28>: mov (%rax),%rdi
 PC (0x7fa8949edfec) 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 0x00007fa8949edfec 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 0x7ffff9d6e6a8
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: Upgraded to saucy on 2013-07-28 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager 0.9.7-0ubuntu4
 deja-dup 27.3.1-0ubuntu1
 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1
 gnome-control-center-unity 1.3daily13.06.19~13.04-0ubuntu1
 indicator-datetime 12.10.3+13.10.20130725-0ubuntu1

Revision history for this message
nico (ponte-nicolas) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 g_type_check_instance_cast (type_instance=0x7fa898502330, type_instance@entry=<error reading variable: Cannot access memory at address 0x7ffff9d6e6a8>, iface_type=140362088715280, iface_type@entry=<error reading variable: Cannot access memory at address 0x7ffff9d6e6a8>) at /build/buildd/glib2.0-2.37.3/./gobject/gtype.c:4008
         is_instantiatable = <optimized out>
         check = <optimized out>
 Cannot access memory at address 0x7ffff9d6e6a8
StacktraceTop: g_type_check_instance_cast (type_instance=0x7fa898502330, type_instance@entry=<error reading variable: Cannot access memory at address 0x7ffff9d6e6a8>, iface_type=140362088715280, iface_type@entry=<error reading variable: Cannot access memory at address 0x7ffff9d6e6a8>) 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
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The panel here has been rewritten/deprecated since, closing the bug

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.