Today
it is probably not worth the effort to backport this
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.
@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.
Yesterday
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.
Tue, Nov 11
Removing VSD 3.4 tag. I don't intend to backport the changes in Qt 6 to Qt 5.
Panel Used By
| Dashboard | Mfcx's Dashboard |