/usr/sbin/bluetoothd doesn't get started automatically

Bug #589464 reported by Vinod on 2010-06-04
This bug affects 6 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)

Bug Description

Binary package hint: bluez

Lucid Lynx. When I reboot, bluetooth-applet says that Bluetooth is on, but the icon is greyed out and it doesn't include any of the options to send files, etc (attaching a screenshot of bluetooth menu). Toggling it on and off has no effect. I've also noticed that bluetoothd is not running. If I start bluetoothd manually, then everything works fine.

So, for some reason bluetoothd is not getting started properly, but I don't know how to diagnose further.


ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluez 4.60-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-22.35-generic
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Thu Jun 3 20:36:55 2010
ExecutablePath: /usr/sbin/bluetoothd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: ASUSTeK Computer INC. 1000
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=bd33138b-199c-4b7b-a000-d26406f80f15 ro quiet splash
 PATH=(custom, no user)
SourcePackage: bluez
dmi.bios.date: 07/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0702
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd07/14/2008:svnASUSTeKComputerINC.:pn1000:pvrx.x:rvnASUSTeKComputerINC.:rn1000:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
 hci0: Type: USB
  BD Address: 00:15:AF:FA:0E:DF ACL MTU: 1021:8 SCO MTU: 64:1
  RX bytes:1025 acl:0 sco:0 events:36 errors:0
  TX bytes:1597 acl:0 sco:0 commands:36 errors:0

Vinod (vinod-kurup) wrote :
Sergius (stadnik-sergey) wrote :

It happens to me with the same effect, but only after a hibernate/restore cycle.
It appears that bluetooth subsystem is started from /etc/init.d/bluetooth via sending a Dbus message to the bluetooth subsystem. For some reason /sbin/bluetoothd fails to start. /etc/init.d/bluetooth stop and then start cycle has no effect either. Only when I manually start bluetoothd everything starts working.

Erik Quaeghebeur (equaeghe) wrote :

Kubuntu 10.04 using blueman. When blueman applet has been used to set bluetooth off, then bluetoothd is not running after a restart.

Symptom: blueman applet icon in tray dissapears right after startup when bluetooth is set to off.

Workaround: start bluetoothd manually when bluetooth is needed.

Expected behavior: bluetoothd runs (at least) whenever blueman does, so that blueman on its own can be used to set bluetooth to on.

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.

Changed in bluez (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers