Arch Linux

doctordeity

Member

From: behind you

Registered: 2020-05-18

Posts: 12

[SOLVED] GNOME Keyring Not Logging in to Default Key on Boot

Howdy, y'all!

So I use Proton VPN and Proton Mail Bridge. Unfortunately every single time I boot, GNOME Keyring creates a new key, and I have to log in and set everything up again. Funnily enough, Seahorse shows me that these keys are saved, but even when I unlock them, these apps won't log into those, they only seem to want to create a new key and set that one as the default. I had to do a reinstall the other day (long story) and it's been happening since then. I tried:

- Not setting a password
- Reinstalling GNOME Keyring
- Reinstalling Proton VPN and Proton Mail Bridge
- Deleting all of the keys except the most recent one

I'm honestly a bit stumped. What else should I try?

Last edited by doctordeity (2026-05-22 22:29:44)

---

“Humans cannot create anything out of nothingness. Humans cannot accomplish anything without holding onto something. After all, humans are not gods.”
– Kaworu Nagisa

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,527

Re: [SOLVED] GNOME Keyring Not Logging in to Default Key on Boot

What starts gkr? Session script, autostart, user service?
Do you use systemd-homed or pam_mount or is your $HOME otherwise populated late?
Any gkr errors/warnings/messages in the journal?

---

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

doctordeity

Member

From: behind you

Registered: 2020-05-18

Posts: 12

Re: [SOLVED] GNOME Keyring Not Logging in to Default Key on Boot

Deleting the new key after it is created caused GKR to fall back on the previous key, which fixes the problem and maintains it across reboots! Marking as solved. :-)

---

“Humans cannot create anything out of nothingness. Humans cannot accomplish anything without holding onto something. After all, humans are not gods.”
– Kaworu Nagisa