From ArchWiki

Use With GNOME

I'm running GDM and Gnome and running into issues with getting gnome keyring to offer to save and automatically unlock ssh keys. Currently the article seems to indicate that this would just work, but that is certainly not the case. Could anyone elaborate on how to get this to work? Is it expected that users still add the keyring daemon launcher routine to their rc files in order to enable keyring support for ssh key passwords as mentioned in ? --Bret (talk) 05:18, 24 September 2015 (UTC)


"and make them available to applications." ... how do you use it?(firefox?) What applications are supported? the gnome page unclear as usual...Jasper1984 (talk) 11:39, 25 August 2012 (UTC) Edit: modification made to add it. Jasper1984 (talk) 11:50, 25 August 2012 (UTC)

place of default keyring

I could not find any documentation on where the keyring-file really is. Turns out that its directory is


greatest secret of them all. Also, if you have gnome-keyring , install seahorse GUI so you keep an overview of it gnome-keyring content. --UBF6 (talk) 02:20, 21 February 2018 (UTC)

Using the keyring outside GNOME with a a display manager (SDDM) =

From the article it seems that the keyring (no matter how it is called) is automatically unlocked by SDDM if the password matches the login password. Also it seems that it is not necessary to modify /etc/pam.d/sddm. Is this correct? This seems not to happen with sddm 0.17.0. Is this a bug? —This unsigned comment is by Simgunz (talk) 08:23, 2 July 2018‎ (UTC). Please sign your posts with ~~~~!

xinitrc method does not work

The method described for .xinitrc does not unlock the keyring. A comment on This reddit post suggests the PAM method must be used in conjunction for it to work, but this wiki proposes the PAM method as standalone. quequotion (talk) 06:13, 10 October 2019 (UTC)

Is the --start step still necessary with the dbus service installed by the package?

The --start step section of the wiki mentions:

> If you are not using GNOME, Unity, Mate, or Cinnamon as your desktop environment, initialisation will not complete automatically. You can fix this using various methods:

However, the arch gnome-keyring package installs a dbus service at `usr/share/dbus-1/services/org.gnome.keyring.service` which runs the daemon's --start process. Is this --step requirement out of date? --Yonson (talk) 18:36, 23 July 2021 (UTC)

Yes, I think the start step is outdated. If you start the daemon from your .zshenv, you will get the message "discover_other_daemon: 1". I will update the page to mention the systemd service as the recommended way.
TheStroyer (talk) 09:22, 22 June 2022 (UTC)

Launching gnome-keyring-daemon outside desktop environments (KDE, GNOME, XFCE, ...)

Emptty login manager doesn't execute scripts in /etc/X11/xinit/xinitrc.d/ automatically. Also, user sway configuration doesn't automatically include /etc/sway/config.d/50-systemd-user.conf. It's better to know what's going on under the hood so that people remember dbus-update-activation-environment and why they need it instead of 50-systemd-user.conf.

Amano 2022-08-03