Bluetooth service needs to be restarted before a Bluetooth dongle works

[Michael Bewley]

Binary package hint: bluez

I can't turn bluetooth on with a dongle plugged in, unless I issue the command "sudo service bluetooth restart". This occurs when the dongle has been plugged in on starting up (I need to use a wired keyboard to log in), or when I plug in the dongle later. The dongle in question is the one attached at the time of the bug report (which was just after I issued the bluetooth restart command).
This is similar to Bug #762964 and #700292, but it isn't fixed yet with the latest updates installed (I believe my kernel version is the same as the kernel updates mentioned that fix it in some instances).
I also had a related problem with a logitech bluetooth dongle (for an MX5000 keyboard), where I discovered a workaround that I had to replug in the dongle while holding the red button to get it to work (I didn't try the bluetooth restart command).

I'm aware that I can just add a restart command in the rc.local file, but I'm trying to use "stock" ubuntu, as it's now in the league of a proper commercial OS! Let me know if you need any more info or troubleshooting steps.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: bluez 4.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue May 3 22:28:25 2011
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
InterestingModules: sco bnep l2cap btusb bluetooth
MachineType: System manufacturer P5K-VM
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=a5139a7b-604d-431d-b166-22dfc8047bfa ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to natty on 2011-04-28 (4 days ago)
dmi.bios.date: 06/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0902
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0902:bd06/20/2008:svnSystemmanufacturer:pnP5K-VM:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K-VM
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:15:83:44:57:07 ACL MTU: 384:8 SCO MTU: 64:8
  UP RUNNING
  RX bytes:356 acl:0 sco:0 events:13 errors:0
  TX bytes:53 acl:0 sco:0 commands:13 errors:0
rfkill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

[Mike Yates (fonehelp)]

My dongle was never a problem with 10.10 but would not P&P at all in 11.04 for the first three days.
Now it "usually" works if I start up with it inserted but never if inserted live.

usb-devices:-
T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev=52.76
C: #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

On failure:-
[ 435.656168] usb 2-2: USB disconnect, address 2
[ 435.657041] btusb_intr_complete: hci0 urb f1429300 failed to resubmit (19)
[ 435.657071] btusb_bulk_complete: hci0 urb f1429200 failed to resubmit (19)
[ 435.658041] btusb_bulk_complete: hci0 urb f1429180 failed to resubmit (19)
[ 435.658134] btusb_send_frame: hci0 urb f1f64800 submission failed
[ 443.560181] usb 2-2: new full speed USB device using uhci_hcd and address 3
[ 1523.136185] usb 2-2: USB disconnect, address 3
[ 1540.576160] usb 2-2: new full speed USB device using uhci_hcd and address 4

On success:-
[ 25.177801] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 25.231100] usbcore: registered new interface driver btusb
[ 25.644274] Bluetooth: L2CAP ver 2.15
[ 25.644284] Bluetooth: L2CAP socket layer initialized
[ 25.678833] cfg80211: World regulatory domain updated:
[ 25.678844] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 25.678855] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 25.678865] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 25.678875] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 25.678884] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 25.678894] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 25.701647] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 25.701656] Bluetooth: BNEP filters: protocol multicast
[ 25.734683] Bluetooth: SCO (Voice Link) ver 0.6
[ 25.734693] Bluetooth: SCO socket layer initialized
[ 25.924624] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 25.924640] i915 0000:00:02.0: setting latency timer to 64
[ 25.998449] Bluetooth: RFCOMM TTY layer initialized
[ 25.998464] Bluetooth: RFCOMM socket layer initialized
[ 25.998471] Bluetooth: RFCOMM ver 1.11
[ 26.087690] i915 0000:00:02.0: irq 44 for MSI/MSI-X
[ 26.087707] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 26.087714] [drm] Driver supports precise vblank timestamp query.
[ 26.200936] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 26.202981] [drm] initialized overlay support
[ 26.400079] ath9k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 26.400103] ath9k 0000:02:00.0: setting latency timer to 64
[ 26.452504] ath: EEPROM regdomain: 0x65
[ 26.452513] ath: EEPROM indicates we should expect a direct regpair map
[ 26.452524] ath: Country alpha2 being used: 00
[ 26.452529] ath: Regpair used: 0x65
[ 26.452720] cfg80211:...

[Mohd Farimi Ab Rahman (farimi)]

My workaround is to put

sudo service bluetooth start

in the Startup Aplication List.

Works for me, for now.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.