MASTER bluetooth-applet crashed with SIGSEGV in g_type_instance_get_private()

StacktraceTop:g_type_instance_get_private ()
add_killswitch (killswitch=0x89eafa0,
event_cb (source=0x89f3960,
?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0

Same problem with my laptop (acer aspire 5720z) But after a log-off and log-on with connected adapter, the bluetooth is working well.

Same problem

I have this same problem (Toshiba Bluetooth).

Same problem here. It happened right after I plugged in an usb bluetooth receiver.

Applet crashed when i plug BT adapter D-link DBT-122

Same problem on my Fujitsu Siemens V3205.

this problem on my dekstop pc

Occurs here too, on amd64.

The bug seems to stem from the fact that bluetooth_killswitch_init in lib/bluetooth-killswitch.c sets up an IO watch, but bluetooth_killswitch_finalize doesn't clean it up. As such, when the event actually does come, event_cb goes and uses a freed object handle and promptly explodes.

Attached is a patch that solves this problem, but I think there's another, more fundamental bug here; if the bluetooth dongle isn't plugged in at startup, it seems to deinitialize killswitch handling permanently. For example, if I start it up with the dongle in, then unplug the dongle:
** Message: adding killswitch idx 22 state 1
** Message: Reading of RFKILL events failed
** Message: killswitch 22 is 1
** Message: killswitches state 1
** Message: killswitch 22 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 22 type 2 op 1 soft 0 hard 0

** Message: removing killswitch idx 22
** Message: killswitches state 1

But if I start with it out, then plug it in and remove it:
** Message: Reading of RFKILL events failed
** Message: killswitches state 1

Perhaps the killswitch-unreffing in main.c:990 should be removed as well? I'm not familiar enough with the code to know if this is the right approach, though.

Fresh install : install from CD, aptitude full-upgrade, install restricted-extra.
Suspend (not a suspend to disk).
Same problem happened on resume.

Same problem when I plug in my bluetooth usb adapter under Karmic.
My device is a Pilot 2 (22b8:0850 Motorola PCS Bluetooth Device)

I'm using also KDE and kdebluetooth seems to works fine...

I've put a version of the package with my patch (effectively the same one I posted to upstream's bugzilla; slightly different from the one in this thread as it disables the killswitch-disabling logic in main as well) in my PPA at: https://edge.launchpad.net/~bdonlan/+archive/test/+packages

It'd be helpful if some people could give it a test - in particular, make sure your bluetooth RF killswitches still work after this!

Thanks for your work on this Bryan! I have tested your 2.28.1-0ubuntu2~local1 packages and they seem to fix the issue here.

The drop-down menu still says "Bluetooth: On" when I have disabled it with the killswitch, and clicking "Turn off" does not change it. But I guess that's another bug, because the rest of the menu reacts correctly. It seems like the on/off in the menu is independent of the killswitch.

@Tormod: Does your bluetooth device still show up in lsusb when the killswitch is on? If not, it's probably implemented by just disconnecting the USB connection to the bluetooth hardware rather than a killswitch as bluetooth-applet considers them. Unfortunately I don't have any hardware with any accessible killswitch whatsoever here so I don't know what the correct behavior is :/

Bryan, it disappears from lsusb when the killswitch is on.

@Tormod, ok, that means you probably don't have a killswitch as bluetooth-applet sees them.
Note that this bug only occurs if you have zero killswitches when the applet starts up, so if your bluetooth adapter is internal, it's a good bet that you have that kind of pure-hardware killswitch if you experience this bug (and the killswitch is likely to be off when the applet starts...)

Same problem here. It also affects Belkin USB adapters.

Same problem here. Sony Vaio vgn-fw21j & amd64

i have the the same problem with a trust bluetooth.
i confirm that logging off and on again the bluetooth works.
also on ubuntu 9.04 worked fine.

This bug was fixed in the package gnome-bluetooth - 2.28.1-0ubuntu2

---------------
gnome-bluetooth (2.28.1-0ubuntu2) karmic; urgency=low

  * fix LP: #437162 - Gnome Bluetooth needs to use different icons for
    notification area and system menu; take notify.c part of bgo:596564
    patch to support special icons for tray; also install all bluetooth.png
    as bluetooth-active.png in binary-post-install/gnome-bluetooth::
    - debian/patches/01-status-icon.patch
  * fix LP: #445422 - topcrash bluetooth-applet crashed with SIGSEGV in
    g_type_instance_get_private(); add improved patch from bgo:598181
    att:145298
    - debian/patches/02-lazy-killswitch-crashes.patch
  * fix memleak surrouding killswitch removal
    - debian/patches/03-fix-killswitch-memleak.patch
  * fix handling of killswitch removal
    - debian/patches/04-fix-yes-no-killswitch-handling.patch
  * fix icon not properly removed from panel after bt device/killswitch
    gets removed
    - debian/patches/05-fix-icon-visibility-for-no-killswitch.patch

 -- Alexander Sack <email address hidden> Wed, 14 Oct 2009 17:00:55 +0200