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

Bug #932644 reported by Mihail
114
This bug affects 18 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Fix Released
High
Unassigned

Bug Description

TEST CASE:
1. Open gnome-control-center
2. Select Keyboard
3. Select tab 'shortcut'

ACTUAL RESULT:
this crash

EXPECTED RESULT:
No crash and it switches to the tab
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-2ubuntu9
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 15 14:31:19 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f969d186d80 <g_type_check_instance_cast+16>: mov (%rdi),%rax
 PC (0x7f969d186d80) ok
 source "(%rdi)" (0xffffffffa08a02f0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to precise on 2012-02-15 (0 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 deja-dup 21.2-0ubuntu4
 gnome-bluetooth 3.2.2-0ubuntu1
 indicator-datetime 0.3.1-0ubuntu5

Revision history for this message
Mihail (pvpdk1) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0xffffffffa08a02f0, iface_type=140284909527472) at /build/buildd/glib2.0-2.31.16/./gobject/gtype.c:3993
 create_cell (treeview=0x7f96a0894380, accessible=0x7f96a075d690, tree=0x7f96a04417f0, node=0x7f96a043e6c0, column=0xffffffffa08a02f0) at /build/buildd/gtk+3.0-3.3.14/./gtk/a11y/gtktreeviewaccessible.c:369
 _gtk_tree_view_accessible_add_state (treeview=0x7f96a0894380, tree=0x7f96a04417f0, node=0x7f96a043e6c0, state=<optimized out>) at /build/buildd/gtk+3.0-3.3.14/./gtk/a11y/gtktreeviewaccessible.c:1894
 gtk_tree_view_real_set_cursor (tree_view=0x7f96a0894380, path=0x7f96a0602b10, flags=<optimized out>) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtktreeview.c:13305
 gtk_tree_view_row_deleted (model=<optimized out>, path=<optimized out>, data=0x7f96a0894380) at /build/buildd/gtk+3.0-3.3.14/./gtk/gtktreeview.c:9139

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
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
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
visibility: private → public
description: updated
tags: added: qa-manual-testing
Changed in gnome-control-center (Ubuntu):
importance: Medium → High
milestone: none → ubuntu-12.04-beta-1
Revision history for this message
Sebastien Bacher (seb128) wrote :

gtk+3.0 (3.3.14-0ubuntu3) precise; urgency=low

  * Revert the previous upload, it turned gnome-control-center to a segfault
    land (and probably others), we will update to the next gtk including that
    stack of commits once upstream rolls a tested tarball
    (lp: #932876, #932644)

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Fix Released
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.