Bluetooth is disabled. Pressing "Turn on bluetooth" not working

Bug #554431 reported by Yotam Benshalom
98
This bug affects 21 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: bluez

Lucid on Dell xps studio 1340.
After the updates of April 1-3, bluetooth icon appears grayed out. Clicking it states that bluetooth is on. Using preferences and pressing the button "Turn on Bluetooth" makes the button go gray, but nothing more. Basically this is identical behavior to bug #441800, which is supposedly fixed.
I will be happy to supply further details if necessary.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluez 4.60-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Sat Apr 3 07:15:29 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterestingModules: sco bnep l2cap btusb bluetooth
MachineType: Dell Inc. Studio XPS 1340
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=c3257748-07cc-46a6-baa4-f0f5d8b79d53 ro quiet splash
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0K183D
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.asset.tag: 1234567890
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A11
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0K183D:rvrA11:cvnDellInc.:ct8:cvrA11:
dmi.product.name: Studio XPS 1340
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: USB
  BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
  DOWN
  RX bytes:6 acl:0 sco:0 events:1 errors:0
  TX bytes:24 acl:0 sco:0 commands:8 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

Revision history for this message
Yotam Benshalom (benshalom) wrote :
Revision history for this message
Yotam Benshalom (benshalom) wrote :

Well, this sorted itself out after two reboots. Invalid :)

Changed in bluez (Ubuntu):
status: New → Invalid
Revision history for this message
arkmundi (rkerver) wrote :

I just upgraded to 10.04 and had the same problem on my Dell Inspiron 1525, bluetooth showing the message "bluetooth is disabled". Found here and the last message "sorted itself out after two reboots." So rebooted that second time. Am confirming the problem went away. :)

Revision history for this message
Eric Hammond (esh) wrote :

I just had the same problem on a fairly new installation of Ubuntu 10.04 Lucid on a Dell Latitude E6500.

I'm not sure that "two reboots" is an acceptable workaround for the general public.

Changed in bluez (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Eric Hammond (esh) wrote :

One reboot fixed the problem on my system (so that bluetooth is now enabled and on), but this issue should still be corrected so that new Ubuntu users do not run into a big "Turn on bluetooth" button that does not work.

Revision history for this message
Cosmin L (lcosmin) wrote :

This also affects me, although rebooting does not help. (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/599578)

Revision history for this message
aviram (avibrazil) wrote :

I have the same problem on 10.10.

Rebooting does not make it work.

Revision history for this message
aviram (avibrazil) wrote :

By the way, this is not the first bug I report here with absolutely no response from some support team.

Fedora is not like this... the community is obssessed by closing bugs.

Revision history for this message
mdmcginn (mcweb) wrote :

Was working before I rebooted.

Revision history for this message
mdmcginn (mcweb) wrote :

sudo hcidump -XYt > $HOME/hci.log
sudo: hcidump: command not found

Unplugging and replugging my USB Bluetooth dongle fixed the problem.

Revision history for this message
James Valentine (jamesdavidvalentine) wrote :

Rather than rebooting (I hate restarting my session), this worked for me:

sudo modprobe -r btusb
sudo modprobe btusb

You might also want to try this before those commands:

sudo /etc/init.d/bluetooth restart

Revision history for this message
cabruca (valeriomelo) wrote :

Hi People, what's the solution?

Thanks!!!!

Revision history for this message
Andrey Andreev (andyceo) wrote :

In my case, the solution was: enter the notebook into the sleep mode and then resume it.

Notebook Dell Inspiron 1525, Ubuntu 10.10.

Revision history for this message
Ákos Maróy (akos-maroy) wrote :

bluetooth doesn't work for me either, and no number of reboots makes it work. restarting /etc/init.d/bluetooth, or re-loading the module doesn't help. this is on 10.10 64 bit - bluetooth used to work on 10.04 and 09.10. this is on an HP Envy 15.

when unloading / reloading the btusb modile, I get:

May 8 09:45:02 tonkachi kernel: [ 1429.392530] Bluetooth: Core ver 2.15
May 8 09:45:02 tonkachi kernel: [ 1429.392597] NET: Registered protocol family 31
May 8 09:45:02 tonkachi kernel: [ 1429.392599] Bluetooth: HCI device and connection manager initialized
May 8 09:45:02 tonkachi kernel: [ 1429.392601] Bluetooth: HCI socket layer initialized
May 8 09:45:02 tonkachi kernel: [ 1429.395574] Bluetooth: Generic Bluetooth USB driver ver 0.6
May 8 09:45:02 tonkachi kernel: [ 1429.395598] usbcore: registered new interface driver btusb

when pussing the 'turn on bluetooth' button, I get:

May 8 09:45:13 tonkachi kernel: [ 1440.720397] ACPI Error: Needed [Buffer/String/Package], found [Integer] ffff880233a47af8 (20100428/exresop-590)
May 8 09:45:13 tonkachi kernel: [ 1440.720411] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20100428/dswexec-460)
May 8 09:45:13 tonkachi kernel: [ 1440.720425] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.WMID.HWMC] (Node ffff880236c590e0), AE_AML_OPERAND_TYPE
May 8 09:45:13 tonkachi kernel: [ 1440.720538] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.WMID.WMAD] (Node ffff880236c591e0), AE_AML_OPERAND_TYPE

Revision history for this message
Geert (geert-x) wrote :

Same issue over here with an HP DM1 and Ubuntu 11.4 64bit (actually Mint 11), rebooting doesn't help. Workaround is to restart bluetooth with this command after each boot: sudo /etc/init.d/bluetooth restart

Revision history for this message
nicholas5 (nick-fellows) wrote :

I am also experiencing this problem , this is in addition to the following :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443873

(XPS15 9530)

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yotam,

Thank you for reporting this bug to Ubuntu. Ubuntu 10.04 (lucid) reached EOL on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please upgrade to the latest version and re-test.

Changed in bluez (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for bluez (Ubuntu) because there has been no activity for 60 days.]

Changed in bluez (Ubuntu):
status: Incomplete → Expired
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.