Bug#844785: systemd prevents polkit from working properly

2016-11-19 Thread Adam Bolte
On 20/11/16 15:13, Raphaël Halimi wrote: > Control: retitle -1 systemd-shim not fully compatible with systemd > 232 Control: affects -1 policykit-1 policykit-1-gnome mate-polkit > > Le 20/11/2016 à 04:21, Adam Bolte a écrit : Right. I retitled the bug > to more precisely describe the problem, and

Bug#844785: systemd prevents polkit from working properly

2016-11-19 Thread Raphaël Halimi
Control: retitle -1 systemd-shim not fully compatible with systemd 232 Control: affects -1 policykit-1 policykit-1-gnome mate-polkit Le 20/11/2016 à 04:21, Adam Bolte a écrit : > It took about an hour to find this bug report, since I was looking for > changes related to consolekit, polkit, pam,

Bug#844785: systemd prevents polkit from working properly

2016-11-19 Thread Adam Bolte
It took about an hour to find this bug report, since I was looking for changes related to consolekit, polkit, pam, etc. I've been using using sysvinit-core to avoid systemd issues (systemd doesn't even boot for me for some reason I don't care to investigate), so it didn't immediately occur to me

Bug#844785: systemd prevents polkit from working properly

2016-11-19 Thread Felipe Sateler
Control: reassign -1 systemd-shim 10-2 On 19 November 2016 at 00:18, Raphaël Halimi wrote: > Package: systemd > Version: 232-1 > > Since systemd 232, lightdm's menu entries to > shutdown/reboot/suspend/hibernate the system are grayed out. > > Furthermore, GNOME polkit

Bug#844785: systemd prevents polkit from working properly

2016-11-18 Thread Raphaël Halimi
Sorry, I forgot to mention that I use sysv init. Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature

Bug#844785: systemd prevents polkit from working properly

2016-11-18 Thread Raphaël Halimi
Package: systemd Version: 232-1 Since systemd 232, lightdm's menu entries to shutdown/reboot/suspend/hibernate the system are grayed out. Furthermore, GNOME polkit authentication agent fails to start (I use openbox, with the agent normally started from ~/.config/openbox/autostart). When