You are not logged in.
Pages: 1
Topic closed
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.so
login[387]: pam_systemd_home(login:auth): Failed to query user record: Unit dbus-org.freedesktop.home1.service not found.
```
Last edited by vf (2020-08-20 11:19:47)
Offline
I have the same issue, tried from both X and tty with correct credentials
Offline
I would try
sudo pacman -S pam
Offline
remains exactly the same
Offline
https://bbs.archlinux.org/viewtopic.php?id=258313
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.
```
Offline
```
pacman -Qkk pam
pam: 551 total files, 0 altered files
```
Offline
Then you either created files yourself or a package still uses these modules in which case you should make a relevant bugreport, search for files using tally2 and cfg in /etc/security and remove the relevant lines/check which package they belong to with pacman -Qo and file relevant bug reports should they come from the repos.
Also if you intend to use code tags do so with [ code ] [ /code ] without spaces instead of backticks
Last edited by V1del (2020-08-20 11:06:28)
Online
Just had this issue myself. Try checking for /etc/pam.d/system-login.pacnew. If it exists, replace your current /etc/pam.d/system-login and reboot.
Offline
```
diff /etc/pam.d/system-login.pacnew /etc/pam.d/system-login
2a3
> auth required pam_tally2.so onerr=succeed file=/var/log/tallylog
6a8
> account required pam_tally2.so
19c21,22
< session required pam_env.so user_readenv=1
---
> session required pam_env.so
> session optional pam_cgfs.so -c freezer,memory,name=systemd,unified
```
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...
Last edited by vf (2020-08-20 11:19:19)
Offline
That's normal system maintenance, so no need for a bug report, but the package you should've pacman -Qkk'd was pambase. And this is the reason you need to read your pacman output as it will have mentioned the creation of this file.
Last edited by V1del (2020-08-20 11:22:19)
Online
```
pacman -Qkk pambase
backup file: pambase: /etc/pam.d/system-login (Modification time mismatch)
pambase: 8 total files, 0 altered files
```
Offline
Found this in /var/log/pacman.log:
[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
Offline
Same
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
Last edited by vf (2020-08-20 11:41:58)
Offline
If anything, this is a bit indicative of an incomplete packagekit backend for e.g. KDE Discover, Gnome Software Centre. The messages about .pacnew files don't show up in the message view when using graphical update tools, and so it's very easy to update and then not realise there's been a critical config file update.
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?
Offline
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 !
Arch...the way it was meant to be !!
Offline
Search about ^@ and input polldev and Linux 4.13 for more information
Last edited by vf (2020-11-22 09:46:19)
Offline
Closing this solved thread.
Offline
Pages: 1
Topic closed