Bug 423457

Summary: When unlocking a session after laptop lid has been closed screen brightness is not restored
Product: [Plasma] Powerdevil Reporter: Matej Mrenica <matejm98mthw>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bugseforuns, lubimov.maxim+kde, matejm98mthw, natalie_clarius, nate, postix, syiad.al-duri
Priority: NOR Keywords: wayland
Version: 5.20.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Matej Mrenica 2020-06-24 17:07:04 UTC
SUMMARY
... or is reset to 0%. But it doesn't always happen.

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.71
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Only on Wayland
Comment 1 Matej Mrenica 2020-07-27 13:16:11 UTC
Here is a log, someone might notice something useful: https://pastebin.com/zYSizmrD
Comment 2 Patrick Silva 2020-11-01 11:42:23 UTC
I can't reproduce on neon unstable. Can you reproduce with newer Plasma?

Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.0
Comment 3 Matej Mrenica 2020-11-01 17:52:01 UTC
I can only test on Arch Linux with Plasma 5.20.2 and I have this issue there.
Comment 4 Nate Graham 2020-11-02 21:31:03 UTC
Is the power cord connected or not? Are you hitting https://gitlab.freedesktop.org/upower/upower/-/issues/126 or not?
Comment 5 Matej Mrenica 2020-11-03 07:04:01 UTC
It's connected all the time, I don't think it's the issue.
Comment 6 Syiad 2022-09-26 11:54:04 UTC
I have the same issue with Kubuntu 22.04.
Frameworks 5.98.0
Plasma 5.25.5
Qt 5.15.03
Kernel 5.15.0-50
Wayland

When I open the lid to resume a session, the screen brightness is at full power (I suppose). The brightness percentage  setting remains where it was prior to suspend, but the actual brightness is ~100%. To restore it after login, I have to decrease and then increase it by one step; it jumps to the new value upon decrease.
Comment 7 postix 2024-05-18 11:39:53 UTC

*** This bug has been marked as a duplicate of bug 452492 ***