MX Linux Forum

Shame that most major DE's have made systemd a hard dependency but that's a topic for another thread.


That's a GNOMEism. KDE, LXQt, Xfce, and MATE all don't require systemd and aren't planning on making it a requirement.


It may not be a requirement but Deb13 is going with systemd ...

DeepDayze wrote: Wed Aug 13, 2025 2:09 pm Shame that most major DE's have made systemd a hard dependency but that's a topic for another thread.

That's a GNOMEism. KDE, LXQt, Xfce, and MATE all don't require systemd and aren't planning on making it a requirement.

Is the way systemd-shim worked literally impossible to get working with cgroups v2 or would it require more effort than the maintainer was willing to put in? I'm guessing the former but I just want to know for sure.

Consider that KDE is still available in the various BSDs which are completely incompatible with systemd, including a recently introduced FreeBSD install media with KDE.

Imagine that, BSD might be the savior or they might give up on KDE..... probably the latter inevitably.


Wayland is ...

Thanks anyway.

I wonder how Slackware users will cope. KDE's been default for some time and Slackware's been opposed to systemd from the very start of the affair. Then again, Patrick is quite a wizard so he may find a work around.


@LU344928 I booted up AlienBob's latest Slackware15 -current ...

The death of systemd-shim and the broken state of Docker on Arch Linux ARM share the same cause: cgroups v1 is no longer enabled on the kernel starting with version 6.12. It's a shame too because MX was basically unique in the ability to switch init systems on-the-fly.

I finally got it. It needed a Startup WM Class added to it.

I was saying that this exact .desktop file which I have used on multiple desktops (including GNOME) is the only one that can't be pinned to my taskbar.

No. Still cog. I have put the icon in there.

There is only one correct answer on when to install security updates: once they're available for your system.