On 1/17/18, Irrwahn <[email protected]> wrote: > * screen sessions killed on logout > (regression, works with elogind disabled!)
This is because elogind is designed to be logind replacement (and actually shares its code) and so it's bug-for-bug compatible. Systemd uses cgroups to track processes and on logout kills all user's processes started during the session. > * urban@vboxascii:~$ loginctl reboot > AUTHENTICATING FOR org.freedesktop.login1.reboot This is incorrect behaviour. Required privileges should be granted automatically due to pam module, could you show your /etc/pam.d/session-common? Oh, wait... > Connection to 192.168.2.167 closed by remote host. Remote connection, so this explains the previous message. Can you repeat the same but with a local login? > 3. No consolekit/policykit, only elogind installed and activated > (not sure if that even makes any sense, but what the heck): ... Works as expected. _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
