Werner is going to add the missing implementation so that the error will soon be gone.

Note: We would need to handle possibly diverse error cases. A network share could be configured e.g. to not allow deletion for the user so that the temporary file can not be deleted.

In D618#6745, @TobiasFella wrote:

@ikloecker would there be any ABI problems with adding the new virtual function here?

@ikloecker would there be any ABI problems with adding the new virtual function here?

What about adding a "show gnupg log" button as we have in other dialogs?

I am currently working on backup/restore of Kyber keys. The error message will go away.

Conclusion: gpg needs to emit a more useful status error. -> subticket

gpgme logs:

2025-11-13 11:22:26 gpgme[28014.6de1]   _gpgme_io_read: check: [GNUPG:] KEY_NOT_CREATED <LF>
2025-11-13 11:22:26 gpgme[28014.6de1]   _gpgme_io_read: check: [GNUPG:] FAILURE gpg-exit 33554433<LF>

where 33554433 means (GPG_ERR_SOURCE_GPG, GPG_ERR_GENERAL) = (GnuPG, General error)

For Kleopatra we need to add an "Audit log" button to the error dialog. And we need to check if gpg is giving us a useful error that we (gpgme) are ignoring or if gpg doesn't throw a useful error. What do the gpgme logs say?

Backported for VSD 3.4.

Fixed (as far as possible).

meanwhile it looks like this in Kleopatra, it has now the blue sign but the issue is still the same:

what do we want here? "No public key" would be better that "General error" but then we would still have the same issue as here: T7886: Kleopatra: Enhance error on missing subkey, if set by default-new-key-adsk.

This needs to be fixed in Kleopatra because we create our own config dialog using a generic page dialog.

The second problem with the wrong tab order is also fixed.

I checked the code under gnupg/dirmngr. Those are no harm.

Removing VSD 3.4 tag. I don't intend to backport the changes in Qt 6 to Qt 5.

In T7588#207022, @timegrid wrote:

• unselected radio/checkboxes are a bit hard to see and worse to distinguish

In T7588#207022, @timegrid wrote:

• calendar (weekend days: general/selected/hover on dark background)

There are a lot of other ways to confuse the user. We can't fix them all because the whole purpose of a cleartext signature is to make it easy to use in legacy environments like an BBS. Modern systems use MIME to handle this in a more stringent specified way. For any use it is stongly suggested to check the actual signed data which is avaialable with the --output options. At least a sanitizing viewer should be used which filters out all escape characters (something like cat -v |less).

We have seen wrong encodings quite often in the past and thus we won't apply the patch. After all the armor header is a different layer and could also be applied or removed by other software or tools. The integrity of an OpenPGP message does not depend on its concrete outer encoding.

For someone who considers the rejection is the requirement of the spec., here is a change:

Here is a revised patch (hopefully the last one):