[Powerdevil] [Bug 337674] kded5 is eating CPU

[Christoph Feck via KDE Bugzilla]

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

--- Comment #88 from Christoph Feck  ---
Please check which kded module is responsible. You can disable them in the
SystemSettings Service Manager.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Trioxin via KDE Bugzilla]

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

Trioxin  changed:

   What|Removed |Added

 CC||tomash...@protonmail.com

--- Comment #87 from Trioxin  ---
Not verified fixed for me. kded5 is killing my CPU at a constant 25%.

Kubuntu 15.10
Plasma: 5.4.2
QT: 5.4.2

Debug info: http://hastebin.com/uqoriyuhoq.avrasm

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #86 from mif...@gmail.com ---
(In reply to Francesco from comment #85)
> Same here, same bt. Powerdevil 5.5.3 on gentoo amd64.
Oh, yep, I use Gentoo too, ~amd64 profile.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Francesco via KDE Bugzilla]

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

Francesco  changed:

   What|Removed |Added

 CC||palmar...@unive.it

--- Comment #85 from Francesco  ---
(In reply to miflab from comment #84)

> Well, now it eats ~40% with same bt. And here still only one kded5 process.
> I no have any ideas what's going on...

Same here, same bt. Powerdevil 5.5.3 on gentoo amd64.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #84 from mif...@gmail.com ---
Created attachment 96551
  --> https://bugs.kde.org/attachment.cgi?id=96551=edit
screenshot

Well, now it eats ~40% with same bt. And here still only one kded5 process.
I no have any ideas what's going on...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #82 from mif...@gmail.com ---
Created attachment 96361
  --> https://bugs.kde.org/attachment.cgi?id=96361=edit
bt

And another bt...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #83 from Martin Klapetek  ---
Can you check if you have 2 kded5 processes running?
Your backtrace again shows no activity at all.

That said, please compare the backtrace with the previous ones
before you upload a new one, there's no point uploading the same
backtrace again and again.

Lastly, the only thing of interest in the backtrace is libvlc+alsa,
hard to tell where is this coming from though.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #80 from mif...@gmail.com ---
(In reply to Martin Klapetek from comment #79)
> Can you check if you have 2 kded5 processes running?
Not sure, this issue is very random, but i'll try.
Also I notice that after do `sudo gdb --pid` cpu usage slightly decrease and
after quit this back to 25%.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #81 from Martin Klapetek  ---
> Also I notice that after do `sudo gdb --pid` cpu usage slightly decrease and 
> after quit this back to 25%.

Yes, attaching gdb to it makes the process actually stop,
quitting gdb makes the process continue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #79 from Martin Klapetek  ---
Can you check if you have 2 kded5 processes running?
Your backtrace again shows no activity at all.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #77 from mif...@gmail.com ---
Created attachment 96117
  --> https://bugs.kde.org/attachment.cgi?id=96117=edit
thread apply all bt

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #78 from mif...@gmail.com ---
(In reply to Martin Klapetek from comment #75)
> Are you sure this is when the kded5 process is eating the cpu?
Yep today I got this again. I attached screenshoot and new bt.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #76 from mif...@gmail.com ---
Created attachment 96116
  --> https://bugs.kde.org/attachment.cgi?id=96116=edit
kded5 cpu usage

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #75 from Martin Klapetek  ---
Thanks, pasting it here. Always please either attach the file here or paste it
directly here, pastebins tend to disappear. That said, your backtrace looks
absolutely normal, there's nothing wrong going on (in fact there is /nothing/
going on). Are you sure this is when the kded5 process is eating the cpu?

---

(gdb) thread apply all bt

Thread 5 (Thread 0x7ff9a51c5700 (LWP 22153)):
#0  0x7ff9b537832d in poll () from /lib64/libc.so.6
#1  0x7ff9b4ae3ac2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7ff9b4ae572f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7ff9a6cfdcb9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7ff9b56d4082 in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7ff9b31f2444 in start_thread () from /lib64/libpthread.so.0
#6  0x7ff9b538130d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7ff993318700 (LWP 0)):
#0  0x7ff9b537832d in poll () from /lib64/libc.so.6
#1  0x7ff9b249deec in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff9b249dffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff9b58cb847 in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib64/libQt5Core.so.5
#4  0x7ff9b587d41a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7ff9b56cf6d4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7ff9b56d4082 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7ff9b31f2444 in start_thread () from /lib64/libpthread.so.0
#8  0x7ff9b538130d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7ff9835e7700 (LWP 29419)):
#0  0x7ff9b31f83b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7ff983dbb8eb in vlc_cond_timedwait () from /usr/lib64/libvlccore.so.8
---Type  to continue, or q  to quit---
#2  0x7ff983d7e07c in ?? () from /usr/lib64/libvlccore.so.8
#3  0x7ff983d7eb55 in ?? () from /usr/lib64/libvlccore.so.8
#4  0x7ff9b31f2444 in start_thread () from /lib64/libpthread.so.0
#5  0x7ff9b538130d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ff980137700 (LWP 29421)):
#0  0x7ff9b5382b27 in semop () from /lib64/libc.so.6
#1  0x7ff98366afd7 in ?? () from /usr/lib64/libasound.so.2
#2  0x7ff983639196 in snd_pcm_recover () from /usr/lib64/libasound.so.2
#3  0x7ff9900261bf in ?? () from
/usr/lib64/vlc/plugins/audio_output/libalsa_plugin.so
#4  0x7ff983d98f83 in ?? () from /usr/lib64/libvlccore.so.8
#5  0x7ff983d6cc12 in ?? () from /usr/lib64/libvlccore.so.8
#6  0x7ff983d6e06b in ?? () from /usr/lib64/libvlccore.so.8
#7  0x7ff9b31f2444 in start_thread () from /lib64/libpthread.so.0
#8  0x7ff9b538130d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff9b6a8e800 (LWP 22151)):
#0  0x7ff9b537832d in poll () from /lib64/libc.so.6
#1  0x7ff9b249deec in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ff9b249dffc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff9b58cb847 in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib64/libQt5Core.so.5
#4  0x7ff9b587d41a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7ff9b58846fc in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#6  0x7ff9a6db5c88 in kdemain () from /usr/lib64/libkdeinit5_kded5.so
---Type  to continue, or q  to quit---
#7  0x00408560 in ?? ()
#8  0x0040594d in main ()
(gdb)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

--- Comment #74 from mif...@gmail.com ---
bt here - http://pastebin.com/dxUkvRMx
kde-frameworks/kded 5.16.0
kde-plasma/plasma-desktop 5.5.0
kde-plasma/powerdevil 5.5.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek via KDE Bugzilla]

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

--- Comment #73 from Martin Klapetek  ---
Please follow the steps from Comment #8.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[via KDE Bugzilla]

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

mif...@gmail.com changed:

   What|Removed |Added

 CC||mif...@gmail.com

--- Comment #72 from mif...@gmail.com ---
I have same issue (25% CPU usage of kded5) on my plasma 5.4.3.
kde-frameworks/kded 5.16.0
kde-plasma/plasma-desktop 5.4.3
kde-plasma/powerdevil 5.4.3

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Jürgen Scholz]

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

