For those wanting to build a Wayland-only Linux desktop experience without carrying any aging X11 baggage, GNOME 47 will be able to optionally offer Wayland-only support without carrying X11/X.Org support. This Mutter merge request landed today that allows compiling Mutter with X11 support disabled. That landed today along with this GNOME Shell merge request for being able to disable X11 support too.
I wonder how long it’ll be possible to build Gnome with Xorg support. If I had to guess I’d say there won’t be any support within the next 3 years, because keeping future Gnome working with Xorg is work nobody wants to put in.
That said, Xwayland will likely keep being around for the foreseeable future.
Out of curiosity, do you use Xorg and if yes, what’s keeping you from using Wayland?
XOrg is my daily driver for these reasons:
That being said, I have no fundamental opposition to Wayland, and will probably use it someday.
Those are all good reasons. XFCE aims to support Wayland with the next release, so if they choose to use an established compositor it shouldn’t be too buggy.
With XFCE porting their apps over the setup shouldn’t change much, unless you’re using Xorg specific tools.
Over the last few years most features I’d expect from a windowing system were added to Wayland, so I expect the drama to cool down. (I don’t even know what’s still missing (except accessibility), with VRR, tearing, DRM leasing (VR), and global hotkeys being done. It’s just apps like Discord that have to cave in under the pressure to fix their apps.)
Once everything works, there’s no point talking about it.
@Furycd001@fosstodon.org
I totally expect one day a XFCE (Wayland) option will show up, I will click it, forget I did, and use it forever more.
https://wiki.xfce.org/releng/wayland_roadmap
I switched to Wayland after GNOME 46 release because it fixed the issues I had with it (artifacts and persistent display failures). Many people may still prefer X11 at least because of the lack of input latency on slow machines.
Proper screen sharing and xclicker is Why I occasionally switch back to X
Not OP, but I use sunshine and moonlight for streaming my pc to various devices. Wayland forces me to use kms and I can’t turn the monitors off while I’m doing it. Someone was working on a pipewire backend, so hopefully that goes somewhere.
GreenWithEnvy is also a nuisance on Wayland while Nvidia Settings Panel doesn’t even work. I have a custom script just to control my fans on Wayland, but I’m eventually switching from Nvidia anyways, so it won’t matter for much longer.
deleted by creator
The primary maintainer stepped down, but there has still been work done by other contributors. The primary problem is that the underlying library is reliant on x11. This is the same reason why nvidia-settings doesn’t have all of its features on wayland. Basically if nvidia’s on tool doesn’t work then there is no way that green with envy can either. There is an open merge request attempting to switch to a different library that Nvidia says they plan to move to eventually, but it is slow going.
deleted by creator