| Summary: | Brightness gets maximized after screen times out. | ||
|---|---|---|---|
| Product: | [Plasma] Powerdevil | Reporter: | KingSpammerNerd <kingspammernerd> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aspotashev, meven.car, meven29, notuxius, pietro.fontana |
| Priority: | NOR | Keywords: | wayland |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
KingSpammerNerd
2019-11-24 06:41:32 UTC
I can confirm this issue on a Plasma/Wayland session. Operating System: Manjaro Linux KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.5.13-1-MANJARO OS Type: 64-bit Device: Intel HD Graphics 620 driver: i915 v: kernel Display: wayland server: X.org 1.20.7 driver: modesetting See also this other report: https://bugs.kde.org/show_bug.cgi?id=383307 I can reproduce this issue just by locking and unlocking the session, the brightness is maximized after unlocking. I don't reproduce with a recent Plasma version with the steps described here. What I tested : 1. set screen lock timeout to 1 minute "lock screen" kcm 2. waited 1 minute for session lock 3. waited more until the screen turned off 4. Moved mouse The screen switches on with the previous set brightness. 1. Sleep the session 2. Moved mouse The screen switches on with the previous set brightness. I suspect I don't reproduce because of a different bug, I encountered when testing : 1. in powersaving kcm set brightness to 100% when plugged in (I was plugged in) 2. Lower the brightness manually using the plasma applet 3. Turn laptop to sleep 4. Turn the laptop on again and login I could observe the screen brightness did not change, but the plasma applet showed that I had 100% brightness. I reproduced this behavior after locking the screen and letting turned off. SOFTWARE/OS VERSIONS Kde neon Kernel 5.3 KDE Plasma : 5.18.80 KDE Frameworks: 5.69 Qt: 5.14 Thinkpad T460s Can you confirm the bug after checking your settings in the powersaving kcm, and check you don't have value set for brightness in whatever battery state you are testing ? Can you confirm this was not due to a powersaving setting ? *** Bug 383307 has been marked as a duplicate of this bug. *** Update, I still experience the issue but it became harder to reproduce. I tried the following: 1. set screen dim timeout to 1min, set screen energy saving timeout to 2min 2. set automatic screen lock to 1min 3. wait until the screen is locked and turned off alternative 3. lock the screen and wait until it turns off 4. wake up the screen and unlock it I am not able to reproduce the issue, but I still experience it everyday when I leave the computer locked for a longer period. The Plasma applet behaves in a consistent way on my system, it always displays the current brightness. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 Kernel Version: 5.6.3-2-MANJARO Display: wayland server: X.org 1.20.8 driver: modesetting (In reply to Pietro F. Fontana from comment #5) > > I am not able to reproduce the issue, but I still experience it everyday > when I leave the computer locked for a longer period. Do you have a powerdevil/powersaving settings set for the brightness ? Aka `kcmshell powerdevilprofilesconfig` Do you use hibernation on your laptop, especially when the computer is "locked for a longer period" ? If we can't reproduce it anymore, maybe we can resolve this one with status "Works for me". (In reply to Méven Car from comment #6) > Do you have a powerdevil/powersaving settings set for the brightness ? > Aka `kcmshell powerdevilprofilesconfig` Yes, none of them is set to maximum brightness. > Do you use hibernation on your laptop, especially when the computer is > "locked for a longer period" ? The system does not suspend or hibernate automatically when connected to AC. > If we can't reproduce it anymore, maybe we can resolve this one with status > "Works for me". I would say that the problem is still there, but it's not easy to reproduce. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |