I found that to use a workaround to restart gnome-keyring-daemon from command line in a way to reuse the existing socket: the env var GNOME_KEYRING_TEST_PATH. This var should be set to the /tmp/keyring- XXXXXXXX that was previously in use.
For example: GNOME_KEYRING_TEST_PATH=/tmp/keyring-pw7JIX/ gnome-keyring-daemon ** Message: another SSH agent is running at: /tmp/keyring-pw7JIX/ssh GNOME_KEYRING_SOCKET=/tmp/keyring-pw7JIX//socket SSH_AUTH_SOCK=/tmp/keyring-pw7JIX//ssh GNOME_KEYRING_PID=24788 When I next try to use a ssh key, it asks to authenticate again (should it?), and it caches the keyphrase again. -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
