A set of merge requests were opened that would effectively drop X.Org (X11) session support for the GNOME desktop and once that code is removed making it a Wayland-only desktop environment.
Going along with Fedora 40 looking to disable the GNOME X11 session support (and also making KDE Plasma 6 Wayland-only for Fedora), upstream GNOME is evaluating the prospect of disabling and then removing their X11 session support.
Some concerns were raised already how this could impact downstream desktops like Budgie and Pantheon that haven’t yet fully transitioned over to Wayland. In any event we’ll see where the discussions lead but it’s sure looking like 2024 will be the year that GNOME goes Wayland-only.
What’s everyone’s Wayland showstopper?
I’m holding out for better autoclickers/macro recorders before I go to Wayland
Better Wine support. It’s coming soon, but I prefer xorg until Wine properly supports Wayland.
I would say Xwayland is good ENOUGH, but it’s not great, my clipboard with xwayland is awful on sway, for example. It works, but not the best.
Honestly, Wayland just doesn’t give the impression of working well enough with everything to replace my window manager and all kinds of utilities that grew around it (or X11 in general) for a decade or two just to only notice after using it for a few weeks that it won’t work with some things. It demands a huge time investment up front for questionable gain basically.
As a multimonitor user with mixed properties, and an AMD user, Wayland has been nothing but a massive gain for me and continues to get better in equally massive strides on KDE (been using kwin-wayland for almost a full year as a daily driver now). It even improved the user experience on my surface pro that I’m running the surface-linux kernel on.
I am not using a Desktop Environment and if switching to Wayland means I will have to give up tiling window managers for DEs I will never switch to Wayland.
The time-investment is short-term pain, long-term profit. That’s kinda our thing as Linux guys
But where it the long-term profit? Every time Wayland comes up in the last 15 or so years since it was first mentioned somewhere it is an endless list of comments about things that don’t work and “will work soon” ™. Meanwhile in all that time there hasn’t been a single exploit for the security issues Wayland claims to fix. X11 has worked just fine for all this time.
I am not opposed to replacing things in general (e.g. I do like systemd and never want init scripts back) but Wayland just seems like a bad design with bad goals and bad implementations.
Mine’s mostly just bad electron app support for native Wayland. In theory Electron now offers full Wayland support but hooooo boy is it going to be a while until all of the electron garbage I use finally updates to a new enough version for proper support.
The other gotcha is just general client side decorations support for apps in general. I’m shocked that no one has built a small libadwaita wrapper library that implements client side decorations for apps. It’s going to be ages until app developers all implement their own (crummy) CSD that doesn’t match system themes at all.
You can still use XWayland though, it’s not going anywhere. They are only removing the ability to run a X11-only session.
I play Heroes of the Storm through Lutris.
I have a superultrawide 32:9 monitor.
In X11, I can get HotS to scale past its normal limits just like I could in windows and take up a full 5120x1440 resolution.
In Wayland, I can’t.
I will die on this hill.
thy gamescope(that run on steam deck) i think it can scale, if yes, so it’s an implementation issue, that need to be fixed by the compositor
need to be fixed by the compositor
It is a Wayland issue that things like this need to be fixed per compositor. Honestly, what were the designers thinking?
I found no Remote Desktop solution to be working well together with wayland. (I’m not quite sure, if wayland was the cause of the issues I had with RDP and VNC, have to test that). The proprietary Remote Desktop all show a warning that wayland is not supported. While TeamViewer does kinda work, despite the warning, it is not a very sable connection.
I’ve tried this out, and its promising (KDE Plasma RDP Server). https://planet.kde.org/arjen-hiemstra-2023-08-08-remote-desktop-using-the-rdp-protocol-for-plasma-wayland/
I don’t know if this would work for whatever your remote desktop needs are specifically, but I use Sunshine and it works really well.
I have a older iMac running openSuse tumbleweed GNOME and would like to be able waking it up using my iPad an start a remote season in my iPad from my couch/kitchen, so I can watch my child while do some fun linux stuff (I’m relatively new in the scene) First problem is the waking up part: I had to forcefully disable susbend because the screen was always very glitchy upon wake up (open source readon driver). I used this command for that: sudo systemctl mask suspend.target So I have to wake the iMac from off state or find another sleep mode or fix hibernate to solve the issue. I plan to research if there is way to use wakeOnLan for that.
Second problem was the screen remote on wayland which right now resulted in me using teamviewer on GNOME on Xorg. I don’t really like this setup and I’m looking for FOSS alternatives which preferably work on wayland and idealy would allow to ise multytouch gestures.
It’s never going to happen on Wayland level. It’s absolutely no problem to implement this on a compositor level.
For whatever reason it can’t seem to suspend my thinkpad. Everything crashes and when I open the lid I have to log in again :/
Is that a Wayland issue? Lots of modern laptops have suspend issues (broken S0ix sleep, missing S3, bios declaring wrong states, etc)
I can only assume it’s wayland causing the crash. When I run gnome45 in x11, it suspends and resumes normally, but when I run in wayland upon resume everything is gone, regardless of what was running. I’ve combed through dmesg to find out what’s happening but it hasn’t been too fruitful so far.
i tried rhis autoclicker https://github.com/konkitoman/autoclicker and worked flawless(just needed ticker the suders file because cargo install on .local/bin), but if someone could suggest a macro recorder i appreciate!
Wayland is much better in the long term. People work on it every day and improve it, while X11 gets less and less supported plus X11 is carrying deprecated junk from the last decades
