Description of problem: Using rawhide-20070904.0.iso on a usb stick, the bluetooth service is failing to start on boot. It succeeds if I start it manually after booting. Let me know if you need more information. Version-Release number of selected component (if applicable): bluez-utils-3.17-1.fc8
Can you describe exactly what it says when it fails to boot? Does it boot OK if you disable selinux?
It doesn't fail to boot. Bluetooth just fails to come up *on* boot. I can't try booting without selinux, as this is a live image. I retested on F8 Test 2 with the same results. 'service bluetooth status' after boot returns 'hcid dead but subsys locked'. 'service bluetooth start' starts bluetooth correctly.
OK, I have F8 Test 2 installed now. I booted with selinux=0, and nothing's changed.
Thinking the problem might be that bluetooth is started before dbus.
Zack also mentioned that he gets "Got disconnected from the system message bus" in /var/log/messages when started.
To clarify re: comment #5, I saw it once among the many times I've seen the problem. Maybe that message only gets triggered sometimes.
Some poking by wwoods reported on fedora-devel-list seems to support the problem being "bluetooth is started before dbus".
Yeah - as I mentioned on devel-list, changing the startup priority of bluetooth from 25 to 30 (messagebus is 28) seems to make bluetooth start up properly. bluetooth-applet still doesn't seem to start automatically, but that's a different bug. I also feel compelled to mention bug #222315 here (bluetooth daemons shouldn't be started from an initscript) but it's almost certainly too late in the release cycle for that.
*** Bug 251324 has been marked as a duplicate of this bug. ***
Ah - messagebus is *supposed* to have priority 22, but it has: Required-Start: $syslog $local_fs netfs provides $local_fs, and it has priority 25; rsyslog requires $local_fs, so it gets 26, which puts messagebus at 27. I suggest adding something like the following to /etc/init.d/bluetooth: ### BEGIN INIT INFO # Required-Start: $syslog messagebus # Default-Start: 2 3 4 5 # Short-Description: Bluetooth services # Description: Bluetooth services for service discovery, authentication, # Human Interface Devices, etc. ### END INIT INFO Then chkconfig can work it out by itself. I'm not sure if bluetooth needs to be explicitly stopped at shutdown - you might add a Default-Stop line if so.
Fixed in 3.20-1. Thanks for the help Will.