| Summary: | Monitor brightness settings go to 100% when monitor / system wakes up | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | marc <marc_smith> |
| Component: | Power management & brightness | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | agsimmons0, boskobs, geoffrey.chancel, jpetso, kdebugs, l0rmin, liangrui.ch, manrusin, moylanj, nate, nicolas.fella, os, postix, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
marc
2025-02-15 09:55:22 UTC
Hi! I can confirm this new bug as well. Issues started with upgrade to 6.3. I have two monitors. The main one experiences the issue, the other one does not. Easiest way to reproduce: * dbus-send --session --print-reply --dest=org.kde.kglobalaccel /component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut string:'Turn Off Screen' >/dev/null * wait until display enters power saving mode and backlight goes off * wakup -> main display is at 100% Operating System: Arch Linux KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: Intel® Arc (In reply to os from comment #1) > Hi! > > I can confirm this new bug as well. Issues started with upgrade to 6.3. > I have two monitors. The main one experiences the issue, the other one does > not. > > Easiest way to reproduce: > * dbus-send --session --print-reply --dest=org.kde.kglobalaccel > /component/org_kde_powerdevil org.kde.kglobalaccel.Component.invokeShortcut > string:'Turn Off Screen' >/dev/null > * wait until display enters power saving mode and backlight goes off > * wakup -> main display is at 100% > > Operating System: Arch Linux > KDE Plasma Version: 6.3.0 > KDE Frameworks Version: 6.10.0 > Qt Version: 6.8.2 > Kernel Version: 6.13.2-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor > Memory: 62.7 GiB of RAM > Graphics Processor: Intel® Arc I have two monitors as well, but in my case, both experience this issue. Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550M AORUS ELITE Can confirm, my main monitor has a weird behavior (goes to deep sleep immediately) where it disconnects and reconnects on wake up, it has not been an issue until 6.3. Now two of my monitor's brightness gets set to 100% on wake up. a third LG monitor is completely unaffected. I have tried downgrading powerdevil to 6.2.x, which did not help. I can reproduce this on all of my computers too. Similar behavior, openSUSE Tumbleweed 20250217 plasma version 6.3.0 kde framework 6.11.0 Linux localhost.localdomain 6.13.2-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb 10 09:00:08 UTC 2025 (306384d) x86_64 x86_64 x86_64 GNU/Linux Ryzen 9 7900X Intel Arc a770 LE 1x 27" 1440p connected via DP PRIMARY 1x 24" 1080p HDMI connected via external DP->HDMI adapter (builtin one is flakey it is also a DP->HDMI converter FYI) SECONDARY Primary m,onitor on wake from sleep is ALWAYS set to 100% brightness. Secondary monitor has been unaffected so far. Bug did NOT appear until update to plasma 6.3.0, and has worked fine(since it appeared/offered) until said update. Have NOT yet tested on cachyos or endeavor w/plasma 6.3 as I usually do not bother sleeping those. (Linux sleep is flakey and booting from nvme is about as fast as waking from sleep, desktop I use sleep as er... I haven't migrated the boot drive from spinning rust to nvme yet... I'm practicing my procrastination skills.) I can reproduce this now. It looks like the request comes from KWin directly through the corresponding "external-brightness-v1" Wayland object that is still sticking around from before the suspend/disconnect because ddcutil 2.1.4 doesn't necessarily notify us about the monitor's disappearance. The setter for 100% brightness comes in before any powerdevil-side "setBrightness()" calls are even invoked. I haven't yet figured out why KWin resets brightness to 100% - if you check kwinoutputconfig.json after its disappearance, brightness is still at the lower (e.g. 0.15) value. It only goes up to 1 once the output gets re-enabled. We can probably work around this by removing PowerDevil's underlying display objects if the associated KWinDisplayBrightness goes away. But it would also be good to understand where the 100% are really coming from. Latest fix in 6.3.1 does work, but only partially. When PC gets back from sleep, it indeed saves proper brightness level, **but you are no longer able to change brightness levels with Fn+Up/Down, so you're not able to bring it to other level.** *** Bug 500609 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 494408 *** |