Additional “KDE only wants to work with systemd” evidence: Pipewire screen sharing breaks on nearly all non-systemd setups because they hardcode the assumption that Pipewire will be launched at a specific time after SDDM but before startplasma is called (but it still has to be launched as your user, not as root). So if you launch it using KDE's autostart mechanism screen sharing breaks, and you can't launch it from your system-wide service manager. Luckily my s6 setup w/ user services finally allows me to fix it by setting up the dependencies in order
@nytpu Slackware won't be happy. They ditched Gnome because of this shit.
@sullybiker Additional fact: the new System Monitor that replaced ksysguard in KDE 6 depends on systemd because for some reason it insists on using the systemd supervision tree (via cgroups) instead of just… reading the list of processes like every other system monitor program does?
@sullybiker Oh the System Monitor definitely is. This bug is seemingly unintentional according to the bug report, just happened because I guess none of their developers has a non-systemd test machine (and/or they didn't do a thorough enough test for them to try screen sharing) https://bugs.kde.org/show_bug.cgi?id=483137
@nytpu I believe that is absolutely intentional. It's too deliberate to be otherwise.