Bug 55656

Summary:	systemd 194: pam_systemd "Failed to create session: Invalid argument"
Product:	systemd	Reporter:	Vlad <vovan>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	normal
Priority:	high	CC:	arne.staecker, j, thilo.wiesner
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Vlad 2012-10-05 08:54:27 UTC

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.

Comment 1 Jürg Billeter 2012-10-15 10:23:22 UTC

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.

Comment 2 Vlad 2012-10-27 06:09:17 UTC

This issue still presented in systemd-195. For my understanding: is it expected behaviour, or this bug should be fixed?

Comment 3 Lennart Poettering 2012-10-30 22:21:35 UTC

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.