Adam Borowski wrote: > Michael Biebl wrote: > > non-sense. > > Per the policy, severity for "breaks unrelated software" is > "critical". Thus, this bug is valid.
If you think that systemd is breaking anything on your system please open a bug against systemd package not policykit. > Please explain to me why a wrapper that executes, among others, > "pm-suspend" or "halt", would be related to an init system? > Especially if those commands (which in turn _could_ be related!) work > just fine without it. Because policykit needs to track user session, that ConsoleKit is dead for years, that logind is coming for free with the new selected init system and because it's time IMVHO to start moving away from ConsoleKit on linux architectures. > If you can't fathom a reason why systemd might not work for someone, > please re-read some of massive flamewars we had, I'm not going to > repeat the arguments here. As for policykit, though, basic > functionality like being able to shutdown from xfce, is something not > related to systemd in any way. If you are looking carefully at the dependencies, policykit is depending against libpam-systemd (because you need to have a logind session for the things to work) which in turn depends against "systemd-sysv | systemd-shim". If you don't like the systemd as PID1 just install systemd-shim and your init of choice, everything should work as before. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
