Able to login again by doing this via live usb boot
mv /etc/pam.d/system-login /etc/pam.d/system-login.broken mv /etc/pam.d/system-login.pacnew /etc/pam.d/system-login
You´re a life saver...thnx !
]]>We can't have the .pacnew files automatically overwrite the old files (or do a swap like @deadfrominside did), since this would actually cause more unusable systems than the current solution (/etc/shadow.pacnew would be one example). Merging these files also requires some human intervention since the merges are often non-trivial and require human-like understanding.
Maybe pacnew resolver tools should be hard-dep'd by packagekit and automatically invoked if the installation occurs via packagekit? It would reduce the number of times this happens, but I can imagine such a move ruffling a few feathers. I wonder what ubuntu/debian do with packages that perform a dpkg-reconfigure?
]]>Any upgarde/update should be thinked to not break the system "by default"
You either ask the user if he wants so, either you make a special flag to trigger that behaviour, but in any case you never brake the authentification system by a simple usual update
I don't know if many people was affected but the fact is here
]]>[2020-08-19T22:48:36+0530] [ALPM] warning: /etc/pam.d/system-login installed as /etc/pam.d/system-login.pacnew
[2020-08-19T22:48:36+0530] [ALPM] upgraded pambase (20190105.1-2 -> 20200721.1-2)
[2020-08-19T22:48:36+0530] [ALPM] upgraded pam (1.3.1-2 -> 1.4.0-3)
Able to login again by doing this via live usb boot
mv /etc/pam.d/system-login /etc/pam.d/system-login.broken
mv /etc/pam.d/system-login.pacnew /etc/pam.d/system-login
With this replacement it works
If someone with the problem is courageous enough to make a bug report for this to be corrected in the next release...
]]>Also if you intend to use code tags do so with [ code ] [ /code ] without spaces instead of backticks
]]>Hi,
I was on my session, I did an upgrade, I rebooted, and now I can't login to my user or my root
The keyboard seems to work fine considering that everything typed in `localhost login:` seems fine
I tried to login remotely from SSH and it works, for the same users and same passwords
Do you have any ideas?
```
kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
systemd-udevd[276]: controlC1: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
login[390]: PAM unable to dlopen(/usr/lib/security/pam_tally2.so): /usr/lib/security/pam_tally2.so: cannot open shared object file: No such file or directory
login[390]: PAM adding faulty module: /usr/lib/security/pam_tally2.so
login[390]: PAM unable to dlopen(/usr/lib/security/pam_cgfs.so): /usr/lib/security/pam_cgfs.so: cannot open shared object file: No such file or directory
login[390]: PAM adding faulty module: /usr/lib/security/pam_cgfs.sologin[387]: pam_systemd_home(login:auth): Failed to query user record: Unit dbus-org.freedesktop.home1.service not found.
```
sudo pacman -S pam