Wine's Wayland Driver Is Becoming Mature, May Aim For Upstreaming Early Next Year

[skeevy420]

Sometimes Firefox seems to become confused when switching between maxed/tiled mode and free floating. All the content will be rendered a bit off vertically, maybe 64 pixels or the size of the tab bar. You also need to switch between windows so that it redraws the window and the glitch disappears.

Also, on KDE Wayland, sometimes Firefox will crash when going between windowed and fullscreen modes which will make it forget to render at 200% resolution scale until a logon cycle is done and videos will crash Firefox if you leave them paused while the screen goes into standby,

I wonder which will work better first: Firefox via Wine and Wayland or Firefox via Linux and Wayland

[skeevy420]

Did they finally implement OpenGL support? I remember they said not so long ago about Vulkan (i.e. DXVK) apps only.

A significant improvement compared to last year is support for
cross-process rendering, which is required by Chromium/CEF applications.
Last year the driver was able to run Chrome with the "--in-process"
command-line option. This year Chrome is supported without any special
flags, fully GPU accelerated on both OpenGL and Vulkan! This was
achieved by implementing what is effectively an internal off-screen
swapchain in the driver's OpenGL and Vulkan integration code, along with
a mechanism to send buffers to other processes for presentation when
needed.

This update also brings enhanced support for the linux-dmabuf v4 Wayland
protocol (aka dmabuf-feedback), which allows compositors to dynamically
send information about optimal formats and modifiers, e.g., depending on
the surface presentation mode (fullscreen vs windowed). Our new
internal OpenGL swapchain can handle such feedback directly, while for
Vulkan we rely on the Wayland WSI to provide this functionality.

That looks to be Yes.

[cypx]

Firefox is mostly good on Wayland although under Kwin clicking-and-dragging to tear out tabs into new windows is buggy.

Seems fix, I don't have problem anymore with that.

[pracedru]

Firefox is mostly good on Wayland although under Kwin clicking-and-dragging to tear out tabs into new windows is buggy.
Chromium under Wayland is generally OK if you are only using a 60 Hz display. It gets all kinds of glitches on high refresh rate monitors because it can't keep up with screen refresh rates of > 60Hz.

This is a KDE bug I think. It doesn't happen on gnome Wayland.

[SSJBurger]

This is a KDE bug I think. It doesn't happen on gnome Wayland.

Seems like the issues I had when I didn't know Firefox was running in xwayland mode and not Wayland.

[Zeioth]

Nice. Seems all we need is some more mature Wayland support from Firefox and Chromium and we can leave X11 behind for good.

What do you mean? I've been using Firefox with native wayland for a solid year now and it works great. Now chrome.. that's another thing. Google doesn't seem to be in a hurry.

90% of my applications are wayland native at this point. I think once this is patch is released I should be able to remove xwayland safely.

[TemplarGR]

What do you mean? I've been using Firefox with native wayland for a solid year now and it works great. Now chrome.. that's another thing. Google doesn't seem to be in a hurry.

90% of my applications are wayland native at this point. I think once this is patch is released I should be able to remove xwayland safely.

I have been using Firefox on Wayland only for more than a year.... It still isn't available by default if i am not mistaken.... And there have been bugs....

[cl333r]

Unfortunately, Wine on Wayland can run into a lot of trouble when attempting to reduce the latency of windowed Windows applications. This happens because Wayland is unable to provide the information on the expected timing of the front buffer flip event, as described in another thread (from this post untill the end of thread).

It is unfortunate that, due to this ommision in Wayland, the users of Wine on Wayland will experiance a sub-optimal desktop experience.

I don't know if it has anything to do with this case but KDE on Wayland (Ubuntu 22.10) starts lagging for no apparent reason some time after I log in, the input events may take a second or 2. After I reboot all is fine, for a while. Which is why I stay with X11 for now.

[Sethox]

What do you mean? I've been using Firefox with native wayland for a solid year now and it works great. Now chrome.. that's another thing. Google doesn't seem to be in a hurry. 90% of my applications are wayland native at this point. I think once this is patch is released I should be able to remove xwayland safely.

Yeah same here, The only missing piece for pure Wayland native (and not XWayland) is the Steam client, Pipewire is already in there which can creates some cool features for stream capturing.

[CochainComplex]

I suspect that the majority if waylandissues can be tied to Nvidia drivers? I m using wayland and Firefox on GNOME now cosmiq since years and with mesa (Intel/AMD) I cant recall any glitches in the recent one maybe two years.