A quick anti-FUD FAQ to debunk "the KDE is forcing systemd!" hoax

Q: Does the Plasma Login Manager require systemd to work?

A: Yes.

Q: So you ARE forcing Plasma users to use systemd!!?!?!

A: No. The Plasma Login Manager is one of probably half a dozen Login Managers (or more) that can boot Plasma. 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.

Q: So I don’t have to use PLM?

A: No! You can completely ignore PLM! Please be our guest and use any of the other non-systemd dependent LMs that will work and continue to work just fine, now and in the future.

Q: Is KDE planning on making any of Plasma’s core components dependent on systemd?

A: No.

Q: So Plasma does not and will not require systemd to work now or in the future?

A: That is correct.

Q: And it will continue to work on non-Linux systems like FreeBSD?

A: Also correct.

Q: Why have I been hearing that KDE will force systemd down everybody’s throats via Plasma then?

A: There are sad people who will do anything for attention and clicks, and will spread FUD and fake controversies to obtain them, including decontextualising comments on merge requests, stating as facts and official communications what are personal opinions, and finally straight up lying.

Don’t believe the FUD.

11 Likes

I saw this: KaOS Linux Drops KDE Plasma After 12 Years for Niri/Noctalia to Escape systemd - 9to5Linux yesterday and just shook my head. :roll_eyes:

1 Like

Yeah, they swallowed the FUD hook, line and sinker. So sad.

3 Likes

I would even be surprised if plasma-login-manager really has a dependency on systemd.

It is just much more likely that requires that certain setup steps have been taken care of externally and that come D-Bus interfaces are available.

In such cases the most convenient or readily-available solution could be the systemd eco-system with other approaches becoming viable after additional testing.

For example many login managers use the D-Bus interface initially introduced by systemd-logind which has since then also been provided by elogind and other alternatives.

1 Like

>I would even be surprised if plasma-login-manager really has a dependency on systemd.

It does. Logind shims only get you so far, and that so far is on-par with the current state of Linux, but still disappointing.

There’s Drop sddm-helper (#20) · Issues · Plasma / Plasma Login Manager · GitLab

and http://github.com/systemd/systemd/pull/39855

which are coming soon, reducing PLM backend to very little.

The longer term plans is to move the abstraction layer slightly higher rather than in the backend and holding us back.

I had PLM-greeter running against greetd at some point, it’s trivial, probably in the history somewhere. My longer term plan is to push the frontend back up to plasma-workspace with the abstraction there.

3 Likes

You obviously know this in more detail than my cursory check could have determined :slight_smile:

I only found one sd_ API call in the Qt message handler and otherwise only D-Bus communication.

So it looked like all important systemd integration went through that and could be provided by alternative implementations.

Thanks for the links, should provide some nice insights!

1 Like