Created attachment 491408 [details] Screenshot of bluetooth settings Description of problem: upon logging in, bluetooth is shown as disabled, yet the bluetooth service is shown as running. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. log in 2. open bluetooth settings and see that it is disabled. Actual results: Bluetooth is always disabled Expected results: Bluetooth is enabled upon logging in. Additional info: [root@larry-laptop1 larry]# systemctl status bluetooth.service bluetooth.service - Bluetooth Manager Loaded: loaded (/lib/systemd/system/bluetooth.service) Active: active (running) since Tue, 12 Apr 2011 01:35:57 -0400; 22min ago Main PID: 712 (bluetoothd) CGroup: name=systemd:/system/bluetooth.service └ 712 /usr/sbin/bluetoothd -n
a random install of gnome-tweak-tool and libre office without updates (none to install) seems to have magically made bluetooth 100% functional. weird.
It has done the same thing again. I noticed a coincidence- whenever the bluetooth (and other) icons show up as invisible until you hover over it, the bug occurs. when they always are visible, Bluetooth works fine.
odd... icons are still invisible but after a sleep and wakeup, bluetooth is live again. sounds like a possible start-up issue...
F15, the bluetooth icon in the top bar (systray?) says it's enabled, but when I click on it to open the "Bluetooth Settings" it says "Bluetooth is disabled". At the same time, I get this in the logs: ----------------------------------- Apr 18 14:25:56 mallory dbus: [system] Activating via systemd service name='org.bluez' unit='dbus-org.bluez.service' Apr 18 14:25:56 mallory dbus: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. ----------------------------------- # systemctl status bluetooth.service dbus-org.bluez.service bluetooth.service - Bluetooth Manager Loaded: loaded (/lib/systemd/system/bluetooth.service) Active: inactive (dead) CGroup: name=systemd:/system/bluetooth.service dbus-org.bluez.service Loaded: error Active: inactive (dead) ----------------------------------- I can restart bluetooth.service and it will say "active (running)" then, but enabling dbus-org.bluez.service still fails: # systemctl restart dbus-org.bluez.service Failed to issue method call: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. And with that, Bluetooth just does not work. Smolt profile: pub_6d9135bd-4735-430d-82f1-94d32e355fba
Hi, I have the same problem with an usb bluetooth adapter. When I plug in the device, the bluetooth applet tells me, that bluetooth is on, but it dos not work and the control-center tells me, it is off. Furthermore it is not possible to change the visibilty status from the bluetotth-applet's button # systemctl restart dbus-org.bluez.service Failed to issue method call: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details ------------------------------------ # systemctl restart bluetooth.service ------------------------------------ outout from # systemctl status bluetooth.service dbus-org.bluez.service bluetooth.service - Bluetooth Manager Loaded: loaded (/lib/systemd/system/bluetooth.service) Active: active (running) since Tue, 19 Apr 2011 15:46:22 +0200; 24s ago Main PID: 2591 (bluetoothd) CGroup: name=systemd:/system/bluetooth.service └ 2591 /usr/sbin/bluetoothd -n dbus-org.bluez.service Loaded: error Active: inactive (dead)
I'm seeing this problem, too, in Fedora 15 Beta.
Same problem here. Might be related to changes in bluetooth kernel interface. https://lkml.org/lkml/2011/3/19/80
Hey! Same problem here. Interesting note. If I start bluetoothd manually on the commandline and then run: hcitool scan hcitool correctly picks up that my bluetooth mouse is available for pairing So the underlying bluetooth infrastructure is working on my system. Please let me know if I can provide any additional information to help figure out what the problem is with the gnome UI. -jef
I have the same problem in Fedora 15 with KDE desktop - bluedevil says that no adapter is found on the system until I do 'systemctl enable bluetooth.service' and 'systemctl start bluetooth.service'.
Oded, I think that you have a separate issue. According to the original bug report here, the bluetooth service is shown as running. You may wish to open a separate report.
Same problem with fc15.x86_64
I had bluetooth.service disabled since I installed F15 around April 11. Had to run 'systemctl enable bluetooth.service' to make it work. Maybe there was problem around that time and the installation process didn't enable this service by default?
Recent updates have fixed this for me on the one laptop that was experiencing the problem. As of now I have two F15Beta+updates laptops installed both with working bluetooth support. I don't know which update fixed it...but as of today it appears to work. Paired with my Bluetooth mouse without a hitch today. -jef
I have problems with bluetooth too. But I am on Fedora 14. After a suspend or a long time of inactivity the Bluetooth turns off, although the icon show it's on. I have to start it from services (in there I can see it's enabled, but I have to click on start) and then it works. This problem appeared in FC14, before in FC13 it was working fine.
Same here, I guess. This appears in /var/log/messages when I open bluetooth settings: May 16 22:01:46 snowball2 dbus: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' May 16 22:01:46 snowball2 dbus: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. May 16 22:01:46 snowball2 dbus: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' May 16 22:01:46 snowball2 dbus: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status' for details. systemctl shows the following: $ sudo systemctl status dbus-org.bluez.service [sudo] password for julas: dbus-org.bluez.service Loaded: error Active: inactive (dead)
The problem is that bluez wasn't getting enabled under systemd, even when it was under upstart. If you upgraded from F14 already (and that's why you would have the problem), simply run: /bin/systemctl enable bluetooth.service as root. And that should fix the problem permanently. If you want to avoid rebooting for now, unplug/replug the Bluetooth adapter, or run: /bin/systemctl start bluetooth.service Now listed in the common bugs: https://fedoraproject.org/wiki/Common_F15_bugs#Bluetooth_not_working_after_upgrade_to_F15_Beta *** This bug has been marked as a duplicate of bug 694519 ***
http pages been impersonated