Manuel Bärenz

wxcore-0.92.3.0 doesn't build on Trusty with GHC 8.2.1

Hmm, good idea, but unfortunately didn't change anything. Not even when I exported (the secret key), deleted and then reimported it.

Yes, that works. For fun, I also tried it with --encrypt, and that says that the public key is missing! Which is strange, because this certainly is the fingerprint of the public subkey. And I've created the key with Enigmail. And gpg2 -k | grep AD59 spits out the key.

I have checked the structure of my new key, itself and all subkeys are valid until 2022.

Thanks! That maybe brought me a step forward. I checked again, no account has the old key. That's right, my gpg.conf wasn't up to date. I changed it to the new key now. Now the error message goes: KEY_CONSIDERED 2DEE9D239F065826DA5680E373989AFCD002AD59 2 KEY_CONSIDERED 2DEE9D239F065826DA5680E373989AFCD002AD59 0 INV_RECP 0 80E373989AFCD002AD59 FAILURE sign-encrypt 9 Note that this is now my valid new key. The other error messages persist unchanged.

I don't see how this bug is invalid. It still persists, please see my answer to Ludwig Hügelschäfer's comment. An additional error message I sometimes see is this one: INV_RECP 0 80E373989AFCD002AD59 FAILURE encrypt 9

Thanks! That maybe brought me a step forward. I checked again, no account has the old key. That's right, my gpg.conf wasn't up to date. I changed it to the new key. Now the error message goes: KEY_CONSIDERED 2DEE9D239F065826DA5680E373989AFCD002AD59 2 KEY_CONSIDERED 2DEE9D239F065826DA5680E373989AFCD002AD59 0 INV_RECP 0 80E373989AFCD002AD59 FAILURE sign-encrypt 9 Note that this is now my valid new key. The other error messages persist unchanged.

After creating new key, can't sign anymore