OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat medium very-common DISPUTE

Chromium and Electron apps ask to unlock the keyring on every launch, or lose all saved passwords

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

Real, very common problem, and the Chromium half is impeccable, but the PAM half sends an Omarchy reader to the wrong file on a wrong premise, and the verify command does not work. (a) The fix says "If you log in through a display manager (SDDM, GDM, LightDM, LXDM) this is already configured" (a faithful copy of ArchWiki GNOME/Keyring) and then walks the reader through /etc/pam.d/login. On Omarchy 4 both halves are wrong. Omarchy ships SDDM (sddm is in /usr/share/omarchy/install/omarchy-base.packages and /etc/sddm.conf.d/ is populated), so /etc/pam.d/login is never consulted, and Arch's sddm PAM stack is only half-configured for gnome-keyring. I read /etc/pam.d/sddm on this box: it has -session optional pam_gnome_keyring.so auto_start but **no auth optional pam_gnome_keyring.so** line, and grep -n gnome_keyring /etc/pam.d/* shows nothing else in the include chain (system-login/system-auth are clean). Without the auth half PAM never captures the login password, so the login keyring is started but never unlocked, which is precisely this record's symptom. The record therefore tells the majority of its audience "already configured, skip this" when it is the actual cause. (b) SDDM autologin, which Omarchy supports (/etc/sddm.conf.d/autologin.conf), has both PAM lines in /etc/pam.d/sddm-autologin but no password is ever typed, so the keyring still cannot be unlocked: a second real case the record does not cover. (c) The verify command pgrep -a gnome-keyring-daemon does not work: the name is 20 characters and pgrep refuses patterns over 15 ("pattern that searches for process name longer than 15 characters will result in zero matches"). It needs pgrep -af. (d) Step 2's hand-start is obsolete and mildly harmful: current gnome-keyring (1:50.0-1) ships gnome-keyring-daemon.socket, enabled by preset and active here, plus /etc/xdg/autostart/gnome-keyring-secrets.desktop which uwsm runs. ArchWiki warns a second start produces "discover_other_daemon: 1". Omarchy's own /usr/share/omarchy/default/hypr/autostart.lua already runs dbus-update-activation-environment --systemd --all. (e) Step 2 also names the wrong file for Omarchy: user autostart lives in ~/.config/hypr/autostart.lua, which hyprland.lua requires. What is correct and stays: the ArchWiki /etc/pam.d/login block and the /etc/pam.d/passwd append are verbatim-accurate. --password-store=gnome-libsecret is a real, currently documented value (ArchWiki Chromium "Force a password store" lists gnome-libsecret, kwallet5, kwallet6, basic, detect) and the Failed to decrypt token for service AccountId-* symptom is quoted verbatim from that same page. ArchWiki Electron documents --password-store for safeStorage. The danger about --password-store=basic writing plaintext into Login Data matches the wiki exactly. gnome-keyring, libsecret and seahorse are all in official repos. busctl --user list | grep secrets works (shows org.freedesktop.secrets owned by gnome-keyring-d).

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

Changing the password store makes everything encrypted under the previous backend permanently unreadable. You are logged out of every site and all saved passwords in that profile are lost. Export what you need first. --password-store=basic is a last resort: it writes the cookie encryption key and passwords as plain text into the profile's Login Data file, readable by anything running as your user. Editing PAM files incorrectly can lock you out of login entirely. Keep a root shell open on another TTY (Ctrl+Alt+F2) while you edit, and test in a second TTY before closing it. Deleting ~/.local/share/keyrings/login.keyring permanently destroys every stored secret.

Symptom

Every time I start Chromium, Slack, Signal or Element a dialog appears asking "Enter password to unlock your login keyring". If I dismiss it, all my saved logins and sessions are gone. Starting the app from a terminal prints Failed to decrypt token for service AccountId-*.

Cause

Chromium (and every Electron app, which uses the same safeStorage/Secret Service code) auto-detects which password store to use. With no desktop environment it guesses, and the guess changes as packages come and go, so the key that encrypted your cookies with one backend cannot be read back with another. Separately, on a bare Hyprland session gnome-keyring is often never unlocked: pam_gnome_keyring.so is not in the PAM stack, or gnome-keyring-daemon --login started by PAM died because it was never handed the session D-Bus environment, so the daemon has no unlocked login keyring to serve.