--- Comment #71 from Jürgen Scholz juergen.scholz...@gmail.com ---
I am kind of late to the party. Ubuntu updated it's packages a while ago and
everything is running smoothly now.

Thank you very much for all your work! :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Jürgen Scholz]

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

--- Comment #68 from Jürgen Scholz juergen.scholz...@gmail.com ---
I updated to new versions of kded5 and plasma-desktop/plasma-framework a few
days ago. The versions are now:
  kded (5.7.0-0ubuntu1) vivid; urgency=medium
  plasma-desktop (4:5.2.0-0ubuntu1) vivid; urgency=medium
  plasma-framework (5.7.0-0ubuntu1) vivid; urgency=medium

Turning off power saving of the monitors seems to be an effective work-around.

If I turn energy management back on, kded5 is starting to use one cpu core
again.

I will attach another gdb stack trace.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Jürgen Scholz]

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

--- Comment #69 from Jürgen Scholz juergen.scholz...@gmail.com ---
Oh, please excuse my oversidght. ubuntu still uses 5.2.0 and *not* 5.2.1. I
will check their bugtracker to either fix this as a backport or to switch to
5.2.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Christoph Feck]

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

--- Comment #70 from Christoph Feck cf...@kde.org ---
This bug was fixed for 5.2.1, so there is no need to attach log files from
5.2.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Nick Shaforostoff]

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

