Ubuntu
gnome-keyring package

  1. Bug #328127
  2. Comment #20

Comment 20 for bug 328127

Revision history for this message
David Thorne (cferthorney) wrote :

I too am having this issue having upgraded from Intrepid.

The SSH_AUTH_SOCK trick seems to work, as does generating a new key (Something I am loathed to do I have a number of current keys which are used in a number of places and I don't fancy regenerating them all) I am using the following version of Gnome-keyring:
sudo dpkg -l | grep gnome-keyring
ii gnome-keyring 2.26.1-0ubuntu1 GNOME keyring services (daemon and tools)
ii libgnome-keyring0 2.26.1-0ubuntu1 GNOME keyring services library
ii libgnome-keyring1.0-cil 1.0.0~svn.r87622-2 CLI library to access the GNOME Keyring daem
ii libpam-gnome-keyring 2.26.1-0ubuntu1 PAM module to unlock the GNOME keyring upon

and Seahorse:
sudo dpkg -l | grep seahorse
ii seahorse 2.26.1-0ubuntu1 A Gnome front end for GnuPG
ii seahorse-plugins 2.26.1-0ubuntu1 seahorse plugins and utilities for encryptio

Does the downgrade cause any issues with other packages (GnuPG etc)?