| 1 |
On Mon, 2017-05-22 at 13:02 +0300, Alexander Kapshuk wrote: |
| 2 |
> On Mon, May 22, 2017 at 1:00 PM, Raffaele Belardi |
| 3 |
> <raffaele.belardi@××.com> wrote: |
| 4 |
> > On Mon, 2017-05-22 at 12:47 +0300, Alexander Kapshuk wrote: |
| 5 |
> > > |
| 6 |
> > > A Google search found this systemd issue: |
| 7 |
> > > https://github.com/systemd/systemd/issues/4342 |
| 8 |
> > > Quote: |
| 9 |
> > > @poettering I see I left no account modules in the bare-bones PAM |
| 10 |
> > > config. Maybe it is pam_acct_mgmt failing then? |
| 11 |
> > > |
| 12 |
> > > @yuwata what happens if you add account required pam_unix.so ? |
| 13 |
> > > |
| 14 |
> > > @fsateler Thanks. By adding the line, user sessions successfully |
| 15 |
> > > start |
| 16 |
> > > without the error messages. Do you think the line should be added |
| 17 |
> > > to |
| 18 |
> > > the minimal PAM file? |
| 19 |
> > > |
| 20 |
> > > See if that helps. |
| 21 |
> > > |
| 22 |
> > |
| 23 |
> > Yes, I saw that but the solution is not at all clear to me: which |
| 24 |
> > PAM |
| 25 |
> > config file are they referring to? |
| 26 |
> > |
| 27 |
> > raffaele |
| 28 |
> > |
| 29 |
> > |
| 30 |
> |
| 31 |
> Could it be this one, /etc/pam.d/systemd-user? |
| 32 |
> |
| 33 |
|
| 34 |
Done then issued 'systemctl daemon-reload' and 'systemctl start gdm', |
| 35 |
no change: |
| 36 |
|
| 37 |
$ cat /etc/pam.d/systemd-user |
| 38 |
# This file is part of systemd. |
| 39 |
# |
| 40 |
# Used by systemd --user instances. |
| 41 |
|
| 42 |
account include system-auth |
| 43 |
# [RB] |
| 44 |
account required pam_unix.so |
| 45 |
session include system-auth |
| 46 |
session optional pam_keyinit.so force revoke |
| 47 |
session optional pam_systemd.so |
| 48 |
|
| 49 |
#journalctl -b |
| 50 |
... |
| 51 |
systemd[1]: Created slice User Slice of gdm. |
| 52 |
systemd[1]: Starting User Manager for UID 32... |
| 53 |
systemd[1]: Started Session c519 of user gdm. |
| 54 |
systemd-logind[173]: New session c519 of user gdm. |
| 55 |
systemd[15240]: user@××.service: Failed at step PAM spawning |
| 56 |
/usr/lib/systemd/systemd: Operation not permitted |
| 57 |
systemd[1]: Failed to start User Manager for UID 32. |
| 58 |
systemd[1]: user@××.service: Unit entered failed state. |
| 59 |
systemd[1]: user@××.service: Failed with result 'protocol'. |
| 60 |
gdm-launch-environment][15237]: pam_systemd(gdm-launch- |
| 61 |
environment:session): Failed to create session: Start job for unit user |
| 62 |
@32.service failed with 'failed' |
| 63 |
systemd-logind[173]: Removed session c519. |
Archives