GNOME Bugzilla – Bug 646492
Please create $GNOME_KEYRING_CONTROL directory in $XDG_RUNTIME_DIR rather than /tmp
Last modified: 2011-04-02 18:22:17 UTC
gnome-keyring creates a temporary directory for its control socket in /tmp. This temporary directory often doesn't get properly cleaned up, resulting in the accumulation of directories in /tmp. (Right now I have a pile of /tmp/keyring-* directories accumulated just in the past month since I last removed all of them. Other systems I've used have many screenfuls of these directories.) This directory seems like a perfect fit for /var/run. Moving the directory there should not affect any existing applications, since they all reference it via $GNOME_KEYRING_CONTROL. Furthermore, this would ensure that they get cleaned up at boot time, at a minimum (or automatically disappear when using a tmpfs for /var/run).
/var/run doesn’t have the appropriate permissions for that use. It is exactly why /tmp is here.
(In reply to comment #1) > /var/run doesn’t have the appropriate permissions for that use. It is exactly > why /tmp is here. /var/run could use mode 1777, and if it does the gnome-keyring can use it. gnome-keyring should fall back to /tmp if /var/run doesn't work.
A correction: this directory should move into $XDG_RUNTIME_DIR if set. That variable will point to a user-writable (and user-specific) directory; if unset, gnome-keyring can fall back to $TMPDIR or /tmp.
*** This bug has been marked as a duplicate of bug 646389 ***