https://bugzilla.novell.com/show_bug.cgi?id=803007 https://bugzilla.novell.com/show_bug.cgi?id=803007#c1 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby@suse.com AssignedTo|security-team@suse.de |fcrozat@suse.com --- Comment #1 from Jiri Slaby 2013-03-01 22:46:42 UTC --- I had the same issue. At least I think. My loginctl output was empty (no seats). I had to add pam_systemd to common-session: session required pam_limits.so session required pam_unix.so try_first_pass session required pam_systemd.so session optional pam_umask.so session optional pam_env.so Now everything works for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803007 https://bugzilla.novell.com/show_bug.cgi?id=803007#c3 --- Comment #3 from Jiri Slaby 2013-03-06 10:11:26 UTC --- (In reply to comment #2)

/etc/pam.d/common-session should be a symlink to /etc/pam.d/common-session-pc (ie the file will be under pam-config control and should get pam_systemd.so added automatically).

Is it the case ?

Nope, both were self-standing files. Now I fixed it so that common-* point to common-*-pc. And of course -pc contained pam_systemd.so. I have no idea how I come to that situation... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803007 https://bugzilla.novell.com/show_bug.cgi?id=803007#c5 --- Comment #5 from Thorsten Kukuk 2013-03-06 10:31:07 UTC --- Has nothing to do with RPM. Somebody played with pam-config or modified files and afterwards ignored the pam-config warnings that pam-config is now disabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803007 https://bugzilla.novell.com/show_bug.cgi?id=803007#c7 --- Comment #7 from Frederic Crozat 2013-03-06 10:42:26 UTC --- (In reply to comment #5)

Has nothing to do with RPM. Somebody played with pam-config or modified files and afterwards ignored the pam-config warnings that pam-config is now disabled.

Well, I'm 99% sure I already saw reports on IRC with similar issue where common-session was handled by pam-config and after upgrade (to Factory), it wasn't a symlink anymore. And it is not systemd, since systemd only relies on pam-config. It would be interesting to know if there was a common-session.rpmsave or common-session.rpmnew created.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803007 https://bugzilla.novell.com/show_bug.cgi?id=803007#c Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.