Hey, I'm quite sure, that this is not the issue of Kmail, as Kmail is using the GPGME to talk to gpg. So it will be an issue of libqgpgme7. But first make sue, that you are really have an valid bug. Please verify the signature in a konsole via gpg --verify. I expect, that it will fail with the same error. Keep in mind that Joot's using a subkey to sign ( 0x54F1A66317486713), this subkey needs to be available also to verify the signature. > When doing "gpg --list-keys 0x57930DAB0B86B067" (or long key ID) > (with "list-options show-keyring=yes" in my gpg.conf) I see the same key > present in my keyring (pubring.kbx) and in Debian's debian-keyring.gpg. As I was told you alsoways have to use --with-colons when using gpg --list-keys --with-colons to get ideas about the key status. > I have no clue how this can happen or be explained, > but it sounds like a bug to me. So far I know gnupg does want to get rid of multiple keyrings statched together. So maybe you find one of the bugs with statching. But you may get more up-to-date news from gnupg mantainers in Debian. hefee
Attachment:
signature.asc
Description: This is a digitally signed message part.