On Mon, 2017-05-22 at 13:02 +0300, Alexander Kapshuk wrote: > On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi > <raffaele.bela...@st.com> wrote: > > On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: > > > > > > A Google search found this systemd issue: > > > https://github.com/systemd/systemd/issues/4342 > > > Quote: > > > @poettering I see I left no account modules in the bare-bones PAM > > > config. Maybe it is pam_acct_mgmt failing then? > > > > > > @yuwata what happens if you add account required pam_unix.so ? > > > > > > @fsateler Thanks. By adding the line, user sessions successfully > > > start > > > without the error messages. Do you think the line should be added > > > to > > > the minimal PAM file? > > > > > > See if that helps. > > > > > > > Yes, I saw that but the solution is not at all clear to me: which > > PAM > > config file are they referring to? > > > > raffaele > > > > > > Could it be this one, /etc/pam.d/systemd-user? >
Done then issued 'systemctl daemon-reload' and 'systemctl start gdm', no change: $ cat /etc/pam.d/systemd-user # This file is part of systemd. # # Used by systemd --user instances. account include system-auth # [RB] account required pam_unix.so session include system-auth session optional pam_keyinit.so force revoke session optional pam_systemd.so #journalctl -b ... systemd[1]: Created slice User Slice of gdm. systemd[1]: Starting User Manager for UID 32... systemd[1]: Started Session c519 of user gdm. systemd-logind[173]: New session c519 of user gdm. systemd[15240]: user@32.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted systemd[1]: Failed to start User Manager for UID 32. systemd[1]: user@32.service: Unit entered failed state. systemd[1]: user@32.service: Failed with result 'protocol'. gdm-launch-environment][15237]: pam_systemd(gdm-launch- environment:session): Failed to create session: Start job for unit user @32.service failed with 'failed' systemd-logind[173]: Removed session c519.
