https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #51 from Jonathan Lopes <joniwe...@gmail.com> --- Created attachment 166718 --> https://bugs.kde.org/attachment.cgi?id=166718&action=edit powerdevil.gdb (In reply to Vlad Zahorodnii from comment #49) > (In reply to Jonathan Lopes from comment #48) > > 2652 is powerdevil > > > > > $ ps -p 2652 -o command > > > COMMAND > > > /usr/lib/org_kde_powerdevil > > Hmm, can you attach gdb to powerdevil and add a breakpoint in > KIdleTime::addIdleTimeout please? Sure. I noticed that if I enable my Energy Saving settings and then disable, this prevents the problem from happening until the next boot (but only if you change before the flood starts, it won't help if it's already flooding the logs). I looked at the source code and I found this relevant section: https://invent.kde.org/plasma/powerdevil/-/blob/Plasma/6.0/daemon/actions/bundled/dpms.cpp?ref_type=heads#L220-227 There's no condition to check if the setting is enabled in the first place, while this one: https://invent.kde.org/plasma/powerdevil/-/blob/Plasma/6.0/daemon/actions/bundled/dpms.cpp?ref_type=heads#L177-179 Which supports my first attempt to add a breakpoint to powerdevil after having changed its settings, when I enabled, it loaded the default values in memory, when I disabled, those values were not reset. But after rebooting, the problem was back since those values will not be set as the setting is disabled. That's my guess, I don't really know if this is indeed the cause of the problem, but it looks like. Does have a check. -- You are receiving this mail because: You are watching all bug changes.
