[Karmic Beta] Bluetooth is disabled.

Bug #447312 reported by Henry Gomersall
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: gnome-bluetooth

Bluetooth appears to be disabled. Mousing over the bluetooth icon shows "Bluetooth: Disabled"

Clicking the bluetooth icon gives me a reduced menu with only options shown in the attached screenshot.

The preferences dialogue is entirely greyed out as shown in the screenshot.

I am aware of bug #441800 and I can confirm that I have gnome-bluetooth 2.28.1-0ubuntu1.

This is running on Karmic Beta, updated and rebooted today (9/10/09). This problem has only manifested itself on Karmic and bluetooth worked fine under Jaunty.

The following output from dmesg reports no problems:
[ 0.380007] Bluetooth: Core ver 2.15
[ 0.380024] Bluetooth: HCI device and connection manager initialized
[ 0.380024] Bluetooth: HCI socket layer initialized
[ 0.706470] Bluetooth: L2CAP ver 2.13
[ 0.706472] Bluetooth: L2CAP socket layer initialized
[ 0.706475] Bluetooth: SCO (Voice Link) ver 0.6
[ 0.706476] Bluetooth: SCO socket layer initialized
[ 0.706521] Bluetooth: RFCOMM TTY layer initialized
[ 0.706524] Bluetooth: RFCOMM socket layer initialized
[ 0.706525] Bluetooth: RFCOMM ver 1.11
[ 26.738593] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 26.738596] Bluetooth: BNEP filters: protocol multicast
[ 27.395868] Bluetooth: Generic Bluetooth USB driver ver 0.5

I cannot use any of the command line tools. There appears to be no /dev/hciX devices.

Please advise what further information is required to debug this.

Revision history for this message
Henry Gomersall (hgomersall) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

are you using a dell? can you please post the output of rfkill list when you see this?

Changed in gnome-bluetooth (Ubuntu):
status: New → Incomplete
Revision history for this message
Henry Gomersall (hgomersall) wrote :

Yes, this is using a Dell Inspiron 9400 with builtin bluetooth.

output from rfkill list:

1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: no
3: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
12: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

Revision history for this message
Alexander Sack (asac) wrote :

all updated to latest doesnt work for you?

Revision history for this message
Alexander Sack (asac) wrote :

also killall bluetooth-applet

and run it from terminal like

bluetooth-applet -d

then post the output you get

Revision history for this message
Henry Gomersall (hgomersall) wrote :

No, latest doesn't solve the problem.

Output from bluetooth-applet -d:

** Message: adding killswitch idx 1 state 1
** Message: adding killswitch idx 2 state 1
** Message: Reading of RFKILL events failed
** Message: killswitch 1 is 1
** Message: killswitch 2 is 1
** Message: killswitches state 1
** (bluetooth-applet:3168): DEBUG: Unhandled UUID 00005001-0000-1000-8000-0002ee000001 (0x5001)
** (bluetooth-applet:3168): DEBUG: Unhandled UUID 00005002-0000-1000-8000-0002ee000001 (0x5002)
** (bluetooth-applet:3168): DEBUG: Unhandled UUID 00005003-0000-1000-8000-0002ee000001 (0x5003)
** (bluetooth-applet:3168): DEBUG: Unhandled UUID 00005557-0000-1000-8000-0002ee000001 (0x5557)
** (bluetooth-applet:3168): DEBUG: Unhandled UUID 00005601-0000-1000-8000-0002ee000001 (0x5601)
** Message: killswitch 1 is 1
** Message: killswitch 2 is 1
** Message: killswitches state 1

Revision history for this message
Henry Gomersall (hgomersall) wrote :

That seems rather telling. Is the UUID its referring to a hardware ID? ie, is this a problem with the applet just not knowing about the hardware?

Revision history for this message
Christian Schendel (doppelhelix) wrote :

same here on a eeepc 901:
** Message: adding killswitch idx 2 state 1
** Message: adding killswitch idx 3 state 1
** Message: Reading of RFKILL events failed
** Message: killswitch 2 is 1
** Message: killswitch 3 is 1
** Message: killswitches state 1
** Message: killswitch 2 is 1
** Message: killswitch 3 is 1
** Message: killswitches state 1

Revision history for this message
Henry Gomersall (hgomersall) wrote :

A simple

