Starting with systemd-194, pam_systemd prints following error: Oct 05 08:47:57 xxx sudo[6850]: pam_systemd(sudo:session): Asking logind to create session: uid=1000 pid=6850 service=sudo type=tty class=user seat=seat0 vtnr=7 tty=/dev/ Oct 05 08:47:57 xxx sudo[6850]: pam_systemd(sudo:session): Failed to create session: Invalid argument Although command "sudo" still works, "su" fails with similar error: Oct 05 08:41:51 xxx su[8140]: pam_systemd(su:session): Asking logind to create session: uid=1000 pid=8140 service=su type=tty class=user seat=seat0 vtnr=7 tty=/dev/pts/8 Oct 05 08:41:51 xxx su[8140]: pam_systemd(su:session): Failed to create session: Invalid argument Oct 05 08:41:51 xxx su[8140]: pam_open_session: Cannot make/remove an entry for the specified session Reverting to systemd-193 solves this problem.
I see this on my system as well. Reverting the following commit fixes the issue. commit a8573ccc35a4efe8900be5d48c6c803670540c2b Author: Lennart Poettering <lennart@poettering.net> Date: Mon Oct 1 14:50:00 2012 -0400 pam: check environ[] for XDG_SEAT as fallback This is useful for systems such as kmscon which want to invoke classic /sbin/login but use it on multiple seats.
This issue still presented in systemd-195. For my understanding: is it expected behaviour, or this bug should be fixed?
Fixed in git since a few days ago.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.