This is fixed.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 19 2025
Nov 18 2025
I believe this bug was fixed by T7829. Please confirm with new gpgwin-5.0.0-beta.
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.
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:
Nov 12 2025
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.
Nov 11 2025
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)
Nov 6 2025
The problem with Enter has been fixed upstream. I have added a patch with this fix.
Nov 5 2025
Fixed. Kleopatra and the GnuPG System configuration and error messages coming from GnuPG should now always use the configured Windows display language regardless of the Preferred languages or the Regional format. (GnuPG on the command line will still use the Regional format.)
Nov 4 2025
The language settings of Windows have strange influence on Kleopatra and GnuPG.
Werner said we leave it as is for vsd3.3.3 and only change reading order of the configs for the change to the next mayor release.
So I retag this ticket for gpd5x. timegrid has made a separate ticket for updating the documentation.
Fixed.
Nov 3 2025
I'm fixing this in Kleopatra similarly to gpg-card.
VS-Desktop-3.3.90.31-Beta shows no warning any more for the export of a newly generated key.
Oct 31 2025
Looks good to me on vsd-3.3.3-beta90.29 @ win11
Oct 30 2025
An new suggestion for the wording without prior reading of the above texts to get a fresh view.
But in German ...
@werner Proposed patch for gpg:
diff --git a/g10/export.c b/g10/export.c index 5dcb9c665..908a6b6a0 100644 --- a/g10/export.c +++ b/g10/export.c @@ -1961,7 +1961,9 @@ do_export_one_keyblock (ctrl_t ctrl, kbnode_t keyblock, u32 *keyid, if (strchr (hexgrip, ',')) { log_error ("exporting a secret dual key is not yet supported\n"); - return gpg_error (GPG_ERR_NOT_IMPLEMENTED); + err = gpg_error (GPG_ERR_NOT_IMPLEMENTED); + write_status_error ("export_keys.secret", err); + return err; }
Move Notepad and Smartcards from View to Tools (entries are additionally still in view)
Backported for VSD 3.4 and VSD 3.3.
Oct 29 2025
I couldn't reproduce the problem because I had apparently told Kleopatra in the past "Do not ask again". :/
I think this problem just occurs because the secret key of the ADSK is available. Otherwise, Kleopatra wouldn't know whether the ADSK is stored on a smart card and therefore wouldn't erroneously take a non-card key for a card key.
Well, in the audit log the output of gpg is shown, nothing Kleo can do there, I believe.
But we need to talk about what still needs to be / can be implemented on the Kleo side.
The API documentation of gpgme has been improved. And Kleopatra no longer tries to read the private key files of subkeys using combined algorithms (like Kyber+some curve) because (as of now) such keys are not stored on any smart cards (that are supported by GnuPG).
New ticket for the remaining issue.