sudo hciconfig hci0 up

enables the bluetooth and everything seems to work.

Still not sure how to make this happen at every boot (without a hacky script of my own). I presume this should be added to /etc/init.d/bluetooth ?

Revision history for this message
Henry Gomersall (hgomersall) wrote :

More info:
After a shutdown and boot, the bluetooth is correctly enabled. Is this the state being remembered by Ubuntu? In which case, this is still a bug, albeit a minor one.

An upgrade should not stop the bluetooth working with no obvious way to turn it on.

Revision history for this message
Christian Schendel (doppelhelix) wrote :

<Quote>

A simple

sudo hciconfig hci0 up

enables the bluetooth and everything seems to work.

</Quote>

That works for me, too. A bit annoying, though.

Revision history for this message
Henry Gomersall (hgomersall) wrote :

Further to this bug, the bluetooth is not robust to suspend. Sometimes after suspend, the bluetooth is not up. Restarting the bluetooth service repeatedly seems to eventually re-enable it. Pauses seem to be necessary at some stage. Its not clear exactly what causes the re-enabling.

Revision history for this message
Eduardo Durany Fernández (edurany) wrote :

Same problem here with a bluetooth usb dongle that works on jaunty.
sudo hciconfig hci0 up does not work for me. Bluetooth-applet always shows "Bluetooth: Disabled"

hcitool scan and sdptool browse WORK OK on command line so the bug is in gnome-bluetooth.

Ubuntu Karmic updated and upgraded: gnome-bluetooth_2.28.1-0ubuntu2

lsusb:
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 006: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

rfkill list:
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
4: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

bluetoothd --nodaemon --debug (shows at the end):
bluetoothd[2749]: Adapter /org/bluez/2749/hci0 has been enabled
bluetoothd[2749]: Computer is classified as laptop
bluetoothd[2749]: Setting 0x00010c for major/minor device class
bluetoothd[2749]: Unable to register adapter: hci0 already exist

bluetooth-applet -d:
** Message: adding killswitch idx 5 state 1
** Message: killswitch 5 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 5 type 2 op 2 soft 0 hard 0

** Message: killswitch 5 is 1
** Message: killswitches state 1
Agent registration failed: The name org.bluez was not provided by any .service files

dmesg |grep bluetooth:
[ 0.102585] Bluetooth: Core ver 2.15
[ 0.102621] Bluetooth: HCI device and connection manager initialized
[ 0.102625] Bluetooth: HCI socket layer initialized
[ 0.897158] Bluetooth: L2CAP ver 2.13
[ 0.897161] Bluetooth: L2CAP socket layer initialized
[ 0.897164] Bluetooth: SCO (Voice Link) ver 0.6
[ 0.897166] Bluetooth: SCO socket layer initialized
[ 0.897210] Bluetooth: RFCOMM TTY layer initialized
[ 0.897214] Bluetooth: RFCOMM socket layer initialized
[ 0.897217] Bluetooth: RFCOMM ver 1.11
[ 7.428296] Bluetooth: Generic Bluetooth USB driver ver 0.5
[ 21.054644] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.054649] Bluetooth: BNEP filters: protocol multicast

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → New
Revision history for this message
Eduardo Durany Fernández (edurany) wrote :

blueman from repo crash and blueman from ppa:blueman/ppa gives an exception on some dbus method.
So something is wrong with dbus protocol between desktop apps and bluez because hcitool and sdptool work perfectly on my machine.

bluez, gnome-bluetooth, blueman...
Next chapter on your ubuntu.

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

I am on Dell Inspiron 1011, fully updated karmic, same issue. I do have bluetooth enabled in BIOS, but

 sudo hciconfig hci0 up
 Can't get device info: No such device

Is that a separate issue? Doing sudo lshw|grep -i blue returns nothing, as if the interface were not visible at all.

Revision history for this message
Sergey K (koblin) wrote :

i have same issue with external usb bluetooth adapter...

bluetooth-properties
** Message: adding killswitch idx 0 state 1
** Message: Reading of RFKILL events failed
** Message: killswitch 0 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 0 type 2 op 2 soft 0 hard 0

** Message: killswitch 0 is 1
** Message: killswitches state 1

Revision history for this message
selimhanov (selimhanov) wrote :

Same problem here with Lenovo s10-2. Everything worked great until I, for some reasons, turned bluetooth off, now I can't turn it back on.