Nick Shaforostoff sha...@ukr.net changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #66 from Nick Shaforostoff sha...@ukr.net ---
i have compiled powerdevil and placed two .so libraries that were present in
bactraces into the system, rebooted and now issue is gone.

both on external monitor connect and screenlocker launch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Christoph Feck]

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

--- Comment #65 from Christoph Feck cf...@kde.org ---
 Can I help with additional information/tests to diagnose the issue?

Yes, test Plasma 5.2.1, since this will contain the commit from yesterday (see
comment #62).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Nick Shaforostoff]

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

--- Comment #59 from Nick Shaforostoff sha...@ukr.net ---
yeah, generally kde5 became slower on my netbook. it takes 5 seconds for alt+f2
runner to start reacting to my input, it takes ~5 seconds for start menu and
simple alt+tab switcher to appear, and it takes ~5-10 seconds just to show
session-end/reboot/poweroff confirmation screen.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Hrvoje Senjan]

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

--- Comment #60 from Hrvoje Senjan hrvoje.sen...@gmail.com ---
kded5 bt w/ Davids patch:

#0  0x7f505a91685f in pthread_cond_wait@@GLIBC_2.3.2 ()
at /lib64/libpthread.so.0
#1  0x7f505b89796b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0xd11fe0) at
thread/qwaitcondition_unix.cpp:128
#2  0x7f505b89796b in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0xd11fc8, mutex=mutex@entry=0xd11fa0,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:200
#3  0x7f505b89657e in QThread::wait(unsigned long) (this=this@entry=
0x7fffac915880, time=time@entry=18446744073709551615)
at thread/qthread_unix.cpp:670
#4  0x7f502ad73462 in PowerDevilUPowerBackend::kjobExecInThread(KJob*)
(job=job@entry=0xd95ed0)
at
/home/hrvoje/Src/local/powerdevil/daemon/backends/upower/powerdevilupowerbackend.cpp:594
#5  0x7f502ad73576 in
PowerDevilUPowerBackend::brightnessValue(PowerDevil::BackendInterface::BrightnessControlType)
const (this=
0xb6d580, type=optimized out)
at
/home/hrvoje/Src/local/powerdevil/daemon/backends/upower/powerdevilupowerbackend.cpp:308
#6  0x7f502ad710cd in PowerDevilUPowerBackend::init() (this=optimized
out) at
/home/hrvoje/Src/local/powerdevil/daemon/backends/upower/powerdevilupowerbackend.cpp:182
#7  0x7f502ab215db in
PowerDevil::Core::loadCore(PowerDevil::BackendInterfac---Type return to
continue, or q return to quit---
e*) (this=0xcb51a0, backend=backend@entry=0xb6d580)
at /home/hrvoje/Src/local/powerdevil/daemon/powerdevilcore.cpp:87
#8  0x7f502ad649bc in KDEDPowerDevil::init() (this=0xc87670)
at /home/hrvoje/Src/local/powerdevil/daemon/kdedpowerdevil.cpp:89
#9  0x7f505baa1506 in QObject::event(QEvent*) (this=0xc87670, e=optimized
out) at kernel/qobject.cpp:1245
#10 0x7f505c72fb5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x8a9bf0, receiver=receiver@entry=0xc87670, e=e@entry=
0xc74760) at kernel/qapplication.cpp:3722
#11 0x7f505c734bc0 in QApplication::notify(QObject*, QEvent*) (this=
0x7fffac916350, receiver=0xc87670, e=0xc74760)
at kernel/qapplication.cpp:3505
#12 0x7f505ba70e55 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=0x7fffac916350, receiver=0xc87670, event=event@entry=0xc74760)
at kernel/qcoreapplication.cpp:930
#13 0x7f505ba72cef in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (event=0xc74760, receiver=optimized out)
at kernel/qcoreapplication.h:228
#14 0x7f505ba72cef in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0,
data=0x8a9d60) at kernel/qcoreapplication.cpp:1534
#15 0x7f505ba73328 in QCoreApplication::sendPostedEvents(QObject*, int)
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
---Type return to continue, or q return to quit---
at kernel/qcoreapplication.cpp:1392
#16 0x7f505bac8d23 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0x91bed0) at kernel/qeventdispatcher_glib.cpp:271
#17 0x7f5059c97a04 in g_main_context_dispatch ()
at /usr/lib64/libglib-2.0.so.0
#18 0x7f5059c97c48 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x7f5059c97cec in g_main_context_iteration ()
at /usr/lib64/libglib-2.0.so.0
#20 0x7f505bac819c in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=0x9105c0, flags=...)
at kernel/qeventdispatcher_glib.cpp:418
#21 0x7f505ba6edab in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)
(this=this@entry=0x7fffac916280, flags=..., flags@entry=...)
at kernel/qeventloop.cpp:204
#22 0x7f505ba76436 in QCoreApplication::exec() ()
at kernel/qcoreapplication.cpp:1183
#23 0x7f505dfcf73a in kdemain () at /usr/lib64/libkdeinit5_kded5.so
#24 0x7f505dc48b45 in __libc_start_main () at /lib64/libc.so.6
#25 0x004007ee in _start ()

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[David Edmundson]

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

