Here’s something that’s both surprising and, in a way, not surprising at all, especially after yesterday’s announcement from KaOS, a distribution long known for its deep commitment to the KDE Plasma desktop, that it plans to move away from it. The main reason cited was KDE’s reliance on systemd in a specific component.
As expected, the news quickly gained traction, prompting KDE to clarify its dependence on systemd and which parts of the desktop environment rely on it. In a post on KDE’s Reddit community titled “A quick anti-FUD FAQ to debunk ‘the KDE is forcing systemd!’ hoax“, the contributor described the claims as misinformation and provided a short FAQ clarifying the project’s position.
I still wonder if the systemd imposition on the new login manager is absolute and can’t be circumvented in any way, i.e. GNOME is allegedly dependent on systemd but you can circumvent it by using logind instead of the full systemd install
That’s because someone took the time to pull out the minimum required interface code from systemd to make elogind after gnome made such a mess of things. It’s a band-aid. More band-aids will no doubt be created to deal with this. It’s just that the necessity is annoying.