https://bugs.kde.org/show_bug.cgi?id=500835
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO |---
--- Comment #2 from Jakob Petsovits <jpe...@petsovits.com> ---
ddcutil 2.2.0 has two different "watch modes", as per release notes:
http://www.ddcutil.com/c_api_220/
The logs from Comment #0 indicate that this user's system is using the POLL
watch mode, see this snippet:
> watch mode = Watch_Mode_Poll, poll loop interval = 2000 millisec
On my system, I get Watch_Mode_Xevent which according to ddcutil is easier on
the CPU. So, if ddcutil with POLL watch mode is too CPU-intensive on a Ryzen
5600G (which isn't even all that old) then that's not so great.
As mentioned in Bug 500951 comment #2, possible attempt on the powerdevil side
of things could be to abandon ddcutil's display change notifications
altogether, and instead trigger manual ddcutil redetection after libkscreen
tells us about new or removed displays.
--
You are receiving this mail because:
You are watching all bug changes.
