Description of problem: On boot: hcid[1907]: Bluetooth HCI daemon ............................ kernel: Bluetooth: HCI device and connection manager initialized kernel: Bluetooth: HCI socket layer initialized hcid[1907]: Can't connect to system message bus: Failed to connect to socket /var/run/ dbus/system_bus_socket: No such file or directory hcid[1907]: Unable to get on D-Bus kernel: Bluetooth: L2CAP ver 2.9 Version-Release number of selected component (if applicable): bluez-utils-3.30-2.fc9.i386 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: service bluetooth status hcid dead but subsys locked Expected results: Additional info: related to 430549. but if messagebus is running: service messagebus status dbus-daemon (pid 1937) is running... and I restart bluetooth: service bluetooth restart Stopping Bluetooth services: [FAILED] Starting Bluetooth services: [ OK ] all's well: service bluetooth status hcid (pid 12962) is running... Is initscripts starting bt too early?
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Please test with the 3.36 bluez updates.
I've gone on to another machine w/out bluetooth.