SUMMARY My TV supports resolutions up to 4K and different refresh rates apply for each resolution. When I change from one resolution to another (in the specific case, from 4K to FHD), I still see the refresh rates of the first resolution. So in my case, 4K supports up to 30 Hz, while FHD goes up to 120 Hz; switching from 4K to FHD shows the correct resolution, but the UI keeps on saying that the TV is at 30 Hz when really it is working at 120 Hz. Clicking on another KCM (e.g. compositor) and then coming back to the KScreen KCM shows the correct refresh rates. Oddly enough, this does not apply in reverse: if I switch from FHD at 60 Hz to 4K, the new refresh rate of 30 Hz is correctly detected and shown by the KCM. STEPS TO REPRODUCE 1. Switch from one resolution with low refresh rate to another with a high refresh rate. OBSERVED RESULT The refresh rate is not updated and is therefore shown incorrectly. EXPECTED RESULT The refresh rate is updated and shown correctly. SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION This happens in X11 on a desktop machine with just one monitor, which is an LG webOS TV, using an AMD Radeon RX 5700 with the latest Mesa drivers and Linux 5.15.22. The TV is connected through an HDMI cable.
Does it happen on Wayland too?
As mentioned in the other bug: I have no idea, I don't use Wayland and the session doesn't work, so I have no way to check this.
I see this too
I'm very certain that this bug has been fixed with 5.24.6 / 5.25.0 (https://invent.kde.org/plasma/kscreen/-/commit/6ecb832923612820c721f58d1d12dd176e10528a) and it's still working correctly here (In reply to David Redondo from comment #3) > I see this too This bug report is about the refresh rate list not adding or removing the refresh rates of the currently selected resolution, are you talking about the same thing? Because KScreen auto-selects the current refresh rate whenever you change the resolution, that's intentional and not a bug (though it auto-selecting the highest refresh rate would probably make more sense)
I will double check but it could also be only an issue in the UI if it sitll happens.
Was anyone able to reproduce the issue in Plasma 5.24.6 or 5.25.0 or later?
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!