Best test this with a newer installer than gpg4win-5.0.0-beta413 to avoid the regression with the raw HTML (see T7886#208675).
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 24 2025
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 23 2025
git checkout gnupg-2.5.14, reverted the commits 46f4cb66125ee34e87e592cc02d38daead3427af and 0cc7759ed5a3890b4e28563a6b5e97f3aa551530, recompiled, and the error message gpg: keydb_search_first failed: SQL error no longer appeared. Also, in /root/.gnupg/public-keys.d/, the two files pubring.db.lock and .#lk0x0000... are present.
Nov 22 2025
Nov 21 2025
Looks good to me on gpg4win-5.0.0-beta413 @ win11.
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.
As this looks good to me on gpg4win-5.0.0-beta413 @ win11, I move this to done on the gpd5x board.
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
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.
Looks good to me on gpg4win-5.0.0-beta413 @ win11
When --output option is used and the user uses temporary file and is ready for checking an error, that is, it's already prepared, it's redundant and useless, indeed.
Let me explain about the change rG57affc4e98ab.
Additionally, in the /root/.gnupg/public-keys.d/ directory, the two files .#lk0x00007fdcb40043b0.b02bef684bbe.5108 and pubring.db.lock are missing.
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.
You can also delete the `#include "deletejob.h" in job.cpp. Other than that it's ready for merge.
Done now, sorry for the confusion around the contructor
gpg was compiled with the latest version of SQLite3 at the time as its own private library, without linking against the system's libsqlite3.so.
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.
Can you please schek which Sqlite version you have installed? I have not seen this on my system.



