[kdelibs] [Bug 343682] New: After resuming, kded4 sometimes eat 100% CPU complaining about org.kde.bluedevilmonolithic

[Éric Brunet]

https://bugs.kde.org/show_bug.cgi?id=343682

            Bug ID: 343682
           Summary: After resuming, kded4 sometimes eat 100% CPU
                    complaining about org.kde.bluedevilmonolithic
           Product: kdelibs
           Version: unspecified
          Platform: Fedora RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: kded
          Assignee: unassigned-bugs at kde.org
          Reporter: eric.brunet at lps.ens.fr

My computer is an up-to-date fedora 21 box, with kde 4.14.3 and (maybe it's
relevant ?) still using kdm. [Side remark: bug tracking system did not propose
version 4.14.3].

Frequently (but not systematically), kded4 gets crazy when resuming the
computer from sleep:
* it eats 100% CPU
* the computer no longer responds to the fn-keys controlling volume,
luminosity, etc.
* kded4 writes at a high rate (order of magnitude: 1000 lines per second) on
its standard error the line
Error response:  "The name org.kde.bluedevilmonolithic was not provided by any
.service files" 

Killing kded4 and restarting it seems to fix the problem until the next time.

It only occurs on a suspend/resume cycle.

Sometimes, the problem appears after I have entered my password and the desktop
is up and running. Sometimes, it appears before I can enter my password; the
screen locker is then locked and I cannot enter my password. Sometimes
(rarely), the screen locker hasn't the time to show up: I see an inactive,
non-responding image of my desktop. 
In the two latter cases, I have to switch to a VT, log-in in text mode and kill
kded4 there. I can then go back to Xorg to enter my password in the
screenlocker, and launch again kded4.

Removing the file   /usr/share/kde4/services/kded/bluedevil.desktop  fixes my
problem, but I imagine I am loosing some functionality (I am not really using
bluetooth). This file belongs to the package bluedevil. I have had this problem
with bluedevil-2.1-1.fc21, and now again
with bluedevil-2.1-2.fc21 which I installed two days ago.

I really don't know how to debug further the interaction of kded4 with
bluedevil!

Reproducible: Sometimes

-- 
You are receiving this mail because:
You are the assignee for the bug.