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

[Timo Aaltonen]

:: tjaalton at wilson:~/.gnupg> ls -al
total 1092
drwx------  3 tjaalton tjaalton   4096 huhti  8 18:21 .
drwxr-xr-x 42 tjaalton tjaalton   4096 huhti  8 18:25 ..
-rw-------  1 tjaalton tjaalton   8081 maali 20  2015 gpg.conf
-rw-rw-r--  1 tjaalton tjaalton      0 huhti  8 00:09 .gpg-v21-migrated
drw-------  2 tjaalton tjaalton   4096 maali 20  2015 private-keys-v1.d
-rw-------  1 tjaalton tjaalton   1669 maali 20  2015 public.key
-rw-------  1 tjaalton tjaalton 517605 maali 20  2015 pubring.gpg
-rw-------  1 tjaalton tjaalton    600 maali 17 22:44 random_seed
-rw-------  1 tjaalton tjaalton   7322 maali 20  2015 secring.gpg
srwxrwxr-x  1 tjaalton tjaalton      0 huhti  8 00:37 S.gpg-agent
-rw-------  1 tjaalton tjaalton   4520 maali 20  2015 trustdb.gpg

don't see anything wrong there

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

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