This enhancement request is a solution to Bug #129713 which presently affects me and is likely to affect others in the future. The scenario is as follows: >=baselayout-1.12.0_pre17 >=udev-089 bluez-utils emerged with "dbus" useflag The bluez-utils initscript (/etc/init.d/bluetooth) currently has an "after coldplug" dependency however udev-089, and later, implement coldplug internally effectively making this a noop. Under the environment detailed above, bluetooth services are started before dbus which causes hcid startup to fail when it is built with dbus support. The solution, which I have verified to work in my environment, is to supplement the existing "after coldplug" with "dbus" i.e. "after coldplug dbus". For some reason, this effect doesn't show for <baselayout-1.12.0_pre17 and I suspect that it came about with the implementation of the functionality that prints "Device initiated services: bluetooth net.eth0" in _pre17 and later but I have no detailed knowledge of those changes.
It has "after dbus" in the init script, don't see what are you requesting. *** This bug has been marked as a duplicate of 121979 ***
Let's dupe it against Bug 118786 which also discusses the coldplug issue.
*** This bug has been marked as a duplicate of 118786 ***