--- Comment #61 from David Edmundson k...@davidedmundson.co.uk ---
Thanks for testing.

It seems the only solution will be to remove these blocking KAuth calls
throughout this function. It's a wrong thing to be doing from kded.

I suggest we query brightnessValueMax in init();
and use m_cachedBrightnessMap for both the getters.

For the set case, we don't really need to wait for a reply. Is the error code
really that useful?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Hrvoje Senjan]

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

--- Comment #58 from Hrvoje Senjan hrvoje.sen...@gmail.com ---
from short testing the patch seems to resolves the CPU problem.
however:
1) for locking the screen, it now takes some 30s to actually show the locker,
2) konsole action (right click) is blocked with:

0  0x7f6f482e94ad in poll () at /lib64/libc.so.6
#1  0x7f6f3bf1926a in  () at /lib64/libdbus-1.so.3
#2  0x7f6f3bf180bf in  () at /lib64/libdbus-1.so.3
#3  0x7f6f3bf025bc in  () at /lib64/libdbus-1.so.3
#4  0x7f6f3bf02f69 in  () at /lib64/libdbus-1.so.3
#5  0x7f6f3bf0352d in dbus_connection_send_with_reply_and_block ()
at /lib64/libdbus-1.so.3
#6  0x7f6f42666780 in QDBusConnectionPrivate::sendWithReply(QDBusMessage
const, int, int) (error=0x7fff89162670, timeout_milliseconds=-1,
message=0x2077aa0, connection=optimized out) at qdbus_symbols_p.h:135
#7  0x7f6f42666780 in QDBusConnectionPrivate::sendWithReply(QDBusMessage
const, int, int) (this=
0x206b910, message=..., sendMode=optimized out, timeout=-1)
at qdbusintegrator.cpp:2046
#8  0x7f6f426533c3 in QDBusConnection::call(QDBusMessage const,
QDBus::CallMode, int) const (this=this@entry=0x23e2b10, message=...,
mode=mode@entry=QDBus::Block, timeout=optimized out) at
qdbusconnection.cpp:576
#9  0x7f6f426717ef in
QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const,
QListQVariant const) (this=this@entry=0x7fff891629b0, mode=QDBus::Block,
mode@entry=QDBus::AutoDetect, method=..., args=...)
at qdbusabstractinterface.cpp:476
#10 0x7f6f426725b5 in QDBusAbstractInterface::call(QDBus::CallMode, QString
const, QVariant const, QVariant const, QVariant const, QVariant const,
QVar---Type return to continue, or q return to quit---
iant const, QVariant const, QVariant const, QVariant const)
(this=this@entry=0x7fff891629b0, mode=mode@entry=QDBus::AutoDetect, method=...,
arg1=..., arg2=..., arg3=..., arg4=..., arg5=..., arg6=..., arg7=..., arg8=...)
at qdbusabstractinterface.cpp:746
#11 0x7f6f42672771 in QDBusAbstractInterface::call(QString const, QVariant
const, QVariant const, QVariant const, QVariant const, QVariant const,
QVariant const, QVariant const, QVariant const)
(this=this@entry=0x7fff891629b0, method=..., arg1=..., arg2=..., arg3=...,
arg4=..., arg5=..., arg6=..., arg7=..., arg8=...) at
qdbusabstractinterface.cpp:689
#12 0x7f6f433c783c in KIO::favIconForUrl(QUrl const) (url=...)
at /usr/src/debug/kio-5.7.0git/src/core/global.cpp:339
#13 0x7f6f433c8085 in KIO::iconNameForUrl(QUrl const) (url=...)
at /usr/src/debug/kio-5.7.0git/src/core/global.cpp:356
#14 0x7f6f21034352 in SearchProvider::iconName() const (this=optimized
out) at /usr/src/debug/kio-5.7.0git/src/urifilters/ikws/searchprovider.cpp:111
#15 0x7f6f4731313a in
KUriFilterData::iconNameForPreferredSearchProvider(QString const) const
(this=optimized out, provider=...)
at /usr/src/debug/kio-5.7.0git/src/widgets/kurifilter.cpp:381
#16 0x7f6f47f83883 in Konsole::SessionController::updateWebSearchMenu() ()
at /usr/lib64/libkonsoleprivate.so.3
#17 0x7f6f47f89697 in
Konsole::SessionController::showDisplayContextMenu(QPoint const) () at
/usr/lib64/libkonsoleprivate.so.3
#18 0x7f6f4494e12f in QMetaObject::activate(QObject*, int, int, void**)
(a=0---Type return to continue, or q return to quit---
x7fff89162eb0, r=0x2384940, this=0x2380270)
at ../../src/corelib/kernel/qobject_impl.h:124
#19 0x7f6f4494e12f in QMetaObject::activate(QObject*, int, int, void**)
(sender=0x23efd50, signalOffset=optimized out, local_signal_index=optimized
out, argv=0x7fff89162eb0) at kernel/qobject.cpp:3702
#20 0x7f6f47fbfc55 in Konsole::TerminalDisplay::configureRequest(QPoint
const) () at /usr/lib64/libkonsoleprivate.so.3
#21 0x7f6f47fa5269 in
Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*) () at
/usr/lib64/libkonsoleprivate.so.3
#22 0x7f6f4561d50a in QWidget::event(QEvent*) (this=0x23efd50, event=
0x7fff891633b0) at kernel/qwidget.cpp:8652
#23 0x7f6f47fa5cca in Konsole::TerminalDisplay::event(QEvent*) ()
at /usr/lib64/libkonsoleprivate.so.3
#24 0x7f6f455ddb5c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x2094b20, receiver=receiver@entry=0x23efd50,
e=e@entry=0x7fff891633b0) at kernel/qapplication.cpp:3722
#25 0x7f6f455e34e6 in QApplication::notify(QObject*, QEvent*)
(this=optimized out, receiver=0x23efd50, e=0x7fff891633b0) at
kernel/qapplication.cpp:3280
#26 0x7f6f4491ee55 in QCoreApplication::notifyInternal(QObject*, QEvent*)
(this=
0x7fff89163cd0, receiver=receiver@entry=0x23efd50,
event=event@entry=0x7fff891633b0) at kernel/qcoreapplication.cpp:930
#27 0x7f6f455e1eb1 in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEv---Type return to continue, or q return to quit---
ent*, QWidget*, QWidget*, QWidget**, QPointerQWidget, bool)
(event=0x7fff891633b0, receiver=0x23efd50) at

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Nick Shaforostoff]

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