Fix

**1. Find out which PAM stack your login actually uses. Check it, do not assume it is fine.**


systemctl status display-manager --no-pager | head -3
grep -n gnome_keyring /etc/pam.d/*

Omarchy 4 logs in through **SDDM**, so /etc/pam.d/login is never read. And Arch's sddm package ships only half of what gnome-keyring needs: /etc/pam.d/sddm has


-session    optional    pam_gnome_keyring.so    auto_start

but **no auth line**, so PAM never captures your login password and the login keyring comes up locked. That is the usual reason for a prompt on every launch on Omarchy, and it is why "a display manager configures this for you" is not true here.

Before editing any PAM file, **open a root shell on another TTY (Ctrl+Alt+F2) and leave it open**. A broken PAM stack locks you out of login entirely. Add the missing line after auth include system-login:


# /etc/pam.d/sddm
auth        include     system-login
-auth       optional    pam_gnome_keyring.so

Log out and back in, and confirm on the second TTY that you can still authenticate before you close it.

For a console login with no display manager, the file is /etc/pam.d/login and the ArchWiki block is:


#%PAM-1.0
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

greetd users edit /etc/pam.d/greetd instead.

**If you use SDDM autologin** (/etc/sddm.conf.d/autologin.conf), no password is ever typed, so PAM has nothing to unlock the keyring with and the missing auth line above will not help. Either accept one prompt per boot, or give the **Login** keyring an empty password in seahorse, which stores every secret in it **unencrypted on disk, readable by anything running as your user.** Do not do that on a machine anyone else can reach.

**2. Packages.** gnome-keyring and libsecret are already in Omarchy's base set, but seahorse is not:


sudo pacman -S --needed gnome-keyring libsecret seahorse

**3. Do not hand-start the daemon. Check it instead.** Current gnome-keyring ships gnome-keyring-daemon.socket (enabled by preset) and /etc/xdg/autostart/gnome-keyring-secrets.desktop, which uwsm runs. Adding another gnome-keyring-daemon --start gives you discover_other_daemon: 1.


systemctl --user status gnome-keyring-daemon.socket
busctl --user list | grep org.freedesktop.secrets

The D-Bus activation environment is already handled on Omarchy by /usr/share/omarchy/default/hypr/autostart.lua. Only on a bare Hyprland session with no uwsm and no display manager do you need to add it yourself, and the user-owned file is ~/.config/hypr/autostart.lua, not hyprland.lua:


-- ~/.config/hypr/autostart.lua
hl.on("hyprland.start", function()
  hl.exec_cmd("dbus-update-activation-environment --systemd --all")
end)

**4. Stop Chromium guessing which store to use.** Pin the backend explicitly:


# ~/.config/chromium-flags.conf
--password-store=gnome-libsecret

# ~/.config/electron-flags.conf
--password-store=gnome-libsecret

For an app bundling its own Electron (these files are read only by Arch's electron package), patch its desktop entry:


cp /usr/share/applications/slack.desktop ~/.local/share/applications/
sed -i 's|^Exec=\(.*slack\) |Exec=\1 --password-store=gnome-libsecret |' ~/.local/share/applications/slack.desktop
update-desktop-database ~/.local/share/applications

**5. If the keyring password no longer matches your login password**, change it in seahorse: right-click the **Login** keyring → Change Password → set it to your user password. To make it track your password automatically in future, append to /etc/pam.d/passwd:


password	optional	pam_gnome_keyring.so

**6. Log out completely and back in**. PAM only runs at login. Then verify (note the -f, because the process name is 20 characters and plain pgrep -a refuses to match names longer than 15):


pgrep -af gnome-keyring-daemon
busctl --user list | grep org.freedesktop.secrets

Verify

pgrep -a gnome-keyring-daemon shows the daemon running with --components= including secrets. busctl --user list | grep secrets shows org.freedesktop.secrets. Launch Chromium: no prompt appears and previously saved passwords are listed under chrome://settings/passwords. seahorse shows the **Login** keyring as unlocked.

Sources

chromium-electron-keyring-password-prompt-every-launch