'The KDE project has addressed some recent concerns from users that they are forcing the systemd init system on current or future versions of its Plasma desktop environment. This comes after the developers of the KaOS Linux independent distro announced that they decided to replace the KDE Plasma desktop environment with a Niri/Noctalia setup to move away from systemd, saying that “Plasma pretty much demands systemd, and will be fully mandatory soon.“ Well, when asked if Plasma or any of its components demands systemd or if it is forced on users, the KDE project said no, except for the new Plasma Login Manager display manager that will be introduced with the upcoming KDE Plasma 6.6 release tomorrow. “So you are forcing Plasma users to use systemd?” No, the Plasma Login Manager is one of probably half a dozen login managers (or more) that can boot Plasma,” said the KDE devs. “We made PLM because it will give distro creators a cool piece of kit that can (not “must”, not “should”: can) be tacked onto a system to boot into Plasma.” The KDE project also said that they are not planning on making any of Plasma’s core components dependent on systemd, and that it will also continue to work on non-Linux systems like FreeBSD, as there were many recent reports on various news outlets that “KDE will drop support for non-systemd systems.” So there you have it, only the Plasma Login Manager will be dependent on systemd, but future Plasma desktop releases aren’t dependent on Plasma Login Manager, nor systemd. Therefore, Linux distros that want to ship the latest Plasma releases will have to use a different login manager, such as SDDM.' -- source: https://9to5linux.com/kde-says-plasma-desktop-will-never-force-users-to-use-... Cheers, Peter