--- Comment #56 from Nick Shaforostoff sha...@ukr.net ---
are you this patch would really matter, taking into account the fact that i
have 
/usr/share/dbus-1/system-services/org.kde.powerdevil.backlighthelper.service 
pointing to existing executable, which is linked against kf5 libraries?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Kai Uwe Broulik]

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

--- Comment #55 from Kai Uwe Broulik k...@privat.broulik.de ---
Does anyone of you have the possibility of reproducing this with an up to date
KAuth, specifically this [1] patch? There have been attempts to fix the KJob
fallback getting stuck but this patch will only be in Frameworks 5.7 which is
not yet released.

[1] https://git.reviewboard.kde.org/r/122029/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[David Edmundson]

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

--- Comment #57 from David Edmundson k...@davidedmundson.co.uk ---
Can someone try this please 
https://git.reviewboard.kde.org/r/122307/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[David Edmundson]

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

David Edmundson k...@davidedmundson.co.uk changed:

   What|Removed |Added

 CC||alexander...@gmail.com

--- Comment #63 from David Edmundson k...@davidedmundson.co.uk ---
*** Bug 343542 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Kai Uwe Broulik]

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

Kai Uwe Broulik k...@privat.broulik.de changed:

   What|Removed |Added

   Version Fixed In|5.2.0   |5.2.1
 Resolution|--- |FIXED
 Status|REOPENED|RESOLVED
  Latest Commit|http://commits.kde.org/plas |http://commits.kde.org/powe
   |ma-workspace/62fbfd5b15234f |rdevil/2c2c13751e19b0a37bb8
   |f38aa11ed131474991a193d17b  |b41096b08f80383e61df

