banned_9-26-2021 This is maybe above my head, but I was under the impression that elogind was bad because it was just a piece of systemd isolated to do what it is supposed to do. I read something along the lines of it being better to have than alternatives when you are not using systemd. Obarun doesn't need elogind, but what is in place of elogind? consolekit2?
eric yep, consolekit2. Instead of continuing develope consolekit , the dev of main soft was prefered to switch to system:D. if all the efforts we made to fork elogind had been put to the development of consolekit2, we would have a much more effective software. Instead, consolekit today has only one main develloppeur. This is also the fault of all distro continuing to use piece of system:D like elogind instead of switching to the real alternative like consolekit. More people use a things, more people want use the things and more it's developed... Another reason to be a warrior...
banned_9-26-2021 I read somewhere that part of the choice is because they can run wayland with elogind, while it doesn't work with consolekit. Since wayland is pushed by freedesktop I suspect the choice is not so innocent, especially in distros that chose to go the other way (away from the sysDgangsters).
ray Here are thoughts on ConsoleKit2 of its developer Eric Koegel: https://erickoegel.wordpress.com/2014/10/20/consolekit2/ Especially curious this link mentioned: https://mail.gnome.org/archives/distributor-list/2012-January/msg00008.html