Bug 444574 - kwin does not honor system setting for monitor refresh rate
Summary: kwin does not honor system setting for monitor refresh rate
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.23.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-29 01:45 UTC by jpandrusky
Modified: 2022-12-08 05:15 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jpandrusky 2021-10-29 01:45:53 UTC
SUMMARY
kwin does not set the configured monitor refresh rate on a fresh login.

STEPS TO REPRODUCE
1. Login from SDDM (0.19.0).

OBSERVED RESULT
Monitor refresh rate is set to 60Hz (verified in monitor OSD). System settings has the monitor refresh rate set to 144Hz. Refresh rate must be changed to 120Hz and back to 144Hz to set the monitor refresh rate to 144Hz (updated refresh rate verified in monitor OSD). This must be done on every login.

EXPECTED RESULT
kwin to set the refresh rate on login to the configured refresh rate, in this case 144Hz.

Operating System: Arch Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.14.14-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: AMD Radeon RX 6800 XT
Comment 1 jpandrusky 2021-10-29 23:37:06 UTC
Changing the refresh to 120Hz and reverting to '144Hz' also seems to work.
Comment 2 jpandrusky 2021-11-05 02:27:30 UTC
Changing to Kscreen. I've been doing some more digging and have found some strange behaviour using kscreen-doctor.

When I log in and run 'kscreen-doctor -o', I get the following:

Output: 1 GBT AORUS FV43U/21100B000422 enabled connected primary Unknown Modes: 0:3840x2160@144! 1:3840x2160@60 2:3840x2160@120 3:3840x2160@60 4:2560x1440@144 5:2560x1440@120 6:2560x1440@60 7:1920x1200@144 8:1920x1080@144 9:1920x1080@120 10:1920x1080@120 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1600x1200@144 15:1680x1050@60 16:1280x1024@60 17:1440x900@60 18:1280x800@144 19:1280x720@120 20:1280x720@120 21:1280x720@100 22:1280x720@60 23:1280x720@60 24:1280x720@50 25:1024x768@75 26:1024x768@60 27:800x600@75 28:800x600@60 29:720x576@50 30:720x576@50 31:720x480@60 32:720x480@60 33:720x480@60 34:720x480@60 35:640x480@75 36:640x480@60 37:640x480@60 38:3840x2160@60* Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown primary

Which says that I should be running at 3840x2160@144, but I'm actually only running at 38402x2160@60.

If I set the refresh to 120Hz and revert to 144Hz, it fixes itself and I'll actually be at 3840x2160@144, but the output of 'kscreen-doctor -o' is:

Output: 1 GBT AORUS FV43U/21100B000422 enabled connected primary Unknown Modes: 0:3840x2160@60 1:3840x2160@120 2:3840x2160@60 3:3840x2160@60 4:2560x1440@144 5:2560x1440@120 6:2560x1440@60 7:1920x1200@144 8:1920x1080@144 9:1920x1080@120 10:1920x1080@120 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1600x1200@144 15:1680x1050@60 16:1280x1024@60 17:1440x900@60 18:1280x800@144 19:1280x720@120 20:1280x720@120 21:1280x720@100 22:1280x720@60 23:1280x720@60 24:1280x720@50 25:1024x768@75 26:1024x768@60 27:800x600@75 28:800x600@60 29:720x576@50 30:720x576@50 31:720x480@60 32:720x480@60 33:720x480@60 34:720x480@60 35:640x480@75 36:640x480@60 37:640x480@60 38:3840x2160@144*! Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: unknown primary

The mode for 3840x2160@144 has changed to 3840x2160@60.
Comment 3 Nate Graham 2022-11-08 22:40:30 UTC
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26?

If it is, please add a comment with the output of `kscreen-doctor -o` and change the status to CONFIRMED. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!
Comment 4 Bug Janitor Service 2022-11-23 05:16:06 UTC
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!
Comment 5 Bug Janitor Service 2022-12-08 05:15:37 UTC
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!