desktop-packages team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

I use gpg key on a Yubikey Neo and this works correctly in Trusty,
Utopic and Vivid.

Make sure that in startup applications "GPG Password Agent, GNOME Keyring: GPG Agent" is unchecked.
Clear custom changes to bashrc.
Logout, login.

Check that gpg-agent upstart user session job is running (In terminal, $
status gpg-agent)

Check environment is pointing at gpg agent, rather than anything else
(e.g. gnome-keyring etc) ( $ env | grep gpg )

** Changed in: gnome-keyring (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1387747

Title:
  No longer asks for passphrase, no access to private key

Status in gnome-keyring package in Ubuntu:
  Incomplete

Bug description:
  I'm using Thunderbird with Enigmail on Trusty in KDE. I've set
  /usr/bin/gpg (i.e., GPG 1, not GPG 2) as GPG path in Enigmail. My GPG
  key is stored on a YubiKey Neo.

  This has worked fine until yesterday. Yesterday, after the following
  update:

  gnome-keyring:amd64 3.10.1-1ubuntu4 -> 3.10.1-1ubuntu4.1

  … Thunderbird/Enigmail no longer asks me for me passphrase when I open
  an encrypted e-mail or when I try to sign an e-mail. Instead, I
  directly see the error message "no private key available".

  A downgrade to 3.10.1-1ubuntu4 and a reboot solves the problem.
  Updating again to 3.10.1-1ubuntu4.1 makes the problem appear again.

  There also have been a kernel update and an update of libykpers. Those
  do nott seem to have caused the problem: Downgrading them (or booting
  the older kernel) does not solve the problem. Only the downgrade of
  gnome-keyring solves it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387747/+subscriptions