Since the last Stable Update, I can’t login anymore.
However, I checked *.pacnew files with the following command:
sudo DIFFPROG=meld pacdiff
No files related to pam or pambase were prompted.
Since reboot, I can’t login anymore (only as root) and the service status is:
● user@1000.service - User Manager for UID 1000
Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
Active: failed (Result: exit-code) since Fri 2020-08-28 13:37:13 CEST; 9min ago
Docs: man:user@.service(5)
Process: 1002 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=224/PAM)
Main PID: 1002 (code=exited, status=224/PAM)
août 28 13:37:13 manjaro systemd[1]: Starting User Manager for UID 1000...
août 28 13:37:13 manjaro systemd[1002]: pam_systemd_home(systemd-user:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
août 28 13:37:13 manjaro systemd[1002]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[**********] ruser=[<unknown>] rhost=[>
août 28 13:37:13 manjaro systemd[1002]: pam_unix(systemd-user:session): session opened for user **********(uid=1000) by (uid=0)
août 28 13:37:13 manjaro systemd[1002]: PAM failed: Critical error - immediate abort
août 28 13:37:13 manjaro systemd[1002]: user@1000.service: Failed to set up PAM session: Operation not permitted
août 28 13:37:13 manjaro systemd[1002]: user@1000.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
août 28 13:37:13 manjaro systemd[1]: user@1000.service: Main process exited, code=exited, status=224/PAM
août 28 13:37:13 manjaro systemd[1]: user@1000.service: Failed with result 'exit-code'.
août 28 13:37:13 manjaro systemd[1]: Failed to start User Manager for UID 1000.
I am at a loss; if the /etc/pam.d/system-login file doesn’t containg lines related to pam_tally, pam-tally2, and pam_cracklib then I’m sorry to say that don’t know what the issue is.
Just an idea - you didn’t happen to overwrite your sudoers file with sudoers.pacnew by any chance, did you?
I updated as well, but no problems with login and I didn’t received /etc/pam.d/system-login.pacnew.
Yeah: is the same for me, and as I’ve said, no issues occurred: all is fine.
However I am puzzled about the fact that, as indicated in the announcement discussion, we have should expected system-login.pacnew.
You would only get the pacnew file if your system-login file had been modified from the original; if there had been no modifications made, then instead of a pacnew file, the old file simply gets overwritten with the new one. That’s what happened with you - your system-login file had never been modified…
I had no problems (nor system-login.pacnew files) on any of my systems, and I have quite a few.