1711166 - No 60hz support in Xwayland

Status: RESOLVED DUPLICATE of bug 1640779

(Core :: Widget: Gtk, enhancement, P3)

Description

[velosterspeed]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

Open Firefox in Wayland, and scroll/do anything

Actual results:

It is at 60hz. If I go into the UFO tester site, it shows the monitor is 60hz, even though my monitor is 120hz

Expected results:

It should have been running at 120fps or 120hz. This does not happen on other applications, or when I am running Firefox in Xorg.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 2

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

Robert, any idea here? Don't we have the vsync enabled?

Comment 3

[Jan Alexander Steffens [:heftig]]

A Mutter bug, maybe? When I set my monitor to 48 Hz (GNOME 40.1), xrandr reports XWAYLAND1 at 48 Hz but glxgears and Firefox still seem to render and display at 60 Hz.

Comment 4

[Robert Mader [:rmader]]

I'm not sure, but IIUC this is a default setup. That would imply Basic compositor on Xwayland - which indeed does not use any kind of Vsync.

velosterspeed: can you attach the content of your about:support here to validate this? Meanwhile, setting the env variable MOZ_ENABLE_WAYLAND=1 should get you the actual FF Wayland backend with vsync.

Comment 5

[velosterspeed]

I'm on mobile right now, but I did not mess with my about:config at all aside from turning on the scrolling physics (its the same with it off). How would I set the env variable?

Comment 6

[velosterspeed]

Ok So doing what Robert says fixes my issue of only 60hz, but then I get entirely new bugs. Hovering over links does not change the cursor. If I put downloads in the overflow menu and try clicking on it, it closes on its own in a fraction of a second. I imagine there are more bugs but this is what I am getting right now.

Comment 7

[Robert Mader [:rmader]]

Hovering over links does not change the cursor.

This sounds very much like compositor bugs - could it be that you run an older version of Gnome or KDE? In any case, what you can also try is not setting MOZ_ENABLE_WAYLAND=1 but force-enabling WR (gfx.webrender.all in about:config).

In any case, please whenever opening bugs, provide the content of your about:support so we have a rough idea what kind of setup you're running. (Wayland/Xwayland/X11, Gnome/Kde etc.).

Comment 8

[velosterspeed]

I am running the latest GNOME force enabling gfx.webrender.all did not do anything it was still running at 60hz. I am not sure how to actually attach my about config, is there a file somewhere with all the contents?

Comment 9

[Robert Mader [:rmader]]

(In reply to velosterspeed from comment #8)

I am running the latest GNOME force enabling gfx.webrender.all did not do anything it was still running at 60hz. I am not sure how to actually attach my about config, is there a file somewhere with all the contents?

Oh right, sorry, forgot that we don't have proper Vsync on Xwayland but just get a fallback 60Hz timer :( Concerning about:support you can simply click "Copy raw data to clipboard" and paste it here. Bugzilla will offer you to turn it into a attachment, which makes it easy to read. If you're running latest Gnome, then it's somewhat unexpected that you run into those other bugs on the Wayland backend, but you may want to check if somebody else reported something similar in bug 635134 or bug 1633989.

Comment 10

[velosterspeed]

Attachment: about conf

Comment 11

[velosterspeed]

Sorry to revive this old report, but recently when I try click on links outside of firefox, it tells me that it is already running but not responding? This is fixed if I take out the MOZ_ENABLE_WAYLAND=1 from my .desktop file

Comment 12

[Martin Stránský [:stransky] (ni? me) (PTO, back on Feb 17)]

(In reply to velosterspeed from comment #11)

Sorry to revive this old report, but recently when I try click on links outside of firefox, it tells me that it is already running but not responding? This is fixed if I take out the MOZ_ENABLE_WAYLAND=1 from my .desktop file

If you want to run Firefox in Wayland/X11 mixed environment you need to set MOZ_DBUS_REMOTE env variable too.

Comment 13

[Robert Mader [:rmader]]

So while this bug was not about the Wayland backend (but rather the Xwayland), it should have been fixed by bug 1640779.