https://bugs.kde.org/show_bug.cgi?id=498913
Bug ID: 498913
Summary: Changing screen brightness too slow
Classification: Plasma
Product: plasmashell
Version: master
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: Power management & brightness
Assignee: plasma-b...@kde.org
Reporter: saulfaut...@gmail.com
Target Milestone: 1.0
Created attachment 177540
--> https://bugs.kde.org/attachment.cgi?id=177540&action=edit
KDE Slow Brightness Change
The fix for the below powerdevil bug resulted in screen brightness changes
taking well over a second, whereas before they were almost instantaneous.
https://bugs.kde.org/show_bug.cgi?id=481793#c7
Jakob Petsovits did a great job getting this fixed quickly, but it needs a bit
more love to get it on par with brightness change responsiveness in other
desktops / OSes.
In my mind an ideal implementation would be to keep the current behaviour as
default, where monitor handles are opened and closed as needed. But, if the
`--disable-cross-instance-locks` option is present in a ddcutilrc config file,
then keep handles open. In this case it won't cause issues with other ddcutil
instances, and brightness changes will be much quicker. The best of both
worlds.
Additionally or alternatively, there could be a setting or environment variable
to toggle whether powerdevil holds monitor handles open or not, to give the
user more control over this.
As a bonus, if it's possible to cache and use the `--bus` arg when opening
monitor handles with libddcutil, it may speed it up as mentioned in the docs
below. Using this with ddcutil cli reduces update time by over 50%.
https://www.ddcutil.com/faq/#ddcutil-is-slow
--
You are receiving this mail because:
You are watching all bug changes.
