Description of problem: After booting the system, bluetooth is disabled, and the bluedevil-monolithic systray icon has a grey background. Bluetooth peripherals does not work until you manually enable it using bluedevil-monolithic's systray icon menu. The same thing happens after suspend/resume; if you manually enable bluetooth, then suspend/resume, it has become disabled again. Version-Release number of selected component (if applicable): bluedevil-2.0.0-1.fc21.x86_64 libbluedevil-2.0-1.fc21.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot up system and log in 2. Enable bluetooth 3. Suspend system 4. Resume system Actual results: After steps #1 and #4, bluetooth is disabled, the bluedevil systray icon has a grey background and no bluetooth peripherals work. Expected results: Bluetooth should be enabled after steps #1 and #4 and bluetooth peripherals should work with no further actions. Additional info: This is a regression, as the previous versions worked perfectly and enabled bluetooth automatically after bootup and resume: bluedevil-2.0.0-0.15.36f0438agit20140630.fc21.x86_64 libbluedevil-2.0-0.10.rc1.fc21.x86_64 Downgrading to these versions fixes the problem. Another point worth mentioning is that after booting up and enabling bluetooth from the systray menu, if you go into the bluetooth configuration dialogue box, there is a notification saying "Bluetooth is not completely enabled", with a associated button saying "Fix it". If you click this button, suspend/resume will start working normally again, i.e., after resuming, bluetooth will be enabled and peripherals works. However this fix, whatever it is, does not survive a reboot, so after a reboot you're back to square one.
The "Bluetooth is not completely enabled" message probably holds more clues as to what is going wrong here. I'll see if I can find it in the sources for more details.
m_noKDEDRunning->setText(i18n("Bluetooth is not completely enabled.")); It would appear bluedevil things the kded4 daemon isn't running when that message is displayed. Can you verify when the bluedevil systray icon is grey, run this: qdbus org.kde.kded /modules/bluedevil isOnline
I tested some more now. With the old version ==================== After booting, and the icon is blue and bluetooth work: $ qdbus org.kde.kded /modules/bluedevil isOnline Service 'org.kde.kded' does not exist. I notice that the message "Bluetooth is not completely enabled" is also shown with the old version. If I press the "fix it" button: $ qdbus org.kde.kded /modules/bluedevil isOnline true With the new (broken) version ============================= After booting, and the icon is gray and bluetooth does not work: $ qdbus org.kde.kded /modules/bluedevil isOnline Service 'org.kde.kded' does not exist. After enabling bluetooth from the menu I get when clicking on that icon (at this point bluetooth actually starts working and my peripherals work and so on): tore@envy:~$ qdbus org.kde.kded /modules/bluedevil isOnline Error: org.freedesktop.DBus.Error.UnknownObject No such object path '/modules/bluedevil' After clicking the "fix it" button in the settings: tore@envy:~$ qdbus org.kde.kded /modules/bluedevil isOnline true It's probably worth mentioning that I am not running KDE, but LXDE. I notice that the settings window contains a toggle "Enable KDE Bluetooth Integration". If I deselect this and try again, I no longer get shown the "Bluetooth is not completely enabled" message and the "fix it" button does not appear. However this does not help towards working around the problem, as bluetooth still remains disabled after boot and resume. Tore
OK, looks like kded4 daemon is crashing or exiting on it's on, for some reason.
The kded4 doesn't start at login in LXDE, as far as I can tell. The old bluedevil version didn't have any problems with that though... Tore
*** Bug 1186472 has been marked as a duplicate of this bug. ***
Somewhat similar symptomps here. Lenovo X1 carbon, but I am running KDE. I had to bisect all my January upgrades to find the culprit which turned out to be bluedevil (the lib didn't trigger anything and I'm in fact now running f21 with only the bluedevil left out and things run smoothly). My symptoms are that 2nd or 3rd resume from a fresh boot causes kded4 and dbus-daemon to run amok, both hogging about 50%. This lasts about 30 seconds after which things quiet down, but a huge portion of kde functionality is gone.
bluedevil-2.1-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/bluedevil-2.1-4.fc21
Package bluedevil-2.1-4.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bluedevil-2.1-4.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2297/bluedevil-2.1-4.fc21 then log in and leave karma (feedback).
bluedevil-2.1-4.fc21 does *not* fix this issue, in fact I cannot tell any difference in behaviour from bluedevil-2.0.0-1.fc21. Bluetooth is disabled after boot-up, and will be disabled again after resume (unless the "fix it" button in the settings has been pressed before suspending). Tore
bluedevil-2.1-4.fc21.x86_64 did fix my issues from the #1186472.
(In reply to Tommi Kyntola from comment #7) > My symptoms are that 2nd or 3rd resume from a fresh boot causes kded4 and > dbus-daemon to run amok, both hogging about 50%. This lasts about 30 seconds > after which things quiet down, but a huge portion of kde functionality is > gone. I also was running KDE on Fedora 21 and had this experience. It took me a long time to notice the flood of "The name org.kde.bluedevilmonolithic was not provided by any .service files" messages in ~/.xsession-errors, which led me to https://bugs.kde.org/show_bug.cgi?id=343682, which led me to bluedevil-2.1-4.fc21, which led me to bug 1186472. I don't even use bluetooth, but my system has been upgraded F16 -> F17 -> F19 -> F21 so I wouldn't know what unwanted services are enabled. This was a pretty critical bug for me because I need my machine to be able to lock when I hit the lock key combination, and suspend when I close the lid. (In reply to Tommi Kyntola from comment #11) > bluedevil-2.1-4.fc21.x86_64 did fix my issues from the #1186472. Same for me. I made no other package changes in the last 10 days other than installing clamav which should have had no effect, and installing this bluedevil update has made all the showstopper KDE issues go away for me.
bluedevil-2.1-4.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
This bug is *not* fixed, cf. comment #10. Re-opening. (Bug #1186472 might well be fixed, but that's a separate issue entirely which has mistakenly been marked as a duplicate of this one.) Tore
Adjusting summary.
In Fedora 22 (bluedevil-5.3.0-1.fc22.x86_64), bluedevil-monolithic no longer exist. Therefore, this bug is probably not applicable any more - I'm not sure if it's possible to run bluedevil outside of KDE anymore at all. I switched to using blueman instead, for what it's worth. Closing the bug.