Woody wrote: > I see also a broken behaviour. I am doing a dual boot - with and > without systemd. > Till the libpolkit-backend has been linked against systemd, it has > worked just fine. > > The problem is now that backend is trying to blindly use systemd, and > fails if systemd is not running as init. With that change the user > authentication for network-manager or pcmanfm mounting are broken - > there is just a pcmanfm msgbox "Not Authorized". > > So *libpolkit-backend should first try to verify if systemd is an > init program, and if not - do not try to use it for authentication* - > it will definitely fail - so there is no point doing so. > > I understand that running without systemd is not a typical Debian > installation, but dependence on systemd should not be a mandatory for > Debian breaking everything either.
The only thing that policykit expects is a registered logind session (you can use loginctl command to check if it exists), not systemd as PID1. Moreover, network-manager also using logind for session tracking since 0.9.8.8-1. > It is an important bug. Could you please check if you have a logind session registered. Also which DM are you using to login? Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
