Bug 344209 - kded uses 100% with 4 monitors
Summary: kded uses 100% with 4 monitors
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.2.0
Platform: Arch Linux Linux
: NOR grave
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-15 21:28 UTC by Alexander Nestorov
Modified: 2015-02-15 22:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Nestorov 2015-02-15 21:28:59 UTC 
I have 2 NVIDIA GT6xx cards using nouveau driver and 4 monitors. The cards are not in SLI, so I use "xrandr --setprovideroutputsource 1 0" to make all monitors usable (see bug https://bugs.kde.org/show_bug.cgi?id=343900 ).

Anyways, as soon as I enable the 3rd and the 4th monitor, kded starts using 100% of 1 of my cores.

I'm leaving this as grave as my entire desktop is left in an unusable state when I enable all my monitors.

Reproducible: Always
Comment 1 Alexander Nestorov 2015-02-15 21:47:35 UTC 
I understand that such a setup is not that common and maybe no KDE devs can get such an environment to debug the bug, and as this is very important for me (it conflicts with my daily work needs) I'm willing to help debug. I will follow any guidance/steps you need me to do in order to get this fixed as soon as possible.

(Please don't get me wrong, I'd help debug all bugs I have reported and the ones other people have reported, but sadly I don't have the time).
Comment 2 Kai Uwe Broulik 2015-02-15 22:03:16 UTC 
Can you verify whether this comes from PowerDevil (ie. disable "Power Management" in System Settings → Startup and shutdown → Background services)? If so, this has been fixed for 5.2.1.
Comment 3 Alexander Nestorov 2015-02-15 22:06:47 UTC 
I disabled power management,, but the bug is still present.
Comment 4 Alexander Nestorov 2015-02-15 22:36:21 UTC 
Oh, actually that did fix the bug, I just had to reboot.