https://bugs.kde.org/show_bug.cgi?id=498913
Saul Fautley <saulfaut...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|unspecified |Arch Linux
Summary|Changing screen brightness |Changing screen brightness
|with slider is too slow |is slow
--- Comment #7 from Saul Fautley <saulfaut...@gmail.com> ---
(In reply to John Kizer from comment #5)
> Do the ideas on that page and in this thread -
> https://github.com/rockowitz/ddcutil/issues/240 - around changing the
> --sleep-multiplier setting change the response time?
I've tried a bunch of different values for `--sleep-multiplier` and other args
but it makes no difference. Using `--bus` makes ddcutil faster, as mentioned in
that issue and in this issue's description, but it can't be applied to
powerdevil or system-wide like other args. I'm on Arch which I've added to the
bug report now.
(In reply to Jakob Petsovits from comment #6)
Thanks very much for the feedback on this Jakob. However I'm not convinced this
is the cause of the issue at hand, or at least not the full picture.
First off, brightness updates using the slider were much quicker right before
the update you pushed for https://bugs.kde.org/show_bug.cgi?id=481793. Was it
your patch that also added the 1 second delay?
Secondly, the delay isn't only seen when using the slider. It's also present
when changing brightness via dbus, e.g. `qdbus6 org.kde.ScreenBrightness
/org/kde/ScreenBrightness/display0 SetBrightness 50 0`. Nate added the "with
slider" to the title of this bug, which I've removed now because I don't think
it's accurate.
I understand not wanting to spam monitors with ddc messages when moving the
slider. But surely the timeout should only apply to the brightness slider
widget then and not to any brightness change made with powerdevil?
--
You are receiving this mail because:
You are watching all bug changes.
