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

Bug #868537 reported by Daniel Hahler
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Likely a duplicate of something else, but just want to submit it, in case it turns out to be useful.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Wed Oct 5 18:51:32 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 LANGUAGE=en_US:en
 LC_TIME=de_DE.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0xb6ffd1b3 <g_type_check_instance_cast+83>: movzbl 0xe(%esi),%edx
 PC (0xb6ffd1b3) ok
 source "0xe(%esi)" (0x6e756262) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown 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: Upgraded to oneiric on 2011-09-29 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
usr_lib_gnome-control-center:
 gnome-bluetooth 3.2.0-0ubuntu1
 indicator-datetime 0.3.0-0ubuntu1

Revision history for this message
Daniel Hahler (blueyed) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0xb991c360, iface_type=80) at /build/buildd/glib2.0-2.30.0/./gobject/gtype.c:3986
 default_adapter_changed (gobject=0xb98e43a0, pspec=0xb9840e90, user_data=0xb99d4d48) at bt-widget.c:994
 g_cclosure_marshal_VOID__PARAM (closure=0xb991ea60, return_value=0x0, n_param_values=2, param_values=0xb99fe118, invocation_hint=0xbfa230e0, marshal_data=0x0) at /build/buildd/glib2.0-2.30.0/./gobject/gmarshal.c:539
 g_closure_invoke (closure=0xb991ea60, return_value=0x0, n_param_values=2, param_values=0xb99fe118, invocation_hint=0xbfa230e0) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=0xb97047c0, detail=1658, instance=0xb98e43a0, emission_return=0x0, instance_and_params=0xb99fe118) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3272

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-i386-retrace
visibility: private → public
affects: gnome-control-center (Ubuntu) → gnome-bluetooth (Ubuntu)
summary: - gnome-control-center crashed with SIGSEGV in
- g_type_check_instance_cast()
+ gnome-control-center crashed with SIGSEGV in default_adapter_changed()
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue should be fixed in that version:

gnome-bluetooth (3.2.0-0ubuntu2) oneiric-proposed; urgency=low

  * debian/patches/lp805311_disconnect-signals-from-adapters-and-devices.patch,
    debian/patches/lp805311_do-not-leak-proxies-for-interfaces.patch:
    disconnect signals for adapters and devices, and also avoid leaking DBus
    proxies for interfaces. (LP: #805311)

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