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

Bug #913652 reported by Rigved Rakshit on 2012-01-09
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Medium
Mathieu Trudel-Lapierre

Bug Description

Description: Ubuntu precise (development branch)
Release: 12.04

gnome-control-center:
  Installed: 1:3.2.2-0ubuntu5
  Candidate: 1:3.2.2-0ubuntu5
  Version table:
 *** 1:3.2.2-0ubuntu5 0
        500 http://in.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

Expected Outcome: This crash report should not have been reported.
Actual Outcome: The crash occurred after I made some changes to the bluetooth setting and then closed the Gnome Control Center.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Mon Jan 9 12:11:41 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111215)
ProcCmdline: gnome-control-center bluetooth
SegvAnalysis:
 Segfault happened at: 0x8222be <g_type_check_instance_cast+46>: mov (%edx),%eax
 PC (0x008222be) ok
 source "(%edx)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-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:
 deja-dup 21.2-0ubuntu2
 gnome-bluetooth 3.2.1-1ubuntu3
 indicator-datetime 0.3.1-0ubuntu2

Rigved Rakshit (rigved) wrote :

This crash has the same stack trace characteristics as bug #868537. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x2, iface_type=80) at /build/buildd/glib2.0-2.31.6/./gobject/gtype.c:3993
 default_adapter_changed (gobject=0x21c8e020, pspec=0x21b87538, user_data=0x21cb00d0) at bt-widget.c:994
 g_cclosure_marshal_VOID__PARAM (closure=0x21cb18e8, return_value=0x0, n_param_values=2, param_values=0x21e9df40, invocation_hint=0xbfa747a0, marshal_data=0x0) at /build/buildd/glib2.0-2.31.6/./gobject/gmarshal.c:539
 g_closure_invoke (closure=0x21cb18e8, return_value=0x0, n_param_values=2, param_values=0x21e9df40, invocation_hint=0xbfa747a0) at /build/buildd/glib2.0-2.31.6/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=0x21a1e088, detail=1764, instance=0x21c8e020, emission_return=0x0, instance_and_params=0x21e9df40) at /build/buildd/glib2.0-2.31.6/./gobject/gsignal.c:3302

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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
affects: gnome-control-center (Ubuntu) → gnome-bluetooth (Ubuntu)
Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → New
Sebastien Bacher (seb128) wrote :

Hey Mathieu, was that issue supposed to be fixed? Could you look at it?

Changed in gnome-bluetooth (Ubuntu):
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)

Indeed, this is supposed to be fixed, and the fix has by now made it to updates. Can anyone seeing this issue make sure you have fully updated your system and see if it can still be reproduced?

As far as I can tell this would probably only be reproducible if you're near an "invisible" wifi network; that's worth taking into consideration when testing. Thanks!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers