Please create a separate ticket for "The initial language in kleopatra is not selected according to windows settings". This is a bug in KDE Frameworks that's orthogonal to the issues of this ticket.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mon, Nov 24
Best test this with a newer installer than gpg4win-5.0.0-beta413 to avoid the regression with the raw HTML (see T7886#208675).
The problem with the raw HTML has been fixed already by Tobias.
Yes, sorry, a typo, I corrected it.
In T7759#208677, @timegrid wrote:Forgot to note: Setting S/MIME debug level in kleopatra via GnuPG System will write the right key to gpg.conf (if I understood it right, this was also a problem)
Nov 21 2025
I also tried to check all tables i can find and it mostly looks good:
- Certificates Lists:
- Main
- Import ("Show imported")
- Cert Selection (e.g. Sign as)
- Keyserver Lookup
- Smartcard
- Groups (both available and in group)
- Certificate Details
- User IDs
- Sub-keys
- Certifications
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Actually pinentry has the same behaviour, so this might be a general problem, if one form input field is changed.
It also applies to clicking on other form elements.
Looks good to me on gpg4win-5.0.0-beta413 @ win11:
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Looks good to me on gpg4win-5.0.0-beta413 @ win11.
Looks good to me on gpg4win-5.0.0-beta413 @ win11:
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Looks good to me on gpg4win-5.0.0-beta413 @ win11: The option is removed in the S/MIME tab.
Note: Backup/Restore secret kyber keys looks good to me on gpg4win-5.0.0-beta413 @ win11 now.
Looks good to me on gpg4win-5.0.0-beta413 @ win11.
The error message in debugview is gone.
Looks good to me on gpg4win-5.0.0-beta413 @ win11:
Tested on gpg4win-5.0.0-beta413 @ win11
Looks good to me on gpg4win-5.0.0-beta413 @ win11.
Looks good to me on gpg4win-5.0.0-beta413 @ win11:
Looks good to me on gpg4win-5.0.0-beta413 @ win11.
Forgot to note: Setting S/MIME debug level in kleopatra via GnuPG System will write the right key to gpgsm.conf (if I understood it right, this was also a problem)
On gpg4win-5.0.0-beta413 @ win11
- The diagnostics button is displayed
- The message contains a hint to adsk
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Still needs to be tested on VSD 3.4.
Looks good to me on gpg4win-5.0.0-beta413 @ win11
Looks good to me on gpg4win-5.0.0-beta413 @ win11
I think last time I didn't test the actual problem.
Nov 20 2025
The tool tip for the menu is missing.
And after the "Save at" dialog we here get a "Secrete Team key was saved to $PATH/$filename" notification window. The one for secret key backup has no location info and for public keys we have no message at all.
We should have consistent behavior when saving secret (and public) keys, imho.
This has been changed:
- A progress/busy indicator page is now shown while smartcards are loaded (unless there are already smartcards shown; in this case the update happens "in the background"). Screen readers speak the progress message.
- The texts on the placeholder page (that is shown if no smartcards were found) are now accessible (if AT is active), i.e. one can reach them with Tab and initially the first text has keyboard focus (so that it's spoken).
- When a smartcard is found then the first smartcard tab has keyboard focus.
Nov 19 2025
In T7886#208534, @werner wrote:FWIW, GnuPG uses this Windows API
[...]
but can be overridden with the LC_ALL, LC_MESSAGES, or LANG envvars by setting them to the usual xx_XX value.
GPG output seems to depend on Regional Format.
Nov 18 2025
This is fixed.
Nov 17 2025
The error dialog now has a button to show the audit log (named Diagnostics).
The error dialog now has a button to show the audit log (named Diagnostics).
works with Gpg4win-5.0.0-beta395, too
as far as i can tell (and remember), I haven't implemented Ingo's suggestions. I'm putting the ticket back in the backlog and on my TODO list
Nov 14 2025
@werner sees no reason to define a new status error for everything in gpg. So let's stick with this Kleopatra ticket and adding the "Audit Log"/"Diagnostics" button.
Yes, we now plan to add an "Show Audit Log" Button (or is it "Diagnostics" in this case?). But we are not sure if this is enough.
Nov 13 2025
it is probably not worth the effort to backport this
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.
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)



