Elogind v239.1 Devuan/Debian combined source

[Mark Hindley]

Peter,

Thanks for this.

On Sat, Nov 10, 2018 at 11:01:46PM +0000, Peter Maydell wrote:
> (12) test startx: works ok. the 'restart' menu option just stops the x
> session, but maybe that's intended

I think this might be related to polkit integration not working. See below.

> (13) apt install lightdm
> (14) reboot
> (15) lightdm still works as much as it did with my/iwj's earlier elogind
> packaging: login and the user session are fine, but the power off/reboot/etc
> menu entries at the login screen are all greyed out.

Installing polkit made those available for me, although they still only produce
a logout rather than reboot. But it is another step!

There is still something not right with the polkit/elogind pid to session
matching that I can't track down.

sid> pkaction --verbose --action-id org.freedesktop.login1.power-off
org.freedesktop.login1.power-off:
  description:       Power off the system
  message:           Authentication is required for powering off the system.
  vendor:            The systemd Project
  vendor_url:        http://www.freedesktop.org/wiki/Software/systemd
  icon:              
  implicit any:      auth_admin_keep
  implicit inactive: auth_admin_keep
  implicit active:   yes
  annotation:        org.freedesktop.policykit.imply -> org.freedesktop.login1.set-wall-message
sid> loginctl show-session $XDG_SESSION_ID -p Active
Active=yes

Which both seem OK. But then this fails

sid> pkcheck --action-id org.freedesktop.login1.power-off -u --process $$
polkit\56retains_authorization_after_challenge=1
Authorization requires authentication and -u wasn't passed.

polkit also keeps spitting out "can't find seesion for PID" errors. I have tried
version 155 from experimental as well, but that seems the same.

Does anybody have any suggestions?

> On reboot, I am getting a python exception and backtrace:
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner:
> Could not get owner of name 'org.freedesktop.login1': no such name
> (not clear what from, but it happens as/after lightdm shuts down).
> 
> Sorry about providing the error as a screenshot, but I can't
> cut-and-paste from virt-viewer and I'm not sure that sysvinit
> service shutdown messages get logged anywhere helpful; anyway,
> the full backtrace is here:
> http://www.chiark.greenend.org.uk/~pmaydell/misc/dbus-python-backtrace.png

I have not seen that. But I have been testing with xfce. I will install Mate and
see if I can reproduce.

Later: actually I can't. Certainly the logout/suspend menu items are enabled
for me but only produce a logout as above.

Many thanks for your report.

Mark