Bug 495490 - On one monitor, brightness setting reverts to 20% instead of staying at 100%
Summary: On one monitor, brightness setting reverts to 20% instead of staying at 100%
Status: RESOLVED FIXED
Alias: None
Product: Powerdevil
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 6.2.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-28 16:23 UTC by Markus
Modified: 2024-11-08 17:22 UTC (History)
3 users (show)

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


Attachments
Brightness setting (37.79 KB, image/png)
2024-10-29 17:19 UTC, Markus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus 2024-10-28 16:23:31 UTC
The brightness setting on my monitor continuously reverts to 20%, regardless of my attempts to adjust it to 100%. This issue causes the monitor to be excessively bright, leading to discomfort and strain on my eyes. I would appreciate any assistance in resolving this problem, as a consistent brightness level is crucial for my comfort while using the device. Thank you!
Comment 1 Nate Graham 2024-10-29 16:25:38 UTC
What version of Plasma are you using, and on What distro?

How many monitors do you have, what are their brands and models, and how are they connected?
Comment 2 Markus 2024-10-29 17:19:10 UTC
Created attachment 175339 [details]
Brightness setting
Comment 3 Markus 2024-10-29 17:35:32 UTC
(In reply to Nate Graham from comment #1)
> What version of Plasma are you using, and on What distro?
> 
> How many monitors do you have, what are their brands and models, and how are
> they connected?

Operating System: Arch Linux 
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 6.11.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics
Memory: 60.6 GiB of RAM
Graphics Processor: AMD Radeon 780M
Manufacturer: HP
Product Name: HP EliteBook 845 14 inch G10 Notebook PC
System Version: SBKPF

Summary

The brightness setting on DELL U2715H consistently resets to 20% or 30%, causing discomfort due to excessive brightness.
Description

I am experiencing an issue with the brightness setting on my DELL U2715H monitor, which always reverts to either 20% or 30%, despite my attempts to manually adjust it. In contrast, my Samsung LS27A600U monitor does not exhibit this problem. The excessive brightness from the DELL monitor causes discomfort and strain on my eyes, making it difficult to use for extended periods. I would greatly appreciate any assistance in resolving this issue to maintain a consistent brightness level. Thank you!
Comment 4 Markus 2024-10-29 17:39:02 UTC
(In reply to Nate Graham from comment #1)
> What version of Plasma are you using, and on What distro?
> 
> How many monitors do you have, what are their brands and models, and how are
> they connected?

Sorry for the additional comment regarding the connections. I am encountering an issue with my DELL U2715H monitor when connected through USB-C to my laptop, while the Samsung LS27A600U monitor is daisy-chained via DisplayPort (DP) directly to the DELL monitor. The brightness setting on the DELL U2715H consistently reverts to either 20% or 30%, despite my efforts to adjust it manually. In contrast, the Samsung LS27A600U does not exhibit this problem. The excessive brightness from the DELL monitor leads to discomfort and strain on my eyes. I would appreciate any assistance in resolving this issue to ensure a consistent brightness level. Thank you!
Comment 5 Nate Graham 2024-10-30 15:09:39 UTC
Thanks for the info.
Comment 6 Jakob Petsovits 2024-10-30 15:21:56 UTC
If you have an X11 session available for testing, could you try logging into that one to see if the problem also surfaces there? (To confirm whether or not this is related to PowerDevil's KWin integration.)
Comment 7 Markus 2024-11-08 17:22:31 UTC
My KDE Plasma system became unbootable, so I reinstalled it. Now it's much more stable, and the brightness settings persist. I'm not entirely sure what caused the initial issue, but it's resolved now.