techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.4K
active users

Trevor Burrows

Someday I'll take the time to solve this recurring keyring issue in , but every time I search for info, it quickly becomes one of those "I'll do this another day" things.

Happens whenever I open VSCodium or Chrome. I just cancel it (three or four times) and it disappears.

@NearerAndFarther is this happening in fedora 41?

@NearerAndFarther nuke the keyring.

Back up original (or with things like this I move it to /tmp/ since it deletes contents after a while.)
mkdir -p ~/.local/share/keyrings-backup mv ~/.local/share/keyrings/* ~/.local/share/keyrings-backup/

Then clean it out:

rm -f ~/.local/share/keyrings/*

Log out and back in.

When you next launch an app that tries to use the keyring (like Chromium, Evolution, etc.), it'll prompt you to create a new default keyring.

Use the same password as your login if you want it to unlock automatically at login.

If you use GNOME or any DE that uses gnome-keyring-daemon, and your login password doesn't match the old keyring password

@spohnz will give this a shot soon - thanks!

@spohnz Looks like this did the trick --- thanks for this. Bookmarking for the future in case it goes awry again!

@NearerAndFarther if you're running 42 or rawhide, might be gitlab.gnome.org/GNOME/gnome-k . otherwise, it really might just be that you changed your password or something. you can try what dallas suggested, or you can install seahorse and use that to change the password on the login keyring to match your user's password.

behind the scenes, when you log in, gnome immediately 'replays' the password you entered against your login keyring. if it doesn't work, you get this dialog.

gitlab.gnome.orgMaking sure you're not a bot!

@adamw will look at this soon - thanks for sharing