Arch Linux

DrZhivago

Member

Registered: 2016-07-17

Posts: 8

Adding pam_gnome_keyring.so to login PAM causes login/unlock to fail

Hi all, I'm on a fresh install of Arch running Sway without a display manager like SSDM or GDM. I set up my /etc/pam.d/login PAM config like the Arch Wiki suggests (note I'm using Ansible to manage my dotfiles):

#%PAM-1.0
# Updated by Ansible - 2022-08-22T22:27:11.626296

auth       required pam_securetty.so
auth       requisite pam_nologin.so
auth       include system-local-login
auth       optional pam_gnome_keyring.so
account    include system-local-login
session    include system-local-login
session    optional pam_gnome_keyring.so auto_start

This worked for a time, but for some reason this setup randomly fails, and when it does I'm locked out of my system, unable to unlock Swaylock or even log back in. My only way into the system is to mount the drive in a live CD and comment out the two lines I added with pam_gnome_keyring.so.

I have one keyring called Login set to my password and set as default. Deleting the keyring and starting again worked for a time but the problem has recently come back.

~ % ls ~/.local/share/keyrings
login.keyring  user.keystore

Does anyone have any ideas? I can post a link to my Ansible-managed dotfiles if it would help.

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,491

Re: Adding pam_gnome_keyring.so to login PAM causes login/unlock to fail

I'd look out for pamand gnome-keyring errors in the system journal.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

DrZhivago

Member

Registered: 2016-07-17

Posts: 8

Re: Adding pam_gnome_keyring.so to login PAM causes login/unlock to fail

Thanks for this idea, I ended up looking through my journal, and noticed a similar error message in this thread: https://bbs.archlinux.org/viewtopic.php?id=254871

The solution ended up being a combination of:
1. Disabling my user gnome-settings-daemon service file that I had created
2. Deleting my ~/.local/share/keyrings folder
3. Restarting, logging in, verifying that ~/.local/share/keyrings had been recreated, and finally re-enabling my gnome-settings-daemon service.