Bug 118786 - bluetooth init.d should use dbus service when available
|
Bug#:
118786
|
Product: Gentoo Linux
|
Version: 2005.1
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: minor
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: cardoe@gentoo.org
|
Reported By: jan@spitalnik.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: bluetooth init.d should use dbus service when available
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-01-12 08:44 0000
|
Hi,
bluez-utils' bluetooth init.d should 'use dbus', as it can be compiled to
support dbus. In such scenario, bluetooth is started before dbus and hcid fails
to start.
I second the motion to fix this ASAP and shipout.
Noticed this problem as well. As a workaround I set dbus to start up at "boot"
softlevel.
However, if using bluez-2.24 with the udev rule, the bluetooth may start
immediately after coldplug regardless. So I thing dbus should also be set to
start before coldplug..
cc'ing dbus maintainer. can we have the above discussed before coldplug added
to dbus' init.d script?
i'll go about adding the required things into bluez-utils' init.d too
added "after dbus" to bluez-utils 2.25's init.d script. now just missing dbus's
init script to run before coldplug
reassigning for further action with the dbus init script.
hi, took me some time to figure this out :-\
net-wireless/bluez-utils-2.25 has the dbus issue
when can we expect a fix?
(In reply to comment #5)
> added "after dbus" to bluez-utils 2.25's init.d script. now just missing dbus's
> init script to run before coldplug
"after coldplug" is bogus w/ >=udev-089, it should be just removed from the
dbus init script when that version goes stable. Same for bluetooth init script.
*** Bug 130235 has been marked as a duplicate of this bug. ***
net-wireless/bluez-utils-2.25-r1 changes the init script to need dbus when
emerged with dbus support which fixes the initial bug report.
after coldplug should be removed from the init script when the coldplug package
is removed from portage.