Bug 482278 - Screen remains dimmed after unlocking
Summary: Screen remains dimmed after unlocking
Status: REOPENED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Power management & brightness (other bugs)
Version First Reported In: 6.2.4
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-03 09:12 UTC by Eugene Shalygin
Modified: 2025-08-13 18:59 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.4.4
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Shalygin 2024-03-03 09:12:41 UTC
SUMMARY
When powerdevil-6.0 is built with screen brightness support (HAVE_DDCUTIL), the screen brightness decreases as per power management settings, but is not restored upon unlocking the session. The brightness level slider in the applet is not updated as well.  Changing the value there brings the desired brightness level back.


STEPS TO REPRODUCE
1.  Wait until the screen gets locked and powered off
2. Wake up the screen. Notice normal brightness level in the screenlock.
3. Unlock the session.

OBSERVED RESULT
Screen goes dim.

EXPECTED RESULT
Screen brightness corresponds to the value as it is set in the brightness applet.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.14
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.7-gentoo (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 5900HX with Radeon Graphics
Graphics Processor: AMD Radeon Graphics
Comment 1 Sharath 2024-03-05 10:45:03 UTC
Hi admin,

The same problem exists in the KDE Neon Wayland version as well.

Regards,
Sharathchandra
Comment 2 Jakob Petsovits 2024-04-02 02:25:05 UTC
Hi, could you confirm if this is still an issue with Plasma 6.0.1 or higher? The original 6.0.0 release was missing this commit: https://invent.kde.org/plasma/powerdevil/-/commit/8681355217eb6ff121785572eaf4ef2ca21b464b which fixed restoring the old brightness in some cases (see the link for more details in the commit message).
Comment 3 David Warner 2024-04-02 04:44:50 UTC
(In reply to Jakob Petsovits from comment #2)
> Hi, could you confirm if this is still an issue with Plasma 6.0.1 or higher?
> The original 6.0.0 release was missing this commit:
> https://invent.kde.org/plasma/powerdevil/-/commit/
> 8681355217eb6ff121785572eaf4ef2ca21b464b which fixed restoring the old
> brightness in some cases (see the link for more details in the commit
> message).

This is still an issue for me in 6.0.3. Same repro steps as above. My screens (2x DisplayPort, 1x HDMI) are set to 100% brightness; after the screens are turned off due to inactivity, they will be at some brightness <100% after being turned back on.
Comment 4 Eugene Shalygin 2024-04-02 12:02:25 UTC
Still an issue here with 6.0.3 and a single HDMI screen as well, albeit it happens less often with 6.0.3 as compared to 6.0.1. The screen is set to 50% brightness, and finds itself dimmed to the min (10%) after waking up from sleep.
Comment 5 David Warner 2024-04-06 10:59:37 UTC
In case it's helpful: in my 2x DisplayPort, 1x HDMI setup, the issue seems to be occurring only on the monitor connected by HDMI - the other 2 monitors are correctly set at 100% brightness after resuming. The monitor connected by HDMI also takes longer to turn back on, so I wonder if it's a timing issue of some kind.
Comment 6 David Warner 2024-04-06 11:25:20 UTC
Sorry, ignore all the above - it just happened on the DisplayPort monitors, too.
Comment 7 kinghat 2024-04-27 21:24:51 UTC
im having this issue as well. mine brightness always gets set to 30%

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Xeon® CPU E5-1620 v3 @ 3.50GHz
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 470 Graphics
Comment 8 Jakob Petsovits 2024-05-04 15:03:50 UTC
*** Bug 486500 has been marked as a duplicate of this bug. ***
Comment 9 Jakob Petsovits 2024-05-04 15:07:16 UTC
See Bug 486500 Comment #2 for an informed guess at what's happening. Brief summary, I agree with David Warner above that this is likely timing-related and perhaps caused by a lack of coordination with the DPMS (screen turn-off/on) action.
Comment 10 Jakob Petsovits 2024-05-04 15:11:54 UTC
Actually no, let me un-duplicate Bug 486500 again because this bug is about brightness being dimmed after *unlocking*, whereas Bug 486500 is about brightness being dimmed immediately after wake-up (i.e. brightness would be wrong even on the lock screen).
Comment 11 Jakob Petsovits 2024-12-16 18:14:46 UTC
Hi, checking in. KWin/Wayland in Plasma 6.2 is handling important parts of the brightness infrastructure, and other fixes have gone into PowerDevil's brightness code over the past couple of releases.

Can you still observe a brightness difference between brightness levels in points (2) and (3) of the original bug description?

Note that Plasma 6.3 will contain a rework of dimming code, which closes Bug 452492 among other reliability wins. If we end up leaving this open for now, let's ask again for retesting once 6.3 is out.
Comment 12 David Warner 2024-12-17 05:41:09 UTC
This is better for me now in Plasma 6.2 on a fresh Fedora 41 install (which I think shipped with Plasma 6.2.1 - currently 6.2.4). The screen is dimmed when the lock screen appears after a period of inactivity, but the correct brightness is always restored after unlocking.
Comment 13 Nate Graham 2024-12-17 16:23:54 UTC
Thanks a lot for following up!
Comment 14 Eugene Shalygin 2024-12-17 16:34:59 UTC
Not much has changed for me: with Plasma 6..2.4 the actual screen brightness and the indicator are out of sync upon waking up the screen.
Comment 15 Jakob Petsovits 2024-12-17 17:27:08 UTC
(In reply to Eugene Shalygin from comment #14)
> Not much has changed for me: with Plasma 6..2.4 the actual screen brightness
> and the indicator are out of sync upon waking up the screen.

Okay, thanks for retesting! There is reason to assume that Plasma 6.3 is going to do better on both fronts, please retest and report back once you get access to the new version.
Comment 16 David Warner 2024-12-20 09:22:57 UTC
This might be an edge case not worth worrying about, but yesterday I had a brief power outage and my monitors were all set to 30% when I turned my PC back on - I guess the previous state isn't retained in this scenario.
Comment 17 Jakob Petsovits 2024-12-21 00:15:41 UTC
(In reply to David Warner from comment #16)
> This might be an edge case not worth worrying about, but yesterday I had a
> brief power outage and my monitors were all set to 30% when I turned my PC
> back on - I guess the previous state isn't retained in this scenario.

This counts as system restart, which is Bug 494722. It's marked as resolved because Plasma 6.3 should fully fix this on Wayland (at the cost of not recognizing OSD menu changes to a monitor's brightness level, only changes through KWin such as brightness applet slider / brightness slider will be remembered). For X11, that issue is a WONTFIX as PowerDevil itself doesn't store brightness values in a config file, so it has no way of bringing back the un-dimmed brightness, at least in case of a power outage.
Comment 18 David Warner 2025-02-14 00:07:40 UTC
(In reply to Jakob Petsovits from comment #17)
> (In reply to David Warner from comment #16)
> > This might be an edge case not worth worrying about, but yesterday I had a
> > brief power outage and my monitors were all set to 30% when I turned my PC
> > back on - I guess the previous state isn't retained in this scenario.
> 
> This counts as system restart, which is Bug 494722. It's marked as resolved
> because Plasma 6.3 should fully fix this on Wayland (at the cost of not
> recognizing OSD menu changes to a monitor's brightness level, only changes
> through KWin such as brightness applet slider / brightness slider will be
> remembered). For X11, that issue is a WONTFIX as PowerDevil itself doesn't
> store brightness values in a config file, so it has no way of bringing back
> the un-dimmed brightness, at least in case of a power outage.

I might need to open a separate bug for this, but I wonder if this Plasma 6.3 change is responsible for a new issue I'm seeing where KDE is somehow mapping 100% brightness to 30% brightness per the monitor's settings. I've disabled screen dimming for now.
Comment 19 David Warner 2025-02-14 00:09:23 UTC
(In reply to David Warner from comment #18)
> (In reply to Jakob Petsovits from comment #17)
> > (In reply to David Warner from comment #16)
> > > This might be an edge case not worth worrying about, but yesterday I had a
> > > brief power outage and my monitors were all set to 30% when I turned my PC
> > > back on - I guess the previous state isn't retained in this scenario.
> > 
> > This counts as system restart, which is Bug 494722. It's marked as resolved
> > because Plasma 6.3 should fully fix this on Wayland (at the cost of not
> > recognizing OSD menu changes to a monitor's brightness level, only changes
> > through KWin such as brightness applet slider / brightness slider will be
> > remembered). For X11, that issue is a WONTFIX as PowerDevil itself doesn't
> > store brightness values in a config file, so it has no way of bringing back
> > the un-dimmed brightness, at least in case of a power outage.
> 
> I might need to open a separate bug for this, but I wonder if this Plasma
> 6.3 change is responsible for a new issue I'm seeing where KDE is somehow
> mapping 100% brightness to 30% brightness per the monitor's settings. I've
> disabled screen dimming for now.

I could have worded that more clearly - I meant to say that 100% brightness in the KDE applet sets the monitor brightness to 30% (per the OSD controls). 50% brightness -> 15%, etc.
Comment 20 TraceyC 2025-08-12 22:08:35 UTC
Thanks for the bug report. I'm sorry we weren't able to get to it yet. Are you still seeing this happen with ddcutil 2.2.1 or greater and Plasma 6.4.4 or later?
Comment 21 Mitja 2025-08-13 16:19:31 UTC
No, this issue is resolved. I'm running Fedora 42 with KDE Plasma 6.4.4.
Comment 22 Nate Graham 2025-08-13 16:20:19 UTC
Great!
Comment 23 Eugene Shalygin 2025-08-13 18:59:14 UTC
Not fixed for me with ddcutil 2.2.1 and Plasma 6.4.4