Red Hat Bugzilla – Bug 448888
service bluetooth does not support chkconfig
Last modified: 2013-01-09 23:42:58 EST
Description of problem:
Got the Summary when updating to rawhide 29/05/2008
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update to rawhide
Error msg in yum's update process
No error msg
Seeing something somewhat similar in Fedora 9.
After installation, /etc/rc?.d/*bluetooth got '-1' priorities
[e.g. K-1bluetooth, S-1bluetooth].
jackal 18:25 :~$ grep -c chkconfig: /etc/init.d/bluetooth
jackal 18:25 :~$
Just wondering if that's intended...
*** Bug 449789 has been marked as a duplicate of this bug. ***
Bastien, can you take care of this ?
/etc/init.d/bluetooth has - unfortunately - an undefined chkconfig!
In result, bluetooth service does start always before messagebus...
(fc9 with all updates on a Thinkpad T40)
hicd requires running messagebus otherwise bluetooth service fails to start.
# chkconfig: 345 23 85
on top of /etc/init.d/bluetooth fixes wrong startup of this service.
It starts now after messagebus with right order...
There are several bug reports related to this...
Fixed in rawhide in bluez-4.5-1.fc10. Update pushed for F9.
bluez-utils-3.35-5.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update bluez-utils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-7239
This is fixed for F10, removing it from the blocker, leaving the bug open for the F9 update.
bluez-utils-3.35-5.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.