Bluetooth is disabled after coming back from sleep

[Oded Arbel]

I'm using Karmic with gnome-bluetooth 2.27.5-1ubuntu1 on a Thinkpad T61 with a builtin broadcom bluetooth adapter:
$ lsusb
Bus 003 Device 008: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller

The problem is that after waking from sleep, the hardware bluetooth led is on, but the gnome-bluetooth icon has a red X and I cannot connect to any device: when I open the context menu it shows no devices and all entries are disabled except "preferences" and the top 2 that read "Bluetooth: On" and "Turn off bluetooth".

Choosing "turn off bluetooth" has no effect. When I open the preferences dialog, it has only the text "Bluetooth is disabled" and a large button labeled "Turn on bluetooth" (yes, the opposite of the menu). Clicking the button makes the button disabled but otherwise has no effect - if I close the preferences dialog and open it again, it reverts back to the same status.

Syslog shows nothing interesting when I do this, nor does dmesg. Grepping dmesg though gives me these:
$ dmesg | grep blue
[ 7597.840073] <6>bluetoothd[6362]: segfault at 7f658eccb4 ip 00007f658e9d6b79 sp 00007fffb89558b0 error 4 in libc-2.9.so[7f658e95f000+166000]
[ 8291.984110] <6>bluetoothd[10580]: segfault at 7fa791e9a4 ip 00007fa791ba5b79 sp 00007fff1b3d1b60 error 4 in libc-2.9.so[7fa791b2e000+166000]

I think the time stamps are from when I woke the computer.

lastly bluetoothd is not currently running.

I can often workaround the issue by toggling the kill radio switch off and then on again (either through the hardware toggle or using the Thinkpad's Fn+F5 shortcut). When I do that, bluetoothd comes back up and everything goes back to normal.

I opened the ticket on gnome-bluetooth as it is obviously behaving badly (the applet menu and pref dialog disagreeing on the bluetooth state and failing to work), but quite likely the underlying problem is in bluez's bluetoothd or the driver.

[Kye Lewis (kye-lewis)]

I've encountered identical behavior, but from a cold boot, not sleep mode, on a desktop.
Still running bluez 4.47-0ubuntu1 at the time of this fault; i have just updated to 4.48-0ubuntu1 0 and will report back if problem re-occurs.

kye@whempist:~$ hcitool dev
Devices:

kye@whempist:~$ lsusb
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 045e:0721 Microsoft Corp. LifeCam NX-3000 (UVC-compliant)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 045e:0053 Microsoft Corp. Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

/var/log/messages:
Aug 18 23:24:00 whempist kernel: [ 16.564078] usbcore: registered new interface driver btusb

kye@whempist:~$ time bluetoothd --nodaemon --debug --udev

real 0m0.017s
user 0m0.004s
sys 0m0.000s

bluetooth works properly again after unplugging and re-plugging usb bluetooth adapter

[Oded Arbel (oded-geek)]

It actually didn't happen to me in the last couple of weeks. Possibly this was fixed upstream. Kye - if you can't reproduce this problem, please let me know so I can close this ticket.

[Alexander Sack (asac)]

I would think this might be fixed in latest packages. Please confirm that this is still the case with up-to-date karmic. Thanks!

[florin (florin-arjocu)]

I upgraded Ubuntu 10.10 to Ubuntu 11.4 (Natty), but I have this bug. I'm not sure if what I use it's gnome-bluetooth, in Startup it's shown as bluetooth-applet.

It is just like the above description. I use an usb bluetooth dongle.

[florin (florin-arjocu)]

It says there is a bugfix. How could one get it?