A multi-line Secret Service value destroys Omarchy's passwordless default keyring, and autologin can never unlock what replaces it
Gate 1 holds: issue #11159 (duckzooka, 2026-09-10, with three independent reproductions), gnome-keyring issues 103 (2022) and 147 (2024) and ProtonVPN/python-proton-keyring-linux issue 5 (2026-08-26) all predate this repository, and the cleartext default is written by a shipped script. Gate 2 mostly held, with two defects in the cause. The record says sddm.sh strips pam_gnome_keyring from /etc/pam.d/sddm because autologin never gives PAM a password, but the script's own comment gives a different reason, preventing a password login from creating an encrypted login keyring, and it deletes only the -auth and -password lines: /etc/pam.d/sddm on this machine still has the -session auto_start line, and /etc/pam.d/sddm-autologin, the service an autologin session actually uses, is not edited at all and still carries the -auth line, which is the source of the gkr-pam messages quoted in the issue. The write-without-escaping claim was checked against gnome-keyring's gkm-secret-textual.c, where the secret is written with g_key_file_set_value and read with g_key_file_get_string, so it is confirmed from code rather than only from a comment. The fix was the real problem. Its cp backup is a one-shot snapshot that goes stale the moment any client stores a secret, the record never says how to use it, and restoring it over a live daemon would be the wrong move anyway, so it neither prevents the corruption nor recovers from it. The corrected fix gives the Proton override, checked against python-proton-core's loader (it reads PROTON_LOADER_OVERRIDES, and the json entry point exists in that package's setup.py), and a recovery that does what PR #11697 does: move the unparseable and password-protected files aside, rewrite the stub from default-keyring.sh, repoint default, then log out. That recipe was not exercised on this machine or a VM, which is why confidence is medium. It cannot destroy stored secrets because nothing is deleted, and danger now says plainly that it does not put them back either. Confirmed on 4.0.2-1: default-keyring.sh and sddm.sh are byte-identical to the pinned blobs, /usr/bin/omarchy-keyring-repair does not exist and is not in current quattro, PR #11697 is open and unmerged as of 2026-09-18, and the default pointer file is a bare name. The existing record keyring-reset-after-update-logins-cleared covers the same end state by a different mechanism, and its repoint-only recipe cannot work here, which the fix now says. Gate 3 holds. Severity lowered from medium to low. The record's mechanism is an integrity failure with no attacker: nobody reaches a credential, crosses a privilege boundary or runs code. The only security default in it, secrets stored in cleartext at rest, is readable only by the user's own account or by whoever already holds the disk, which is the brief's low level, a weakness needing an already compromised local account, and on the default LUKS install the disk is encrypted. The operator may prefer apps-services for this record. The harvester's quoted dialog text drops the source's punctuation but the words match the issue. Re-checked against 4.0.4-1 2026-09-19: Re-checked against 4.0.4-1 on 2026-09-19. install/user/default-keyring.sh and install/login/sddm.sh are byte-identical between the pinned 75cb4f7 blobs, the v4.0.4 tag (c668141e9c42b13c80c9ca4ea108e11708c5e8a5) and the installed copies under /usr/share/omarchy/install (omarchy 4.0.4-1), and neither has a quattro commit after 75cb4f7. On this machine /etc/pam.d/sddm still has only the -session ... auto_start gnome-keyring line and /etc/pam.d/sddm-autologin (owned by sddm 0.21.0-7) still has the -auth and -session lines. /usr/bin/omarchy-keyring-repair does not exist and no such file is in the v4.0.4 tree. None of the 145 files in the v4.0.2...v4.0.4 compare touches the keyring or PAM. The one migration mentioning a keyring, 1787589206.sh, is the pacman packaging key and unrelated. Issue #11159, PR #11697 and PR #10396 are all open. The issue's newest comment, 2026-09-16, reproduces the fault on gnome-keyring 1:50.0. Package side: gnome-keyring 1:50.0-1 and libsecret 0.21.7-1 are installed, both since 2026-08-22, and neither moved with the Omarchy upgrade. Arch extra still ships gnome-keyring 1:50.0-1. libsecret is 0.21.8.2-1 in Arch core, but it is the client library and the fault is in the daemon's file writer. Upstream gnome-keyring is unfixed: gkm-secret-textual.c was last changed in 2014, the 50.0 to 51.1 compare does not touch it, issues 103 and 147 are open, and merge request 111 (opened 2026-08-25 by a third party) is the open fix, so the cause gains one sentence saying so and the source. Text changes are the version and date in cause and fix, the open PR #10396 in cause, and the upstream status. omarchy logout still resolves on 4.0.4-1 through the alias in /usr/bin/omarchy-system-logout. Confidence stays medium because the recovery recipe has still not been exercised on this machine or a VM. The keyring was not read or changed.
Do not delete ~/.local/share/keyrings/ or any file in it to clear the prompt. Every secret it holds, including ones unrelated to whatever broke the file, is gone with it. The recovery above moves files aside for the same reason. It does not put the secrets back: every application has to be signed into again, and anything an application encrypted with a key it kept in the keyring, such as Chromium's saved passwords and cookies under Chromium Safe Storage, is unreadable to it after the reset unless that one item is restored by hand from the moved-aside file. Typing a password into the unlock dialog does not fix anything either: it opens the password-protected replacement for one session, and autologin cannot open it at the next boot, so the prompt returns. Do not answer it by adding an auth pam_gnome_keyring.so line to a PAM file: an autologin session goes through /etc/pam.d/sddm-autologin, which still has that line and no password to give it.
Symptom
After autologin, an "Authentication required, An application wants access to the keyring Default Keyring, but it is locked" prompt starts appearing on every boot, for no configuration change you made. Chrome, Chromium, VS Code, Slack, gh, or other Secret Service clients may also stop finding credentials they had before.
Cause
Omarchy's default keyring is cleartext by design: install/user/default-keyring.sh writes ~/.local/share/keyrings/Default_keyring.keyring with a [keyring] header and no password, and writes the default pointer file naming it. install/login/sddm.sh deletes the -auth and -password pam_gnome_keyring.so lines from /etc/pam.d/sddm so that a password login cannot create an encrypted login keyring that competes with the passwordless one. The -session ... auto_start line stays, and /etc/pam.d/sddm-autologin, the service an autologin session actually goes through, is not edited at all and still carries the -auth line, which is why the journal shows gkr-pam: no password is available for user on every boot. Both scripts are unchanged from 4.0.2-1 through 4.0.4-1, and PR #10396, which applies the same edit to /etc/pam.d/sddm-autologin, is open and unmerged as of 2026-09-19.
The cleartext format is a GLib key file. In gnome-keyring's pkcs11/secret-store/gkm-secret-textual.c a secret is written with g_key_file_set_value(), which does no escaping, and read back with g_key_file_get_string(), which unescapes. A Secret Service client that stores a value containing a raw newline, reported on the issue for Ente Auth through flutter_secure_storage_linux and for Proton VPN's SSO session item, which embeds PEM certificates, therefore writes physical line breaks into the secret= line. The daemon keeps serving the value from memory for the rest of that session, then rejects the whole file at the next start with keyring was in an invalid or unrecognized format. Every other secret in the file goes with it: Chromium's Chromium Safe Storage key, gh, Slack, VS Code and Proton were all reported lost this way. With no loadable default keyring, the next client to ask for a secret triggers gnome-keyring's create-a-keyring prompt, the keyring it creates is password-protected, default is repointed at it, and from then on autologin gives PAM nothing to unlock it with, so the locked-keyring prompt returns on every boot. A newline in a secret is legal in the Secret Service API and the password-protected format stores bytes opaquely, so the fault is specific to the cleartext format chosen for autologin, and any client can trigger it. The daemon side is unfixed upstream: gkm-secret-textual.c has not changed since 2014, gnome-keyring 1:50.0-1 is what Arch and Omarchy 4.0.4 install, the 51.0 and 51.1 releases leave that file alone, and merge request 111, which writes the value with g_key_file_set_string() so GLib escapes the newline, is open.
Fix
There is no shipped repair as of 4.0.4-1: /usr/bin/omarchy-keyring-repair does not exist, and PR #11697, which adds it as an early user unit that moves a corrupt or password-protected default aside and rewrites the cleartext stub, is open and unmerged as of 2026-09-19. Two things you can do now.
**Keep an application that writes multi-line values out of gnome-keyring, where it lets you.** python-proton-core's loader reads PROTON_LOADER_OVERRIDES, and keyring=json selects its own JSON-file backend under ~/.config/Proton/, so Proton VPN never touches the keyring. environment.d is read by the user manager at login, so log out and in afterwards:
mkdir -p ~/.config/environment.d
echo 'PROTON_LOADER_OVERRIDES=keyring=json' > ~/.config/environment.d/proton-vpn.conf
Ente Auth has no equivalent switch, so this closes the hole only for clients that have one.
**Recover once the prompt has appeared.** Do it the way PR #11697 does, by moving files aside rather than deleting anything. See what is there and which keyring default names now:
ls -la ~/.local/share/keyrings/
cat ~/.local/share/keyrings/default
Move the replacement keyring and the unparseable cleartext one aside, write a fresh stub identical to what install/user/default-keyring.sh writes, and point default back at it:
cd ~/.local/share/keyrings
stamp=$(date +%Y%m%d%H%M%S)
cur=$(tr -d '[:space:]' < default)
[[ $cur != Default_keyring && -f $cur.keyring ]] && mv -- "$cur.keyring" "$cur.keyring.broken-$stamp"
[[ -f Default_keyring.keyring ]] && mv -- Default_keyring.keyring "Default_keyring.keyring.broken-$stamp"
cat > Default_keyring.keyring <<EOF
[keyring]
display-name=Default keyring
ctime=$(date +%s)
mtime=0
lock-on-idle=false
lock-after=false
EOF
printf 'Default_keyring\n' > default
chmod 700 . && chmod 600 Default_keyring.keyring && chmod 644 default
Then log out straight away with omarchy logout, without starting another application, because the running daemon still holds the old keyring in memory and can write it back. After the next login the empty cleartext keyring is the default and the prompt is gone. Sign in again to each application that had a secret. The moved-aside cleartext file still holds its values on secret= lines and can be read for re-entry. The issue describes a lossless alternative, folding each stray continuation line back into its secret= line as a literal \n, which is what g_key_file_get_string() expects, but no shipped script does it as of 4.0.4-1.
The repoint-only recipe in keyring-reset-after-update-logins-cleared does not work here: Default_keyring.keyring itself is unparseable, so pointing default back at it reproduces the rejection.
Verify
After the next login, confirm the daemon loaded the cleartext keyring and the pointer is back on it:
cat ~/.local/share/keyrings/default
head -1 ~/.local/share/keyrings/Default_keyring.keyring
journalctl -b -g 'invalid or unrecognized format'
The first prints Default_keyring, the second [keyring], and the third prints nothing for this boot. For Proton VPN, confirm the override reached the session:
systemctl --user show-environment | grep PROTON_LOADER_OVERRIDES
Sources
- https://github.com/omacom/omarchy/issues/11159
- https://github.com/omacom/omarchy/pull/11697
- https://github.com/omacom/omarchy/blob/75cb4f7195cfc064d05cd30623b3254c9541ba3c/install/user/default-keyring.sh
- https://github.com/omacom/omarchy/blob/75cb4f7195cfc064d05cd30623b3254c9541ba3c/install/login/sddm.sh
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/blob/165f0e3210e32538c847be91896736c17a1f6ad6/pkcs11/secret-store/gkm-secret-textual.c
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/103
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/147
- https://github.com/ProtonVPN/python-proton-keyring-linux/issues/5
- https://github.com/ProtonVPN/python-proton-core/blob/53202abdc1a64587884110192e02c31c2c8de04e/proton/loader/loader.py
- https://github.com/omacom/omarchy/pull/10396
- https://gitlab.gnome.org/GNOME/gnome-keyring/-/merge_requests/111