I think this makes sense. I still need X11 for VR because GNOME still doesn’t have display leasing on Wayland but once that gets implemented I won’t be using X11 anymore. I think most people don’t need X11 anymore either. For people like me who still need it for specific things, it can just be installed again manually.
On my RTX 3080 laptop I get a significantly lower frame rate on my laptop screen (240hz) and 4k external monitor (144hz) when using Wayland. Wayland has come a long way but I’m still going to be using X11 for at least the near future.
I would support this, but Wayland always lacks support for remote. I have to switch to x11 if I want to work on it via teamviewer (past) or rustdesk (present).
I just tested freerdp on gnome wayland and it works (via Settings -> Sharing -> Remote Desktop). Combined with tailscale/zerotier, you should be able to remote from anywhere via RDP.
It cannot be used to log in, potentially can’t even unlock but I haven’t used it in a while (Edit: confirmed it cannot connect if locked). A reboot preventing access until I go back to the local console is not fun.
I realize for their rustdesk example it’s not really different iirc, but there are solutions for x11.
This works in a private network you own. But my remote system is at work. I can not use it with full automatic login. Hell it’s even encrypted and has a BIOS PW.
@redcalcium@e8d79 The noVideo experience on Linux dramatically improved, especially with the latest driver versions and modern DIVORCE GPUs. We also kinda have to accept the death of X11
I sure hope so. Just the other day I updated to nvidia v550. Got a blank tty screen right after login to gnome/wayland. Rebooted the computer and login to gnome/x11, no issue. Logout and relogin to gnome/wayland, somehow no issue anymore. I guess this kind of random issues will persist until one day Nvidia decides to play nice with Wayland.
It’s horrible. My laptop with hybrid graphics works ok except for a brief flicker every time it wakes from sleep. It’s not a big deal. My desktop with dedicated nvidia is a hot mess - constant flickering. Steam is borderline non-functional and there are all kinds of graphical glitches on the desktop. I’m stuck with X11 on that machine.
Being the first major distro to force the adoption of new technologies is kinda Fedora’s whole thing, so it’s not really surprising. It’s annoying for people on Fedora who use features Wayland doesn’t have yet, but they can jump through a few hoops to get X11 back, or better yet switch to a distro that cares more about giving users options than they do about beta testing new technologies for their corporate overlords.
Still, somebody has be first, and it’s past time to get serious about this whole transition, so I can hardly try to claim this is a bad thing.
Plasma 6 still installs the X11 session. This change will make it so the Gnome X11 session is not getting installed by deafult, so you need to install it yourself if you need it. In Plasma 6, you just change to the X11 session in your Display Manager.
Because Gnome defaulted to Wayland for a long time, before they now plan to ditch it’s X11 session, while Plasma just recently started defaulting to Wayland. I think Fedora 38 is when they defaulted to wayland in the Plasma edition. Gnome had a way longer lead time, IIRC.
No, it is not the same thing. From the Pagure issue:
From my recollection the WG earlier discussed about the removal of gnome-session-xsession, but we decided not to do that (wisely) until upstream drops it
It’s not like KDE, and when someone updates to F40, it won’t even remove Xorg. It just won’t be installed by anaconda by default in new installs.
Your quote describes literally the exact same thing that Fedora KDE 40 does. Yes, they wanted to go further and remove the Xorg bits already, but that got rolled back.
The KDE packaging team is no longer packaging Xorg, but the GNOME team is. The “re-upstreaming” is a completely different effort with no guarantees on bugs. In addition, the package providing Xorg support in KDE is to be marked obsoleted and will be removed when upgrading. Here’s the actual ruling:
KDE packages which reintroduce support for X11 are allowed in the main Fedora repositories, however they may not be included by default on any release-blocking deliverable (ISO, image, etc.). The KDE SIG should provide a notice before major changes, but is not responsible for ensuring that these packages adapt.
GNOME Xorg still has full support from the team that has always worked on GNOME, unlike Plasma’s Xorg on Fedora 40.
Tbf Wayland released 15 years ago but its an ecosystem rather than one tool. Wayland has evolved and other parts of the system have been built and refined. Plus XWayland compatibiliry layer is an essential component as so little software has been rewritten to work with wayland natively.
We’re only really now at the point where most users can use wayland by default without errors. But I’m still experiencing software and tools that force me to go back to X11. It makes sense for Fedora to drop X11 as default if it’s a more “cutting edge” distro but I don’t think Debian for example will be doing so for years to come.
It also means years for Fedora. They have a development cycle too. Things that they announce today might be considered for the next cycle and might actually make it in Fedora two cycles from current.
I agree with all that your said, but my point is that software age has little to do with when something should be made default. It’s about being the right choice, like you said.
If we keep it up, in 10 years a new project to replace Wayland will be started, and in another 20 it’ll be replaced. Not bad, but not great. 3.6 Roentgen.
Add comment