https://bugs.kde.org/show_bug.cgi?id=482713
--- Comment #72 from d3vilguard <g.igna...@outlook.com> --- This is not only multimonitor behavior. Tested with just the acer connected (one connected monitor). Shutting the monitor down or letting it go to monitor sleep (again no PC suspend states, just monitor sleep. Also disabled DIM) results in it being set to 100% after I wake it up. It should wake up at 15%. Most likely the issue is from the acer taking a few seconds to wake up, while plasma itself is ready to display. This leads to the monitor being recognized as newly connected. Newly connected monitors in 6.3 are getting set at 100% no matter what the value in the monitor was?! Proving this I had my huawei at 15%. Disconnected it. Booted with just the Acer. Connected the huawei. Huawei gets set at 100% instead of 15%! Who in their right mind decided to set 100 to connected monitors instead of to read whatever ddc pulls from the monitor and set it... Or even remember states? To mitigate this I will just disable ddcutil for powerdevil and use ddcutil on its own to control my monitors. $ systemctl --user edit plasma-powerdevil.service [Service] Environment=POWERDEVIL_NO_DDCUTIL=1 $ systemctl --user restart plasma-powerdevil.service Then make two shortcuts for Up and Down ddcutil -b 8 --sleep-multiplier .1 setvcp 10 + 1 & ddcutil -b 6 --sleep-multiplier .1 setvcp 10 + 1 ddcutil -b 8 --sleep-multiplier .1 setvcp 10 - 1 & ddcutil -b 6 --sleep-multiplier .1 setvcp 10 - 1 See -b * is being set by ddcutil for your monitors. This will change by 1% on press. -- You are receiving this mail because: You are watching all bug changes.
