https://bugs.kde.org/show_bug.cgi?id=422033
Dominik Waurenschk <dominik.waurenschk+...@protonmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominik.waurenschk+kde@prot
| |onmail.com
--- Comment #3 from Dominik Waurenschk <dominik.waurenschk+...@protonmail.com>
---
I have just come across this exact issue myself. I investigated the code and
found that RSIBreak calls KIdleTime, which uses a platform-specific plugin to
find the idle time.
For wayland, this prints a warning to console that the plugin does not support
polling idle time (it does support timeouts it seems).
But, then it returns 0, which RSIBreak in turn interprets as 0 seconds of idle
time and resets the timer.
So if it's not possible to measure idle time on wayland (or really hard to do),
I think it could be fixed by having that plugin return an error (like -1 or so)
instead of 0, and then have RSIBreak use it's own timer and listen to the
resumingFromIdle signal perhaps to reset? (I haven't checked if this would
work).
Just wanted to add to add to this bug report that's it's not actually an
RSIBreak problem, rather a KIdleTime or KWayland problem.
--
You are receiving this mail because:
You are watching all bug changes.
