For what it is worth, his systemd is a bug. There is no way in which you can look at systemd and say that "it's a bug". It may be a system not engineered the w

For what it is worth, his systemd is a bug. There is no way in which you can look at systemd and say that "it's a bug". It may be a system not engineered the way you would prefer, but it absolutely isn't "a bug". It's a large, well engineered piece of software, that solves many pain points of traditional ways of managing services and sessions on Unix-like systems over the years. What way would you like to customize your system that you cannot using systemd? I'm genuinely curious if you've ever tried using it. Now, there are many valid reasons why systemd may not be to your taste. No one is forcing you to use it. There are projects in which development is moving to depend on systemd, because it provides a lot of functionality that other systems don't, and the people writing that code don't want to have to reinvent the wheel. Lots of software has dependencies, some of which you may not like, but you shouldn't blame Person A for making a system that you don't want to use, that Person B who writes software you do want to use depends on; and really, blaming Person B isn't particularly helpful either, as they are just trying to get the job done efficiently and don't have the time to maintain many different backends for many different incompatible session management systems.