[Bug 1565963] Re: gpg secret keys not migrated after upgrade to gnupg 2.1

[dkg]

Mario pointed me to this bug, and i'm surprised that this happened.  I
also am not sure how to debug it because it's not something i've been
able to reproduce myself, and it sounds like once it's fixed for
someone, they have no incentive to go back and reproduce it themselves.

Can anyone provide a set of reproducible steps to make this happen?

For example, as a standard user, i can do:

 gpg --gen-key

and then the new key is visible via both "gpg --list-keys" and "gpg
--list-secret-keys"

if i then do:

 gpg2 --list-keys

i can also see the new key.  and if i do:

 gpg2 --list-secret-keys

then i see:

gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/home/testuser/.gnupg/secring.gpg' to gpg-agent
gpg: key 57B78432: secret key imported
gpg: migration succeeded

and subsequent attempts to use the gpg2 secret key work just fine.

do you have any keys on smartcards, any keys ancient or weirdly-
formatted keys, or any other unusual configuration that might have
triggered this problem?

without a way to reproduce the error, i'm kind of at a loss.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/1565963

Title:
  gpg secret keys not migrated after upgrade to gnupg 2.1

Status in gnupg2 package in Ubuntu:
  New

Bug description:
  After upgrading to gnupg 2.1 I can no longer see my keys in seahorse
  (Passwords and Keys in apps scope in unity) and evolution cannot find
  my gpg keys. Someone said this might be related to
  https://www.gnupg.org/faq/whats-new-in-2.1.html#autostart and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796931

  Reading the Debian bug I see someone mentioned that running this might help:
  $ gpg2 --import < ./.gnupg/secring.gpg

  I did that and gpg2 went through each of my private keys to import
  them. When done I logged out and back in and seahorse saw my keys. I'm
  not sure why gpg2 didn't prompt me before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1565963/+subscriptions