Bug 400791 - Wrong reported refresh rate on 75hz monitor
Summary: Wrong reported refresh rate on 75hz monitor
Status: RESOLVED LATER
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-07 09:59 UTC by tromzy
Modified: 2018-11-07 19:18 UTC (History)
0 users

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 tromzy 2018-11-07 09:59:43 UTC
SUMMARY
On a Wayland session, I have a dual monitor setup : the laptop monitor is at 60hz and the external HDMI monitor is at 75hz. If I set the external monitor to 75hz in the Display KCM module, the OSD on my monitor reports 74.8 Hz which is good. But any application on the desktop reports 60 hz. Now, I have read that there were problems with XWayland reporting incorrect refresh rate values, but even native Wayland applications (Falkon, Retroarch) report 60hz.

STEPS TO REPRODUCE
1. Use a dual monitor setup with one monitor at 75hz
2. Try to set 75hz on the monitor
3. The desktop seems to be stuck at 60 hz / 60 FPS.

OBSERVED RESULT
The desktop seems to be stuck at 60 hz / 60 FPS.

EXPECTED RESULT
Applications should report 75hz instead of 60.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
Archlinux, Intel Modesetting
Comment 1 Martin Flöser 2018-11-07 19:18:18 UTC
KWin does not have a per-screen render loop. Due to that the refresh rate of all screens is limited to the lowest refresh rate. So far what you experience is the expected behavior given KWin's internals.

I'm setting to RESOLVED/LATER as this is currently not a bug which we can fix, more like a new feature we need to implement. Once we have implemented a per screen rendering it will automatically resolve. Given that I think LATER makes most sense.