Red Hat Bugzilla – Bug 176522
Bluetooth daemons need to be started after D-Bus system bus
Last modified: 2013-03-13 00:49:34 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051216 Fedora/1.5-3 Firefox/1.5
Description of problem:
hcid needs to connect to the D-Bus system bus. Unfortunately, it hcid is started at priority 25 level and the D-Bus system bus isn't started until priority level 98. Since the D-Bus system bus isn't available when hcid is started it exits immediately.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. chkconfig bluetooth on
3. login and seen that hcid isn't running
Actual Results: Dec 23 10:04:09 lt16585 hcid: Bluetooth HCI daemon
Dec 23 10:04:09 lt16585 sdpd: Bluetooth SDP daemon
Dec 23 10:04:10 lt16585 hcid: Can't open system message bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Dec 23 10:04:10 lt16585 hcid: Unable to get on D-BUS
Expected Results: Dec 23 10:08:57 lt16585 hcid: Bluetooth HCI daemon
Dec 23 10:08:57 lt16585 sdpd: Bluetooth SDP daemon
Dec 23 10:08:57 lt16585 hcid: Registering DBUS Path: /org/bluez/Device/hci0
Dec 23 10:08:57 lt16585 hcid: HCI dev 0 up
Dec 23 10:08:57 lt16585 hcid: Starting security manager 0
Dec 23 10:08:57 lt16585 hcid: Registering DBUS Path: /org/bluez/Manager/default/Controller
Dec 23 10:08:57 lt16585 hcid: Registering DBUS Path: /org/bluez/Manager/hci0/Controller
I think we need to start dbus earlier.
*** Bug 176774 has been marked as a duplicate of this bug. ***
There probably should be an API in dbus to let you monitor when the bus becomes
active and goes away. This is probably not a blocker, though. Moving to target.
If bluetooth can't start up because dbus is starting too late, then that's a
blocker. I thought I saw a report that we'd started dbus earlier though --
although I don't see it in this bug or in bug #176774 at first glance.
Let's not let this bug evolve into the RFE you mention in comment #3 -- keep it
simply for "dbus ate my bluetooth dÃ¦mon", and please close it if that's no
longer true. Switching back to blocker.
There is an API. Setup a timeout when the bus goes away and check if you can
connect at each interval. BTW D-Bus now starts before bluetooth except there is
no way to relink already created init scripts with checkconfig so you will only
get it in a fresh install. I also filed a bug on expat (Bug #178743). It needs
to be moved to /lib since dbus requires it.
Is this a dupe of bug 104058 ?
*** This bug has been marked as a duplicate of 104058 ***
*** Bug 150921 has been marked as a duplicate of this bug. ***