Martin Steigerwald - 25.02.26, 18:07:50 CET:
> Didier Kryn - 25.02.26, 18:06:01 CET:
> > > Forcing through Systemd would alienate people. That has been the
> > > outcome of forcing through Systemd quite some times. I hope some day
> > > people will learn.
> > >

> >      That was my conclusion: distros drop Systemd, but actually it is

> >
> > Systemd which drops them by forcing incompatible design. Apparently
> > Plasma is going the same way as Gnome in the dependency to Systemd.
> > I've read on Kaos' forum that Plasma si contemplating to drop BSD
> > support.
> Have an URL to that?

What I found is that they dropped BSD support from Plasma Login manager,
which I believe is a fork of SDDM:

Drop code for FreeBSD support

We rely on systemd/logind, so FreeBSD is not supported

https://invent.kde.org/plasma/plasma-login-manager/-/merge_requests/42

I did not know that a developer actively dropped that code, but make sense
as the SDDM that they forked from actually had this code.

It affects Plasma Login manager, not Plasma desktop session and SDDM can
still be used, but this is a concerning. Given there are other Systemd-
only features I hope that is not becoming a trend. Like it so often has in
the past. Bit by bit, step by step make lives of users on other-than-
Systemd environments more complicated. Then drop completely. I hope KDE
developer community will be wiser than going this route.

Apparently KDE promo is already doing some damage control:

KDE’s Default Login Manager Binds Itself To Systemd

"(Editor’s note: [Paul Brown] from KDE contacted us to reinforce that KDE
will continue to support the BSDs and smaller Linux flavors, but they’ll
just have to use a different login manager.)"

https://hackaday.com/2026/02/02/kde-binds-itself-tightly-to-systemd-drops-support-for-non-systemd-systems/

We will see.

Best,
--
Martin