I think I’ve used wayland for long enough to be sure that I don’t need the x11 session. Is there a clean way of removing it on Arch Linux without breaking the wayland session?
1 Like
You could, possibly, use the Arch Linux pacman to check the package dependencies –
<Dependencies of a package>
<pacman/Tips and tricks>
Unfortunately, plasma appears to depend on many xorg packages, and also there is no option for deleting a session type [yet, you can if you want to make a feature request [I cannot say anything how well it will go lol, or if it will be considered]] [also doesn’t make that much sense, having another session type isnt a whale trying to fit into your drive]
How Fedora’s KDE spin not have a X11 session?
X11 is the only lifesaver when Wayland is broken, and also the only way to use KDE Plasma on some old hardware, normally it should never be removed and stay as safe mode.
Fedora is just testing ground for the commercial Red Hat Enterprise Linux., so most of what they do is always not driven by the community.
Wayland breaking wouldn’t affect me because I have all my files backed up and I have a single long command that installs everything, my notebook is from 2023, and I’m using Arch because it’s bleeding edge.
Anyway, seems like it’s not possible (in a streamlined way) yet.
Well you are well prepared and have enough time to reinstall and reconfigure your whole system and applications, unlike average users who are not aware of such measures and don’t have time to do it from scratch each time things broke, for example 6.2 broke Wayland and I was unable to work on my laptop for many hours until I remembered I still have X11 which made it easy to continue using my system and getting things done while waiting for Wayland to be fixed.
1 Like
And some other just use things like timeshift, and know how to use that even “chrooted” from a USB-livesystem boot. When 6.2.1 wayland broke my system I was back at a running 6.2.0 10-15 Minutes later, and that included 5-10 fiddling around with the problem first.
But to the Topic.
Unless I desperately need the disk storage I would not even care and just leave X11 unused.
1 Like
Presumably, there were enough developers and testers involved to ensure that, the removal of the X11 components would not affect the system’s operation.
- Given the financing of Fedora Project, one could presume that, paid developers and testers were involved …
IMO there are enough examples of the Fedora Project’s actions diverging from anything that Red Hat/IBM would commercially care about (Btrfs as default even though RHEL moved away from it, caring about KDE at all even though RHEL only officially supports GNOME) that I don’t assume “Red Hat demand” as the reason behind a Fedora change.
In this case, I think ample reasons were given other than “Red Hat wants it”:
1 Like
Unless something changed, I thought sddm itself used x11 to get the initial login screen even if you ultimately launch a Wayland session.
I use openSuse Tumbleweed and I’ve been running it without X11 for several months. Wayland only.
Iirc, there was a config file I needed to poke at to get SDDM to load as expected. One of the pain points I had was the system’s systemd setup had a hard time understanding that I didn’t want X as my display manager. It wasn’t a hard package dependency, but rather that since X didn’t run, some other unit file that claimed a dependency on it wouldn’t get run either. I remember doing a systemctl edit on something.
I don’t mind taking the time to dig up the changes, so if you want, let me know and I’ll report back.