Revision history for this message
selimhanov (selimhanov) wrote :

 I solved my problem with disabled bluetooth doing following:
 Wrote in terminal

 rfkill list

 and got message something like
-------------------------------------------
 1: phy0: Wireless LAN
             Soft blocked: no
             Hard blocked: no
         ........
3: hci0: Bluetooth
            Soft blocked: no
            Hard blocked: no
---------------------------------------------
in order to detect idx of my bluetooth device (in my case, hci0)
then we should type

rfkill unblock hci0 (you should write your idx of your bluetooth device instead of "hci0")

then just log off and log in again or restart PC and bluetooth now must work properly.

Sorry, can't remember the thread at launchpad where I found this solution, that's why described it the way I remember.

Hope it helps someone too.

Revision history for this message
gdesilva (gdesilva) wrote :

I also have been experiencing a similar problem to above.

I use a Dell Dimension 9150 desktop with a Dell bluetooth dongle and bluetooth keyboard and mouse. Everything worked fine in Jaunty. With Karmic, the keyboard and mouse works fine although I cannot get the bluetooth apps to work - no bluetooth adaptor found message.

rfkill list produces nothing. Device Manager states that the USB Bluetooth device in HID Proxy mode.

hciconfig hci0 up returns Can't get device message.

Any assistance is greatly appreciated.

Revision history for this message
gdesilva (gdesilva) wrote :

Hi, here is the output from dmesg | grep Bluetooth in my case;

[ 0.980013] Bluetooth: Core ver 2.15
[ 0.980033] Bluetooth: HCI device and connection manager initialized
[ 0.980033] Bluetooth: HCI socket layer initialized
[ 1.755664] Bluetooth: L2CAP ver 2.13
[ 1.755667] Bluetooth: L2CAP socket layer initialized
[ 1.755670] Bluetooth: SCO (Voice Link) ver 0.6
[ 1.755672] Bluetooth: SCO socket layer initialized
[ 1.755712] Bluetooth: RFCOMM TTY layer initialized
[ 1.755716] Bluetooth: RFCOMM socket layer initialized
[ 1.755719] Bluetooth: RFCOMM ver 1.11
[ 9.225542] Bluetooth: HIDP (Human Interface Emulation) ver 1.2

Revision history for this message
gdesilva (gdesilva) wrote :

For the benefit of those who are having the problem I was experiencing....here is the solution

Check out the post on http://ubuntu-ky.ubuntuforums.org/showthread.php?p=8298037

Essentially,

1. Remove dongle.
2. Press red dot. (reset button)
3. Insert dongle while the red dot is pressed and hold it down for a few seconds.

Hope this will help some of you who are having a problem similar to mine.

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

I opened separate issue for Dell Mini if the interface doesn't show up at all: https://bugs.launchpad.net/bugs/483713 .

Revision history for this message
Michalxo (michalxo) wrote :

Hello all, I am having an interesting bug. After I turn off my BT via software like here http://duopetalflower.blogspot.com/2009/10/ubuntu-karmic-has-option-for-turning.html , and restart X, logout.. I am unable to start my BT again. My bluetooth-applet is invisible/not active, so I can't wake it up again.
If I turn on BT in XP, it wakes up in ubuntu too.
Can anyone help me out? I think I "only" need a command line "aliver" :-)

Revision history for this message
maheshjagadeesan (maheshj) wrote :

I can confirm that starting the computer in Windows / other OS and enabling BT there reactivates BT on Ubuntu as well. Weird, but true.

Revision history for this message
Sergey K (koblin) wrote :

i still have this issue after updating to ubuntu 10.04 beta1

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Sergey,

please open a new bug (One bug per people please !!!), because this is certainly *NOT* the same problem than the reporter.
To open the bug, open a terminal and type "ubuntu-bug bluez".

Thanks

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Henry,

could I assume the bug is solved for you now?

Revision history for this message
Henry Gomersall (hgomersall) wrote :

@baptiste:
yes, its more or less working. The bluetooth is not always up after a suspend, but it can generally be jogged into working by disabling/reenabling through the menu. Its not ideal, but it is workable.

This is using Lucid Beta.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

As the original reporter confirmed this is okay I close this bug.
for other people, open a new bug each one of you.

Thanks

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