Looks good to me on gpg4win-5.0.0-beta413 @ win11:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Fri, Nov 21
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 gpg.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.
Thu, Nov 20
The tool tip for the menu is missing.
Please add the typical "Save at" dialog (instead of automatic saving with info "Key was saved at"). We should have consistent behavior when saving secret (and public) keys.
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.
Wed, Nov 19
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.
Tue, Nov 18
This is fixed.
Mon, Nov 17
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
Fri, Nov 14
@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.
Thu, Nov 13
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)
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.
Wed, Nov 12
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.
Tue, Nov 11
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)
Mon, Nov 10
Thu, Nov 6
The problem with Enter has been fixed upstream. I have added a patch with this fix.
Wed, Nov 5
In T7911#207826, @timegrid wrote:So, for the current vsd docs (3.3): https://gnupg.com/vsd/kleopatra-settings.html
This would be more correct, if i understood it right?HKEY_LOCAL_MACHINE\Software\Wow6432node\GNU\Kleopatra HKEY_CURRENT_USER\Software\Wow6432node\GNU\Kleopatra
Thanks for clarification. I added this to the doc enhancement ticket https://dev.gnupg.org/T7911 and set this ticket to invalid.
I think this is a matter of imprecise documentation.



