OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core medium occasional DISPUTE

Recover logins after an update reset the keyring

omarchyarchhyprlandwayland
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The mechanism (gnome-keyring's default pointer file selecting the wrong keyring) is real, and 'do NOT delete anything' is good advice. But the key value is wrong for Omarchy. Verified in install/user/default-keyring.sh: Omarchy creates ~/.local/share/keyrings/Default_keyring.keyring and writes Default_keyring (with a trailing newline) into the default file. It is deliberately a passwordless keyring, and install/login/sddm.sh strips the pam_gnome_keyring lines from /etc/pam.d/sddm specifically to 'prevent password-based SDDM logins from creating an encrypted login keyring that conflicts with Omarchy's passwordless default keyring behavior'. So pointing default at login is exactly the keyring Omarchy avoids creating, and on most Omarchy machines no login keyring exists at all, so the fix would leave the user worse off. Also systemctl --user restart gnome-keyring-daemon.service is not how gnome-keyring runs here. The pkill fallback is the real path.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Never delete files in ~/.local/share/keyrings: the old secrets are unrecoverable without them. Always copy default aside before editing.

Symptom

After an omarchy update and reboot, all browser login sessions are gone, gh auth status says not logged in, and a dialog asks the user to *create a new keyring*. Looking in ~/.local/share/keyrings shows a freshly written default file and a new Default_Keyring_1.keyring next to the older keyring files.

Cause

gnome-keyring's default pointer file was rewritten during the update/session change, so the daemon created and selected a brand-new empty keyring instead of unlocking the existing one. The old secrets are still on disk. They're just no longer the default.

Fix

Do NOT delete anything. List what is actually there first:


ls -la ~/.local/share/keyrings/
cat ~/.local/share/keyrings/default

The default file contains a bare keyring name with no .keyring suffix. On Omarchy the correct value is **Default_keyring** (matching Default_keyring.keyring), not login. Omarchy deliberately uses a passwordless default keyring and strips pam_gnome_keyring from /etc/pam.d/sddm, so a login keyring usually does not exist on these systems.

Pick whichever keyring file actually holds your secrets (check sizes and dates in the listing above) and point default at its name minus the .keyring suffix:


cp ~/.local/share/keyrings/default ~/.local/share/keyrings/default.bak
printf 'Default_keyring\n' > ~/.local/share/keyrings/default

Upstream writes that value with a trailing newline, so keep the \n.

Restart the daemon, then log out and back in:


pkill -f gnome-keyring-daemon

Inspect and merge with Seahorse if the names are ambiguous:


sudo pacman -S --needed seahorse
seahorse

If the keyring files themselves are gone rather than just mis-pointed, recreate Omarchy's default:


bash /usr/share/omarchy/install/user/default-keyring.sh

Once the right keyring is default again, browser sessions and gh auth come back on next login. Re-authenticate anything still missing with gh auth login.

Verify

cat ~/.local/share/keyrings/default names your original keyring, secret-tool search --all service gh returns entries, and the browser no longer prompts to create a keyring.

Sources

keyring-reset-after-update-logins-cleared