Bug 101383

Summary:	Refresh rate is locked to 60 Hz
Product:	Wayland	Reporter:	ominous
Component:	wayland	Assignee:	Wayland bug list <wayland-bugs>
Status:	RESOLVED NOTOURBUG	QA Contact:
Severity:	major
Priority:	medium	CC:	cfeck, jadahl, jhasse
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description ominous 2017-06-12 01:33:41 UTC

I have tried GNOME on Wayland on both Debian testing and Fedora 26 and I was unable to truly change my refresh rate.

I can pick the refresh rate I want from the list, apply it, my screen goes black and comes back.

144 Hz is reported in xrandr but the screen is still on 60 Hz. This does not happen on GNOME on X and I am able to change it effectively just fine there.

This is the only thing stopping me from using Wayland, sadly. Has somebody been able to effectively change their refresh rate?

Comment 1 Jonas Ådahl 2017-06-12 03:52:58 UTC

It's currently not possible to affect the refresh rate of the actual drawing. This is not by design; it's simply not implemented. Making it work involves updating MetaRendererNative to pass around refresh rates and presentation timings to ClutterStageCogl, so that it can schedule frames given the actual refresh rate of the monitor. Currently, it'll just fall back on 60 Hz, which of course is not good.

Another related issue is that if one monitor is 144 Hz, while another is 60 Hz, we'd still end up drawing at 60 Hz, as mutter still doesn't support drawing separate monitor as individual frames.

In other words, making it work with multiple monitors with different refresh rates is non-trivial, but making it (non 60 Hz refresh rates) work for just a single monitor is probably not very hard.

Comment 2 Pekka Paalanen 2017-06-14 08:08:54 UTC

This not a Wayland bug, this is a bug in the specific compositor implementation.

Could someone provide a link to the Mutter bug report and close this one as NOTOURBUG or so, please?

Comment 3 Jonas Ådahl 2017-06-14 08:12:43 UTC

(In reply to Pekka Paalanen from comment #2)
> This not a Wayland bug, this is a bug in the specific compositor
> implementation.
> 
> Could someone provide a link to the Mutter bug report and close this one as
> NOTOURBUG or so, please?

Sorry, didn't notice this was not GNOME's bugzilla. Frederique, could you report this on GNOME's bugzilla?

Comment 4 Jonas Ådahl 2017-06-14 08:13:58 UTC

Nm, there is one there already: https://bugzilla.gnome.org/show_bug.cgi?id=781296

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.