Today
The previous pkgsrc version was 2.4.9. However, I've just tested 2.5.14 and saw the same behaviour (so I guess there is no point in testing 2.5.16).
For now I'll commit the following German translations, fixing spelling plus other slight changes:
Do you remember wether you had the same problem also with 2.5.14 or 2.5.16? Or can you test with these versions? Which version of libgpg-error are you using?
When I kill the gpg process, I see:
("/tmp/security/gnupg2/work/gnupg-2.5.17/g10/gpg" --no-permission-warning --no-greeting --no-secmem-warning --batch "--agent-program=/tmp/security/gnupg2/work/gnupg-2.5.17/agent/gpg-agent|--debug-quick-random" --list-sec
ret-keys) failed: gpg: starting migration from earlier GnuPG versionsMy 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.
Yesterday
This ticket is explicitly about Kleopatra included in Gpg4win.
Kleopatra is also run on GNU/Linux Distributions.
This is a security update
Option works in Gpg4win-5.0.1 with GnuPG 2.5.17
works in Gpg4win 5.0.1 with GnuPG 2.5.17
Gpg4win 5.0.0 (2026-01-14)
Mon, Jan 26
To reproduce the hang, a loop will suffice (usually happens within the first 15 times, once it needed 50 runs):
Panel Used By
| Dashboard | Mfcx's Dashboard |