-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
PAM: [email protected]: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted #4342
Copy link
Copy link
Closed
Labels
Description
Submission type
- Bug report
- Request for enhancement (RFE)
NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!
systemd version the issue has been seen with
I guess that from baed1fe. The git snapshot ec72b96 has the issue, and 084f580 does not.
NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!
Used distribution
fedora 24 x86_64
In case of bug report: Expected behaviour you didn't see
The error message below is not shown.
In case of bug report: Unexpected behaviour you saw
The following error message is shown.
$ journalctl -b (snip) lightdm[666]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) systemd[1]: Created slice User Slice of lightdm. systemd[1]: Starting User Manager for UID 988... systemd-logind[505]: New session c1 of user lightdm. systemd[1]: Started Session c1 of user lightdm. systemd[669]: [email protected]: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted systemd[1]: Started User Manager for UID 988. (snip) systemd[1]: Starting User Manager for UID 1000... systemd[718]: [email protected]: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted systemd-logind[505]: New session 1 of user watanabe. systemd[1]: Started User Manager for UID 1000. systemd[1]: Started Session 1 of user watanabe. lightdm[711]: pam_unix(lightdm:session): session opened for user watanabe by (uid=0) (snip)Note that if we use the previous pam.d/systemd-user, called fedora-specific one, then the above error message is not shown.
In case of bug report: Steps to reproduce the problem
boot the system and login.
Reactions are currently unavailable