Works with Gpg4win-5.0.2-beta2
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 2 2026
Fixed.
Here's a full log of a gdb run, which segfaults on start:
full debugview log with a crash on import after trusting the root cert:
Please always attach the full Debugview log. Sometimes (like here) I really want to know everything that was logged since the start.
Fixed. This regression was caused by changes made for T8056: Support config options RSAKeySizes and PGPKeyType for Kf6.
Mar 1 2026
In T8029#212310, @werner wrote:My actual plan is to rework the imp[ort/export of secret keys to gpg-agent. Right now gpg-agent has knowledge of OpenPGP for import/export. This is not good and the required conversion should be moved to a helper tools for easier testing and to have this out of the gpg-agent process. For Kyber we right now don't use any conversion mut store the secret keys in gpg-agent's native format. Thus the passphrase is not necessary. We need to figure out why we have this problem here.
Feb 27 2026
@werner said the reading order should be like on the page https://gnupg.com/vsd/kleopatra-settings.html:
Tested with Gpg4win 5.0.2 (Beta):
Registry settings SOFTWARE\Gpg4win\Kleopatra\<config group>\<config entry>
works (I used [CertificateCreationWizard] EMAIL_placeholder for testing)
This is not "Unbreak now" because we have not released the software yet. Unbreak now should be used for bugs in deployed software but not during development.
Note: This was fine on gpg4win-5.0.1
Regarding some broken "reg create" on some filepath: split into T8141: Kleopatra: Many wrong registry keys created in HKCU\Software\Gpg4Win
I rechecked the keyboxd locking of pubring.db. On crash via gdb the file was unlocked before, so this doesn't seem to be the problem:
Ok in Gpg4win 5.0.2. (Beta), in German:
Libkleo does not specify the curve in the parameter file becuase keyCurvve:isEmpty is asserted:
Works on the command line and adding a subkey later does also work.
config file: Sorry, I got confused, it has to be %APPDATA%\GnuPG VS-Desktop\kleopatrarc in this case (VS-Desktop-4.0.90.1203-Beta), of course. And this one works.
Registry entry SOFTWARE\GnuPG VS-Desktop\Kleopatra\CMS\SaveCSRAsPEM does not work, though. But this is a separate issue, seems all Registry entries do not work in that build.
- config file: According to T7717: Location of qt-application config files %APPDATA%/Gpg4win/kleopatrarc should work.
- registry: According to T5707: Kleopatra: Use windows registry additionally to config files this should be SOFTWARE\Gpg4win\Kleopatra\CMS\SaveCSRAsPEM now
Works with VS-Desktop-4.0.90.1203-Beta when putting this in C:\Program Files\GnuPG VS-Desktop\share\kleopatrarc
CSR is then saved as .pem file with ascii-armored content.
Feb 26 2026
Done and backported for VSD 3.4.
So ok, go ahead Ingo with your plan in https://dev.gnupg.org/T7502#213972
As the migration to keyboxd will happen not too far in the future, we'll close this ticket.
Keylisting should meanwhile already be faster due to other changes.
Closing this as invalid.
I tend to agree with keeping it short and close to the wording we use for normal public key imports.
Ok, the behavior in gpg4win-5.0.0-beta413 @ win10 is the same (< 1s).
I can also reproduce the same behavior in other windows dialogs, e.g. in the explorer (changing the location address, clicking on the search input field).
So i'd also say, that this is a virtualbox or win issue and would just close this as invalid without further testing?
I'll also retest this with gpg4win-5.0.0-beta413. I think, this bug was different back then (no need to do it quickly). If it's gone there, too, it might have been a virtualbox or win bug. If it's still there, it might hint at qt/kde.
It turns out that the problem occurs if one clicks with the mouse quickly (< 1 s) after typing a character.
I was too fast with closing this, seems it is reproducible under special conditions. But not by me, here it works.
Me neither, neither on Win10 or 11. I tried the original description and https://dev.gnupg.org/T7943#208784
I can still reproduce this with gpg4win-5.0.1 @ win11
I cannot reproduce this with the released Gpg4win 5.0.1 on Windows 10 (VM).
Feb 25 2026
Done.
For highlighting the cell see T7954: Kleopatra: Highlight focused cell in tables
Backported for VSD 3.4
We decided to backport to VSD 3.4 because it fixes an accessibility issue.
Backported for VSD 3.4
We decided to backport to VSD 3.4 because it fixes an accessibility issue (wrong tab order).
Fixed.
The fix also fixes the wrong tab order of the Close button. (See T8125: Kleopatra: Wrong tab order of "Show Email" button for the same problem concerning the Show Email button.)
Regarding the above comments:
Currently, the Show Email button is never shown in the notepad and the Close button (as X) is only shown in the notepad. So, in the notepad there's only Show Audit Log next to X. And elsewhere there's Show Audit Log and, if applicable, Show Email below.
This is nothing we want to do in Kleopatra. The "Force" button will be removed shortly even for MDC error.
Please add the hint you mentioned.
Feb 24 2026
Changing the position needs some more thought. There can be up to four buttons displayed next to the result:
- Force decryption is shown if decryption failed due to a missing integrity check (MDC)
- Show Audit Log is always shown (unless retrieving the audit log failed)
- Show Email is shown if the decrypted content is something that can be opened in the mail viewer
- Close is always shown in the notepad
"Show audit log" is already a button (probably changed for another ticket). I'll look into the remaining points.