Bug 448888

Summary: service bluetooth does not support chkconfig
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: bluez-utilsAssignee: David Woodhouse <dwmw2>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: bnocera, dcantrell, djuran, katzj, kszysiu, matthias_haase, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-07 09:48:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jóhann B. Guðmundsson 2008-05-29 10:05:44 UTC
Description of problem:

Got the Summary when updating to rawhide 29/05/2008



Version-Release number of selected component (if applicable):



How reproducible:

Always

Steps to Reproduce:
1. Update to rawhide
2.
3.
  
Actual results:

Error msg in yum's update process

Expected results:

No error msg
Additional info:

Comment 1 Kris Rusocki 2008-06-09 00:27:56 UTC
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 [755]:~$ grep -c chkconfig: /etc/init.d/bluetooth 
0
jackal 18:25 [756]:~$ 




Comment 2 Kris Rusocki 2008-06-09 00:29:22 UTC
Just wondering if that's intended...


Thanks,
Krzysztof


Comment 3 Jeremy Katz 2008-07-09 19:58:47 UTC
*** Bug 449789 has been marked as a duplicate of this bug. ***

Comment 4 Matthias Clasen 2008-08-24 03:00:09 UTC
Bastien, can you take care of this ?

Comment 5 Matthias Haase 2008-08-26 17:53:01 UTC
/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...

Comment 6 Bastien Nocera 2008-09-12 10:28:31 UTC
Fixed in rawhide in bluez-4.5-1.fc10. Update pushed for F9.

Comment 7 Fedora Update System 2008-09-14 06:50:07 UTC
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

Comment 8 Jesse Keating 2008-10-03 23:41:46 UTC
This is fixed for F10, removing it from the blocker, leaving the bug open for the F9 update.

Comment 9 Fedora Update System 2008-10-07 09:48:25 UTC
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.