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

Fix apps failing with "org.freedesktop.secrets was not provided by any .service files"

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

Cause and most of the fix are right, and the Omarchy-specific detail is verified precisely: install/login/sddm.sh really does sed -i '/-auth.*pam_gnome_keyring\.so/d' and the same for -password on /etc/pam.d/sddm, with a comment about the passwordless Default_keyring, and the /etc/pam.d/login block quoted for TTY logins matches the Hyprland wiki's own snippet. gnome-keyring ships usr/share/xdg-desktop-portal/portals/gnome-keyring.portal, so routing org.freedesktop.impl.portal.Secret=gnome-keyring in ~/.config/xdg-desktop-portal/hyprland-portals.conf is valid, and /usr/lib/git-core/git-credential-libsecret is genuinely shipped by Arch's git. The defect is the docker login section: it hands the reader "credsStore": "secretservice" while only vaguely saying to 'install a helper', and there is no docker-credential-secretservice in the official repos (I checked: it exists only in the AUR, alongside docker-credential-helpers and docker-credential-pass). Setting credsStore without that binary reproduces the exact error in the symptom. Also worth using the shipped gnome-keyring-daemon.service instead of only the hand-run daemon.

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

Never delete files under ~/.local/share/keyrings/ to "start clean": every stored secret is in those files and is unrecoverable without them. A passwordless keyring stores its contents unencrypted on disk. That is a deliberate Omarchy trade-off for autologin, but do not add a passwordless keyring to a machine where the disk is not encrypted. Adding pam_gnome_keyring.so to a PAM file with a typo can lock you out of logins. Edit it from a root shell you already have open.

Symptom

Anything that wants the system keyring fails. docker login prints:


Error saving credentials: error storing credentials - err: exit status 1, out: `The name org.freedesktop.secrets was not provided by any .service files`

Sometimes instead: Cannot autolaunch D-Bus without X11 $DISPLAY. git push over HTTPS re-asks for the password every time, secret-tool store --label=test foo bar hangs or errors, and Flatpak password managers cannot save anything.

Cause

org.freedesktop.secrets is provided by gnome-keyring-daemon's secrets component. On a bare Wayland compositor there is no desktop environment starting it with the right components, and the session D-Bus may not know about the graphical environment at all, so it cannot even show an unlock prompt. Flatpak apps additionally need the Secret *portal* routed to gnome-keyring, which is only wired up for GNOME by default.

Fix

Install the pieces and start the secrets component as documented (gnome-keyring libsecret seahorse, dbus-update-activation-environment --systemd --all, then gnome-keyring-daemon --start --components=secrets in your session startup, or simply systemctl --user enable --now gnome-keyring-daemon.service, which the package ships). Verify with busctl --user list | grep secrets and a secret-tool store / lookup round-trip. Git over HTTPS via /usr/lib/git-core/git-credential-libsecret is unchanged.

For **docker login**, the credential helper is not in the official repos, so install it from the AUR before setting credsStore, otherwise you get the same 'error storing credentials' failure:


yay -S docker-credential-secretservice   # or docker-credential-pass for a GPG/pass-backed store

{
  "credsStore": "secretservice"
}

Confirm the binary is on PATH first (command -v docker-credential-secretservice). If you would rather not install a helper at all, delete any credsStore line from ~/.docker/config.json and accept the base64 plain-file store.

The Flatpak Secret-portal routing, the Omarchy keyring inspection (ls -la ~/.local/share/keyrings/, cat ~/.local/share/keyrings/default) and the /etc/pam.d/login lines for TTY logins all stand as written.

Verify

busctl --user list | grep secrets shows org.freedesktop.secrets, secret-tool stores and looks up a value, and docker login / git push stop re-prompting. seahorse opens and lists the keyring.

Sources

secret-service-not-available-keyring