SUMMARY When I log in back after the user was locked because of inactivity, the refresh rate is locked to the internal monitor's max refresh rate (I use a laptop that has a monitor with 90hz and an external monitor with 144hz). STEPS TO REPRODUCE 1. Disable the internal monitor and have an external monitor with higher refresh rate plugged in 2. Keep the laptop idle so it automatically locks the user 3. Log in back into the locked account OBSERVED RESULT - Refresh rate is locked at 90hz (laptops refresh rate) and cannot be fixed by changing the refresh rate in Display Settings - Display settings still show the correct settings (144hz even when it is set to 90hz) A QUICK FIX - Enable the internal monitor and then disable it. For some reason, the moment you enable the internal monitor, it fixes all the problems. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: Zenbook UN5401QAB_UN5401QA System Version: 1.0
Please attach the output of drm_info when it's working normally, and when the refresh rate is wrong.
(In reply to Zamundaaa from comment #1) > Please attach the output of drm_info when it's working normally, and when > the refresh rate is wrong. I don't have an executable named drm_info. Is this GitHub repo what I need to install ? https://github.com/ascent12/drm_info
Yes
Created attachment 150849 [details] log before the bug happens
Created attachment 150850 [details] log when the bug happens (after logging back in)
Created attachment 150851 [details] log after enabling and disabling the internal monitor
Looks like what system settings reports is actually correct: your monitor is running at 144Hz. How are you noticing that the refresh rate is wrong?
(In reply to Zamundaaa from comment #7) > Looks like what system settings reports is actually correct: your monitor is > running at 144Hz. > > How are you noticing that the refresh rate is wrong? Well, there is a big difference between what is set after the glitch and 144hz. I was just guessing it was using a lower refresh rate because it looked like it. Responsive time when clicking on the app launcher was normal. Resizing was normal. Everything was normal, except it was laggy and to me, it looked like the refresh rate has been lowered which is solved by enabling and disabling (you have to apply both changes) the internal monitor.
Can you record a video of the screen while it's slow? Ideally with system monitor open
(In reply to Zamundaaa from comment #9) > Can you record a video of the screen while it's slow? Ideally with system > monitor open I will only be able to do so in 4 days because currently, I don't have an external monitor on my hands.
(In reply to Zamundaaa from comment #9) > Can you record a video of the screen while it's slow? Ideally with system > monitor open https://cloud.aljaxus.eu/index.php/s/npSmqyXfGw7Lo5W
We've made big improvements to render time tracking and frame scheduling in Plasma 6, so this bug is most likely fixed. In case you're still experiencing it, just reopen this