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

[dkg]

In the default import process, i don't think i ended up needing to enter
any passwords at all.  I can understand why you might need to enter
passwords when importing secret keys that weren't already in your
keyring, in general, but it seems like if being able to import them
cleanly (without password entry) works in one case, it ought to be able
to work in the other too.

anyway, i'd like to help, but without any way to reproduce this
behavior, i'm sort of stuck :(

-- 
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