Description of problem: After the current software upgrade to bluez, I've lost bluetooth. I installed a fresh copy of fc15 beta, and out of the box I had no bluetooth. I played around and used "systemctl enable bluetooth.service" to get the bluetooth daemon to start automatically. I had to manually start bluetooth-applet and for a while I had an active bluetooth light on my laptop and a bluetooth icon in gnome-shell. I had hooked up a bluetooth mouse. After a software upgrade on 4/19/2011 I lost bluetooth again and the above steps don't activate it either. "systemctl status bluetooth.service" reports: bluetooth.service - Bluetooth Manager Loaded: loaded (/lib/systemd/system/bluetooth.service) Active: active (running) since Wed, 20 Apr 2011 04:18:21 -0700; 28min ago Main PID: 1013 (bluetoothd) CGroup: name=systemd:/system/bluetooth.service └ 1013 /usr/sbin/bluetoothd -n And when I start bluetooth-applet manually on the command line it just hangs reporting nothing. Version-Release number of selected component (if applicable): bluez-4.87-3.fc15.x86_64 gnome-bluetooth-3.0.0-1.fc15.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
bluetooth-applet wouldn't do anything because gnome-shell has its own implementation, and we don't want both the gnome-shell and the bluetooth-applet showing up at the same time. In any case, bug should be fixed in an update shortly. *** This bug has been marked as a duplicate of bug 694519 ***