Support us on Patreon
PayPalCollabora have shared a great progress update on getting Wine working directly with Wayland, which is going to eventually replace X11 on most Linux distributions.
Notes for newbies: Wine is a translation layer that can run Windows games and applications on Linux, Wine is a huge part of what makes Steam Play Proton do anything. Wayland is the next-generation replacement for the ancient and now mostly unmaintained X server on Linux.
Originally announced in late 2020, Collabora has been developing a Wayland driver for Wine. The idea is to hopefully remove the need for XWayland and remove one more layer between things causing more complexity and likely performance hits. Collabora engineer Alexandros Frantzis has now put up an RFC (request for comments) onto the Wine development mailing list, so they can hopefully find the best way on progressing it and getting it upstreamed directly into the Wine project.
The focus of this update is to support a number of new features that are useful for applications and games, and which have also been considered potential integration pain points for the Wayland driver. These are copy/paste, drag-and-drop and support for changing the display mode.
Copy/paste support works well in both directions (native Wayland apps <=> Wine apps) with many common formats already supported. Drag and drop works in the direction of native Wayland apps to Wine apps for many common formats.
Implementing the display mode change is particularly interesting since Wayland doesn't allow applications to directly change the mode in the display hardware. However a similar effect can be achieved for particular surfaces by scaling in the compositor (typically using the GPU). In case of a Wine mode that doesn't match the current compositor mode, the driver instructs the compositor to scale the window contents so that they appear as if the hardware display mode had been changed while respecting the aspect ratio.
You can see more in a video demonstration below:
Direct Link
Last edited by jens on 19 February 2021 at 5:32 pm UTC
oldominion Feb 19, 2021
Quoting: jensNice, with also Nvidia preparing for xWayland I guess I'm only missing Chrome/Chromium/Electron in Wayland land.
Does Chromium or vscode not work on Wayland?
Last edited by Shmerl on 19 February 2021 at 5:50 pm UTC
-Improvements in the Wayland compositors
-Replacement of OpenGL in favor of Vulkan
-Replacement of Pulseaudio/JACK in favor of Pipewire
-Freesync with HDMI
-Wayland as default for Wine
I'm always happy when I see one of those things going forward :)
Quoting: oldominionQuoting: jensNice, with also Nvidia preparing for xWayland I guess I'm only missing Chrome/Chromium/Electron in Wayland land.
Does Chromium or vscode not work on Wayland?
Currently no. They are working on it though.
Quoting: BielFPs-Freesync with HDMI
I'd prefer HDMI to disappear and be replaced with DisplayPort everywhere.
Quoting: ShmerlI'd prefer HDMI to disappear and be replaced with DisplayPort everywhere.
Me too, but as a owner of a notebook with only HDMI (2.0) output, I would like to see this on Linux too.
But I agree with you, display port is way better and I wish Raspberry and More televisions could have it as default, but unfortunately that's not the case.
Last edited by BielFPs on 19 February 2021 at 8:00 pm UTC
At least the editor had a window fade. The wine windows don't, fair enough. It's all so ugly!
TheRiddick Feb 20, 2021
People on gnome or plasma for example who don't want to switch to tiling or some experimental compositor cannot change gamma.
Additionally I notice with plasma wayland the window rules system seems to be broken, it won't remember position correctly even if you set a global rule, it seems to behave differently then X11 where I set a exact window title global rule and everything just remembers position and size without too much issue.
Also had a issue with firefox not being accessible while a fullscreen app/game was open and minimized. But I think there is a Xwayland specific flag you can launch firefox with to work around that. Still, lots of annoying issues still (on top of already X11 feature limits).
Until issues like this get resolved, I won't be touching wayland. If they never get resolved.. well that will be very bad because normal desktop users are not going to tolerate that BS. (I consider myself an advanced desktop user (not tiling), I can work around issues even use custom builds of apps to resolve issues, but its a pain in the butt really!)
Last edited by TheRiddick on 20 February 2021 at 9:44 am UTC
Quoting: TheRiddickAlso had a issue with firefox not being accessible while a fullscreen app/game was open and minimized. But I think there is a Xwayland specific flag you can launch firefox with to work around that. Still, lots of annoying issues still (on top of already X11 feature limits).
Why are you running Firefox through XWayland in the first place? Native Wayland support is pretty damn solid by now.
Perhaps you meant you're facing this issue using the native backend, thus resort to using XWayland with a related flag to work around the bug?
See more from me