--- Comment #62 from Kai Uwe Broulik k...@privat.broulik.de ---
Git commit 2c2c13751e19b0a37bb8b41096b08f80383e61df by Kai Uwe Broulik.
Committed on 29/01/2015 at 21:46.
Pushed by broulik into branch 'Plasma/5.2'.

Fix PowerDevil brightness calls breaking kded, Volume 3521

Query both brightness and maximum only once and then only listen to udev change
events and just kick off the set job and forget about it. That way we do not
have
nested event loops outside the init method anymore.
FIXED-IN: 5.2.1

This prevents re-entrancy issues

M  +23   -6daemon/actions/bundled/brightnesscontrol.cpp
M  +2-0daemon/actions/bundled/brightnesscontrol.h
M  +5-3daemon/backends/hal/powerdevilhalbackend.cpp
M  +1-1daemon/backends/hal/powerdevilhalbackend.h
M  +41   -42   daemon/backends/upower/powerdevilupowerbackend.cpp
M  +2-1daemon/backends/upower/powerdevilupowerbackend.h
M  +2-1daemon/powerdevilbackendinterface.h

http://commits.kde.org/powerdevil/2c2c13751e19b0a37bb8b41096b08f80383e61df

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Nick Shaforostoff]

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

--- Comment #53 from Nick Shaforostoff sha...@ukr.net ---
i have updated packages to 5.2 version and the issue is still there.

i can see it after screenlocker run as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Ruman Gerst]

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

--- Comment #51 from Ruman Gerst mrbo...@live.de ---
Huh? What happened?

It was gone for me with Plasma 5.1.1, now I'm using Plasma 5.2 from Kubuntu
Next Backports - now it's back!

I'll post a sysprof file, again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Ruman Gerst]

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

--- Comment #52 from Ruman Gerst mrbo...@live.de ---
Created attachment 90766
  -- https://bugs.kde.org/attachment.cgi?id=90766action=edit
Output from sudo sysprof now with Plasma 5.2 [Kubuntu Next Backports]

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Ruman Gerst]

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

Ruman Gerst mrbo...@live.de changed:

   What|Removed |Added

Version|5.1.95  |5.2.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Nick Shaforostoff]

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

Nick Shaforostoff sha...@ukr.net changed:

   What|Removed |Added

 CC||sha...@ukr.net

