Red Hat Bugzilla – Bug 222315
bluetooth daemons shouldn't be started from an initscript
Last modified: 2011-04-27 09:00:36 EDT
Running the bluetooth daemons on machines without the hardware has little point.
We should just be starting them when hardware is attached (either as a hal
callout or a udev rule)
There will be singleton addons in HAL 0.5.10 (Out in 2-3 months) to handle this
- am working with Marcel and other Bluez developers. The only change, for this,
will be replacing the initscript with a HAL fdi file....
(there are other Bluez/HAL integration bits that will benefit from this too
(Bluez can claim HAL interfaces) but that is outside the scope of this bug.)
David, is there an open bug for that particular HAL feature? It would also be
useful for authentication hardware, so that they could modify the PAM
configuration, and start up helper services on-demand/when plugged in.
(In reply to comment #2)
> David, is there an open bug for that particular HAL feature? It would also be
> useful for authentication hardware, so that they could modify the PAM
> configuration, and start up helper services on-demand/when plugged in.
It's mentioned here
and is on track for 0.5.10. HTH.
Will we have this in time for Fedora 8?
Will it be possible to disable this behaviour? Just because bluetooth hardware
is available it doesn't mean that I always want to run the servers.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Still the case, still should be fixed
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
We use dbus activation to start up hcid in rawhide. It probably breaks quite a
few things. Please test and file bugs.
Clean F15 install, no bluetooth hardware, and the bluetooth service starts automatically during boot.
Should I file a different bug?