this post was submitted on 22 Jan 2026
38 points (100.0% liked)
Linux
11277 readers
243 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't want to move to systemd, I'm happy with OpenRC. And I hope this move doesn't force systemd on those of us using Linux and KDE.
That being said some devs (Gentoo devs?) cherry-picked some tiny parts from systemd and made packages for those parts so that when you want to install something with a hard dependency on systemd but you're using another init system (like Gentoo's default OpenRC) you will be fine without actually installing the whole systemd thing.
Maybe the FreeBSD folks can think of something similar, but I don't know. Last time I looked when there was no official efforts from KDE to bring it to FreeBSD they bitched about it because it was "bloat".
You can keep using sddm. It isn't being discontinued. In fact you can use any login manager you want. Plasma is not going to enforce one.
I personally am happy about the new plasma login manager, because it will allow features they couldn't reasonably implement with sddm.
The people upset about this is a classic case of getting upset about things that won't affect them at all.
I would think that elogind should work? Is it hard dependent on systemd or logind? I thought it was the latter
PLM is hard dependent on systemd.
That's the part that confuses me, because allegedly GNOME has a hard dependency on systemd yet in Gentoo you can install GNOME without having to install nor use sytemd. I hope this new KDE login manager can work the same or a similar way, though
gentoo uses elogind to emulate the systemd interfaces required by gnome
@refalo @mmmm #guix also follows this philosophy, but uses #shepherd as the root process.
That's unfortunate