SUMMARY STEPS TO REPRODUCE 1. don't touch the mouse and keyboard for 5 minutes 2. Right when the screen dims and is going to be automatically locked, IMMEDIATELY shake the mouse to prevent it OBSERVED RESULT Sometimes, randomly (I guess if the timing is exactly right), the screen locking is prevented, but the screen remains dim, the full brightness is not restored. Changing the screen brightness with the slider control does absolutely nothing. Manually locking and then unlocking the screen does not restore the original brightness. The workaround is to press Ctrl+Alt+F3 to go to a virtual console and then Ctrl+Alt+F1 to come back to the graphical screen, then the original brightness is restored. However, the screen brightness control still does nothing. EXPECTED RESULT When the screen locking is aborted by shaking the mouse, everything should go back to normal, including the screen brightness. Always (as opposed to most of the times). This is absolutely crazy and I think it's a relatively recent regression. I have already observed this a couple of times, but I had never seen it happen until recently. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.3.6 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.6.99-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × 12th Gen Intel® Core™ i7-1255U Memory: 15.3 GiB of RAM Graphics Processor: Intel® Iris® Xe Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: Vivobook_ASUSLaptop X1502ZA_F1502ZA System Version: 1.0
Thank you for the bug report! However Plasma 6.3.6 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need help with Plasma 6.3.6, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE. If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.