--- Comment #50 from Nick Shaforostoff sha...@ukr.net ---
i don't know whether the fix is installed in my vivid (most packages have
5.1.95 version), but i'm able to reproduce high cpu usage by connecting
external monitor.

when i connect external monitor, it has black background and immediately
everything becomes slow: at first 'top' shows that 4 'migration' processes are
taking cpu time, then after a while kded5 eats 100% cpu time (it goes crazy
with PowerDevilUPowerBackend::brightnessValueMax() and
PowerDevilUPowerBackend::brightnessValue()).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Antonis G .]

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

Antonis G. gaanto...@civil.auth.gr changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #49 from Antonis G. gaanto...@civil.auth.gr ---
Still happening, nothing changed. I should also add that Battery plasmoid
reports No screen or keyboard brightness controls available.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Kai Uwe Broulik]

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

Kai Uwe Broulik k...@privat.broulik.de changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
   Version Fixed In||5.2.0
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/plas
   ||ma-workspace/62fbfd5b15234f
   ||f38aa11ed131474991a193d17b

--- Comment #47 from Kai Uwe Broulik k...@privat.broulik.de ---
Apparently this fixed the issue. Feel free to re-open if the issue persists.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Tajidin Abd]

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

--- Comment #48 from Tajidin Abd tajidin...@archlinux.us ---
well for me it seems that when i login to Plasma5 kded5 is crashing from the
start. I wish i could provide you a backtrace. It is saying Segmentation fault

I am using the lastest build from git. I use the AUR repo from Archlinux. 
The lastest commit seems to crash kded5

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[David Edmundson]

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

David Edmundson k...@davidedmundson.co.uk changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #37 from David Edmundson k...@davidedmundson.co.uk ---
Can you guys confirm what distro and where you get your Plasma 5 from. Is it
self-installed? It seems like a polkit problem.

Also can you show me the output of:
pkaction -a org.kde.powerdevil.backlighthelper.syspath

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Luca Beltrame]

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

--- Comment #38 from Luca Beltrame lbeltr...@kde.org ---
In data domenica 18 gennaio 2015 14:23:29, hai scritto:

 Can you guys confirm what distro and where you get your Plasma 5 from. Is it
 self-installed? It seems like a polkit problem.

In my and Hrvoje's cases is from openSUSE, using distro-supplied packagign.

 pkaction -a org.kde.powerdevil.backlighthelper.syspath

All I get is:

[lb@leon ~]$ pkaction -a org.kde.powerdevil.backlighthelper.syspath
org.kde.powerdevil.backlighthelper.syspath

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Hrvoje Senjan]

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

--- Comment #42 from Hrvoje Senjan hrvoje.sen...@gmail.com ---
i'm also having two kded5 processes, user's and sddm's. however, only users
goes wild.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Kai Uwe Broulik]

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

--- Comment #46 from Kai Uwe Broulik k...@privat.broulik.de ---
Git commit 62fbfd5b15234ff38aa11ed131474991a193d17b by Kai Uwe Broulik.
Committed on 18/01/2015 at 22:19.
Pushed by broulik into branch 'Plasma/5.2'.

Remove explicit source request

This was there to initially populate the dataengine. But since the requests are
all
asynchronous the data won't be there on time anyway, so let's just wait until
somebody
explicitly requests the source which was done by batterymonitor anyway
resulting in two
subsequent calls potentially confusing PowerDevil and causing it to go nuts.

M  +0-2dataengines/powermanagement/powermanagementengine.cpp

http://commits.kde.org/plasma-workspace/62fbfd5b15234ff38aa11ed131474991a193d17b

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Hrvoje Senjan]

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

--- Comment #44 from Hrvoje Senjan hrvoje.sen...@gmail.com ---
i've just tried kdm, and managed to reproduce the issue still...

it's essential that the helper, and not XRandBrightness is used.
also, i've tried locally to revert the logic in powerdevil (switch to
!job-exec(), instead of checking it's successful first, and that resolved for
me bug 342597. one caveat is that the slider then has 9/9 which is a regression
i'd say compared to 5.1.x. the logic switch does not help this bug though)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Steven Franzen]

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

--- Comment #45 from Steven Franzen sfranze...@hotmail.com ---
(In reply to David Edmundson from comment #37)
 Can you guys confirm what distro and where you get your Plasma 5 from.
I have Fedora 21 with Plasma 5.1.95 and KF 5.6 installed from Daniel Vrátil's
custom repositories.

 Also can you show me the output of:
 pkaction -a org.kde.powerdevil.backlighthelper.syspath
org.kde.powerdevil.backlighthelper.syspath

Re: SDDM:
I also use SDDM (version 0.10.0), but I only have a single instance of kded5
running.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek]

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

--- Comment #43 from Martin Klapetek mklape...@kde.org ---
Fwiw (with regards to those sddm comments) I use lightdm and have never seen
this issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Nickolay Krachkovsky]

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

Nickolay Krachkovsky krachkov...@mail.ru changed:

   What|Removed |Added

 CC||krachkov...@mail.ru

--- Comment #34 from Nickolay Krachkovsky krachkov...@mail.ru ---
Same for me. kded5 consumes 1 core. I'm using notebook, if I change monitor
brightness cpu usage is lowered to 0%, but after time may up again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[tajidinabd]

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

tajidin...@archlinux.us changed:

   What|Removed |Added

 CC||tajidin...@archlinux.us

--- Comment #35 from tajidin...@archlinux.us ---
Also on Archlinux git build the kded5 is killing one core on my machine at
100%. If i kill it things return to normal

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Steven Franzen]

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

Steven Franzen sfranze...@hotmail.com changed:

   What|Removed |Added

 CC||sfranze...@hotmail.com

--- Comment #36 from Steven Franzen sfranze...@hotmail.com ---
(In reply to Mykola Krachkovsky from comment #34)
 Same for me. kded5 consumes 1 core. I'm using notebook, if I change monitor
 brightness cpu usage is lowered to 0%, but after time may up again.

This trick also works for me.

I can further report that I can reliably trigger the CPU usage manually by
unlocking (not just locking) the screen from the screen locker.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek]

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

--- Comment #31 from Martin Klapetek mklape...@kde.org ---
*** Bug 341775 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek]

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

Martin Klapetek mklape...@kde.org changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|unspecified |5.1.95
 Resolution|DOWNSTREAM  |---
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Marco Martin]

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

Marco Martin notm...@gmail.com changed:

   What|Removed |Added

 CC||notm...@gmail.com

--- Comment #32 from Marco Martin notm...@gmail.com ---
more than kded5 eating 100% cpu is perhaps it dying and restarting all the
time? (i get that sometimes)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Hrvoje Senjan]

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

--- Comment #33 from Hrvoje Senjan hrvoje.sen...@gmail.com ---
nope, it is the same process

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Martin Klapetek]

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

Martin Klapetek mklape...@kde.org changed:

   What|Removed |Added

   Target Milestone|1.0 |---
Version|master  |unspecified
Product|plasmashell |Powerdevil
   Assignee|se...@kde.org   |plasma-devel@kde.org
 CC||k...@privat.broulik.de
  Component|general |general

--- Comment #29 from Martin Klapetek mklape...@kde.org ---
I'm not sure if I'm reading this correctly but it looks like

PowerDevilUPowerBackend::brightnessValue execs a job and inside this new event
loop the
PowerDevilUPowerBackend::brightnessValueMax execs a job and then inside
PowerDevilUPowerBackend::brightnessValue execs a job and then
PowerDevilUPowerBackend::brightnessValueMax execs a new job...?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

[Powerdevil] [Bug 337674] kded5 is eating CPU

[Hrvoje Senjan]

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

--- Comment #30 from Hrvoje Senjan hrvoje.sen...@gmail.com ---
Created attachment 90381
  -- https://bugs.kde.org/attachment.cgi?id=90381action=edit
sligthly more debug

i am also getting the CPU murdering after recent changes to powerdevil
dataengine  powerdevil itself (see also bug 342597)

this one can be reproduced on my setup at 99% of the time after doing a switch
user routine. after going back to original session, kded5 is busy

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel