You are not logged in.
For some reason, when I log in, I am now prompted for my password and then immediately prompted for the password again (I don't use a login manager, so this is just at command line after boot). There is no error message, it just asks for the password again. If I enter my password the second time everything works normally. If I enter my password correctly the first time and then just hit enter the second time, it logs me in, but I get error messages about not being able to switch to home. I use systemd-homed with luks, and I think that what is happening is that the second password is being used to decrypt my home directory and if I don't enter it, I can log in but home is not accessible. But I can't figure out why it suddenly asks for my password twice when up until now, entering it once logged me in and decrypted home through systemd-homed.
I do see that systemd was updated right before this happened (I haven't tried downgrading because I'm not sure what other related packages I would need to downgrade if I downgraded systemd). Anyone else have this problem or have suggestions for figuring out what's going on?
Last edited by slamhound (2021-12-13 20:15:13)
Offline
Well, I updated again today, and for whatever reason, the problem has resolved. So I'll mark this as solved.
Offline
I actually just encountered this issue as well. On top of requiring my password twice before logging in, I now need to unlock my gnome-keyring when I reach the desktop. This occurred after updating today.
EDIT: What would I need to check to see what the potential issue is?
Last edited by Foreman (2021-12-16 03:04:50)
Offline
I went through journalctl and found this:
Dec 15 19:12:16 rosicrucian sudo[1645]: PAM unable to dlopen(/usr/lib/security/pam_unit.so): /usr/lib/security/pam_unit.so: cannot open shared object file: No such file or directory
Dec 15 19:12:16 rosicrucian sudo[1645]: PAM adding faulty module: /usr/lib/security/pam_unit.so
Dec 15 19:12:16 rosicrucian systemd-homed[577]: user: changing state active → authenticating-for-acquire
Dec 15 19:12:16 rosicrucian systemd-homework[1646]: None of the supplied plaintext passwords unlock the user record's hashed passwords.
Dec 15 19:12:16 rosicrucian systemd-homed[577]: Authentication failed: Required key not available
Dec 15 19:12:16 rosicrucian systemd-homed[577]: user: changing state authenticating-for-acquire → active
Dec 15 19:12:19 rosicrucian systemd-homed[577]: user: changing state active → authenticating-for-acquire
Dec 15 19:12:19 rosicrucian systemd-homework[1647]: Provided password unlocks user record.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Discovered used LUKS device /dev/mapper/home-user, and validated password.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Successfully re-activated LUKS device.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Provided password unlocks user record.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Discovered used loopback device /dev/loop0.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Read embedded .identity file.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Provided password unlocks user record.
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Reconciling user identities completed (host and header version were identical).
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Reconciling embedded user identity completed (host and embedded version were identical).
Dec 15 19:12:20 rosicrucian systemd-homework[1647]: Everything completed.
Dec 15 19:12:20 rosicrucian systemd-homed[577]: user: changing state authenticating-for-acquire → active
Dec 15 19:12:20 rosicrucian sudo[1645]: pam_systemd_home(sudo:auth): Home for user user successfully acquired.Any idea if the missing PAM modules at the top could be the issue, and if so, how to fix it?
Last edited by Foreman (2021-12-16 03:18:05)
Offline
I actually figured out what my problem was, and it had to do with a failed validity fingerprint scanner setup. I had added the following two lines to my /etc/pam.d/system-local-login file:
auth sufficient pam_unix.so try_first_pass likeauth nullok
auth sufficient pam_fprintd.soThis was suggested to be added by the wiki: https://wiki.archlinux.org/title/Fprint
I hadn't gotten it to work (thinkpad fingerprint drivers are finnicky), and so I uninstalled the requisite driver packages immediately prior to running a pacman -Syu. I thought it was the upgrade, but it was actually the removal of the drivers and lack of fprint package that screwed up my login. It didn't appear when screenlocking or logging out/in, only on bootup dude to systemd-homed locking the /home partition and requiring a decryption. After removing the two lines above and rebooting the double password issue disappeared, and my keyring is unlocked by default upon login.
Last edited by Foreman (2021-12-17 01:17:40)
Offline