Thanks, confirmed then, moving to Done.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 30 2025
Issue with pretty kyber names moved into: T7708.
Moving this to done.
General issues with unformatted fingerprints/keyids moved into T7707.
Ingo tested this and it worked.
Looks good to me on gpg4win-5.0.0-beta336 @ win10:
- Full stops are fine now
- "not VS-NfD compliant" for invalid signatures not shown anymore (tested in vsd compliance mode)
Looks good to me on gpg4win-5.0.0-beta336 @ win10:
With above configuration it seems to work on gpg4win-5.0.0-beta336 @ win10.
Any way to verify in kleopatra, that the setting was applied?
Tested on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
I tested the VSD elements on gpg4win-5.0.0-beta336 @ win10 (beta compliance mode).
Happens also in the group config (warning icon):
Looks good to me on gpg4win-5.0.0-beta336 @ win10.
Jun 27 2025
Mostly looks good to me on gpg4win-5.0.0-beta336 @ win10/win11.
Related? In smartcards view:
Jun 26 2025
Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).
Thanks for the feedback. The issues are the same as on win10:
Jun 25 2025
- Issues found
On gpg4win-5.0.0-beta330 everything works fine again (both smime and openpgp regardless of expiration).
Jun 24 2025
I now imported all certs in testzertifikate_2023/ (smime and openpgp) and generated a new one (openpgp, default settings, expiration 2028) and still get no valid signing certs in okular
added gpgsm log:
Ingo mentioned some maybe related expiration year 2038+ ticket, but I only found one for kleo: https://dev.gnupg.org/T7069
Issue about no valid smime certs found on signing split into: https://dev.gnupg.org/T7697
Jun 23 2025
3 non-hang logs, all took ~20s to open the file (with 20s "Keine Rückmeldung" shown in Okular)
Here's the gpgsm debug log (debug x509,ipc,lookup):
It could be connected to those "keylists hangs" problems. On Kleopatra it took some time to refresh the key list. After that I can open the signed file again.
Well, now I also can reproduce the hanging on verification again (opening of an unsigned document is fine, of a signed document hangs).
Maybe the signing part above is important to trigger it - although it happened now in a clean state after a reboot, so it should not be caused by e.g. leftover processes.
I'm quite sure, that I used a fresh install on a new VM, but on another fresh one I can't reproduce the verification part anymore and the signature is shown as valid.
May 23 2025
May 22 2025
In T7658#201260, @TobiasFella wrote:That screenshot is for kleopatra crashing, not related to okular.
May 20 2025
tested on gpg4win-4.4.1-beta59@win10
looks good to me on gpg4win-4.4.1-beta59@win10
looks good to me on gpg4win-4.4.1-beta59@win10
looks good to me on gpg4win-4.4.1-beta59@win10
also fine on vsd-3.3.2.0@win10
looks good to me on gpg4win-4.4.1-beta59@win10
looks good to me on gpg4win-4.4.1-beta59@win10
looks good to me on gpg4win-4.4.1-beta59@win10
looks good to me on gpg4win-4.4.1-beta59@win10
May 16 2025
May 13 2025
basically solved, for follow up see
after https://dev.gnupg.org/rW14d86c01819ef3ddbc7f03b34e821e367cea3b02 only qrencode is left:
currently not testable. some urls in download.sh are broken (404):
there are no display warnings
May 12 2025
looks good to me on gpg4win-5.0.0-beta190@win10
looks good to me on gpg4win-5.0.0-beta190@win10
on gpg4win-5.0.0-beta190@win10 (high contrast):
looks good to me on gpg4win-5.0.0-beta190@win10















