http://bugzilla.suse.com/show_bug.cgi?id=1040289 http://bugzilla.suse.com/show_bug.cgi?id=1040289#c2 Petr Cervinka <pcervinka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pcervinka@suse.com --- Comment #2 from Petr Cervinka <pcervinka@suse.com> --- I confirm exactly the same behavior on Tumbleweed, gpg fails with "No secret key" error. So far, I tested rollback to previous TW snapshot, gpg works fine with previous version. I also did a test with backup(used by gpg2-2.0.24-8.1) of ".gnupg" folder. Latest gpg proceeds with migration, but fails again. gpg: starting migration from earlier GnuPG versions gpg: porting secret keys from '/home/petr/.gnupg/secring.gpg' to gpg-agent gpg: key E1F7622DF4882DD0: secret key imported gpg: migration succeeded gpg: encrypted with 2048-bit RSA key, ID 0BA102312BA1C30C, created 2017-05-03 "Petr Cervinka <pcervinka@suse.com>" gpg: public key decryption failed: End of file gpg: decryption failed: No secret key It doesn't look related to key corruption in version 2.1.20. -- You are receiving this mail because: You are on the CC list for the bug.