Bug 468304 - KWin locks refresh rate at 60 Hz when configured for 120 or 144, no problem with 165 Hz
Summary: KWin locks refresh rate at 60 Hz when configured for 120 or 144, no problem w...
Status: RESOLVED DUPLICATE of bug 468235
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.27.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-08 20:28 UTC by Egor Kuznetsov
Modified: 2023-04-08 21:40 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 Egor Kuznetsov 2023-04-08 20:28:10 UTC
SUMMARY
I noticed that if I enable the AMD Freesync option in the monitor settings, and then set the screen refresh rate in the monitor settings to be different from 165 Hz and possibly higher, the monitor and KDE continue to run at 60 Hz. However, this behavior does not depend on the set option for Adaptive sync in Display Configuration in System Settings (if I set Never, for example, Hz lock still exists)


STEPS TO REPRODUCE
1. Turn on AdaptiveSync (maybe it will be called FreeSync in other model of displays) in display settings
2. Choose any refresh rate up to 165 Hz
3. Accept new refresh rate

OBSERVED RESULT
Display says that refresh rate is 60 Hz and I visually noticed that desktop compositing still runs at 60 FPS

EXPECTED RESULT
Display must operate at the frequency specified in the display settings

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230407
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: ASUS

ADDITIONAL INFORMATION
If it can be helpful, Display model is MSI G27CQ4 E2. I use DisplayPort for connection
Comment 1 Zamundaaa 2023-04-08 21:40:37 UTC

*** This bug has been marked as a duplicate of bug 468235 ***