Linuxiac - KDE/Systemd or sysVinit, you can't have both!

dos2unix

Well-Known Member
Joined
May 3, 2019
Messages
4,408
Reaction score
4,601
Credits
41,638


Linuxiac.com pages never display correctly for me.

Am I the only one?

Very few photos show; many of the ones that don't have a .bin extension. (May be my pfSense router's pfblockerNG ad blocker.)

Sorry to interrupt.
 
[Linuxiac]

From what I read in the article, it just means that PLM, the new plasma login manager won't be usable on non systemd systems. You'd still be able to use plasma/KDE - you'd just have to use a different login manager like sddm. Doesn't seem like an issue to me.
 
Copy/pasted from the article:

KDE Plasma Login Manager Won’t Support Systemd-Free Linux or BSD Systems​

KDE's new Plasma Login Manager is tightly bound to systemd, making it unusable on systemd-free Linux distributions and BSD systems.

It's clearly talking about PLM being unusable in BSD and any Linux-based OSes without systemd.
And in the middle of the article, it clearly states:
To avoid any confusion, it’s important to emphasize that the lack of PLM support on systemd-free Linux distributions or BSD systems does not mean you can’t use the KDE Plasma desktop environment there. Plasma itself remains fully usable on those platforms.

So it will only affect the new plasma login manager PLM. Plasma users on non-systemd linux and BSD can just use sddm, or any other login manager to start their KDE/Plasma session.
 
So it will only affect the new plasma login manager PLM. Plasma users on non-systemd linux and BSD can just use sddm, or any other login manager to start their KDE/Plasma session.

True, but then it's not 100% KDE solution, it's a hybrid.
 
But sddm is what KDE/Plasma currently uses. It's also used by LXQT (the project that merged LXDE and Razor-QT). And sddm is QT based. So it's therefore entirely compatible with KDE/Plasma. So I still don't see the problem!
 
I concluded the same as Jas. Seems to me it s KDE whom are making the hybrid, via PLM.

It's all academic until 17 February, anyway, I'll consider my options then.

Eleven distros in my stable use KDE, and I use sddm.conf to manage my HiDPI for login screen, I would want that functionality to continue.

Avagudweegend

Wiz
 
I am not really too concerned myself, because, as far as I can ascertain, SDDM will continue being maintained and retain a first-class citizen status within the KDE project.

The features presented as part of or exclusive to PLM are nowhere near significant enough to warrant me switching away from OpenRC (and elogind) in favor of SystemD.

Phoronix - KDE Plasma 6.6 Beta Released With Plasma Login Manager, Plasma Setup

GitHub - KDE/plasma-login-manager

I have never really found SDDM lacking so I will likely continue using it for the foreseeable future.
 
I'm not too concerned at the moment about this. SDDM works ok. Just will be a pain for some Distros that don't want to use systemd. Wonder how some of them will cope with it.
 
Last edited:
I will not use SDDM again. I'm going back to TTY login and a WM again.
 
I'm not too concerned at the moment about this. SDDM works ok. Just will be a pain for some Distros that don't want to use systemd. Wonder how some of them will cope with it.
Gentoo will be largely okay as we use the homegrown elogind for using GNOME and KDE without the need for SystemD (although we also have the option to use Gentoo with SystemD, I just like OpenRC better as I wanted to experiment with something new!), I believe some other SystemD-Less distributions also use it so they should be okay too, at least as long as SDDM continues being developed!

Edit: It would appear that Artix, Void, Slackware and CRUX leverage elogind already.
 
Last edited:


Follow Linux.org

Members online


Top