Things for the Okular PDF Tool.
Details
Fri, Jan 23
@werner: Is this resolved?
Wed, Jan 21
I also tested to add the qual flag to the root cert in the global trusted.txt, as using qualified.txt is considered legacy, but still the same behavior
The first time Okular was included is gpg4win-4.2.0:
See here for how it should look like:
I see. I added the root cert to C:\ProgramData\GNU\etc\gnupg\qualified.txt and the usage of the signing certs does include a qualified signature in Kleopatra now. Still I don't see any highlight/filter in Okular:
Tue, Jan 20
None of these certificates are for qualified signatures.
Try compare with a gpg4win 3.latest.
Thu, Jan 15
On gpg4win-5.0.0 @ win11 I created a bunch of smime certs:
- For each keyusage
- keyEncipherment, dataEncipherment
- digitalSignature
- nonRepudiation
- digitalSignature, nonRepudiation
- Alice's certs with different names, Bob's certs with same name for each key
Wed, Jan 14
Was anything changed? What to test here?
Tue, Jan 13
Thanks, looks good to me:
- Saving to c:\windows
- Saving with removed signing key
A way to trigger some errors could be trying to save to c:\windows or some other place you can't do.
Or while you have the key list open in okular, remove the key underneath everything and then continue.
We now have a filter for qualified signatures if there is any in the list
Fixed upstream with https://invent.kde.org/graphics/okular/-/merge_requests/1301 - not yet in our packaging
Fri, Jan 9
That was also fixed in gnupg 2.2.50 and thus vsd 3.3.3
Thu, Jan 8
Looks good to me on gpg4win-5.0.0-beta479 @ win11.
Wed, Jan 7
>gpgsm -v --sign --local-user "Edward Tester" test.pdf > test.gpg.p7s
gpgsm: enabled compatibility flags:
gpgsm: looking up issuer from the Dirmngr cache
gpgsm: number of matching certificates: 0
gpgsm: dirmngr cache-only key lookup failed: No data
gpgsm: issuer certificate {04A0A7E932B29D43A9B6673139AF52C0A5FC467BF5A64D044D1AC33613ABBB73CA532569F5779999114C0118CD66FDF6E92B1B0EEE2A4D5A815DA7FD892DDDE9C1} not found using authorityKeyIdentifier
gpgsm: looking up issuer from the Dirmngr cache
gpgsm: number of matching certificates: 0
gpgsm: dirmngr cache-only key lookup failed: No data
gpgsm: certificate is good
gpgsm: root certificate is not marked trusted
gpgsm: fingerprint=D4:EC:A6:B4:69:AB:B5:44:08:27:CB:3F:C7:D7:91:08:3C:10:27:DB
gpgsm: DBG: BEGIN Certificate 'issuer':
gpgsm: DBG: serial: 01
gpgsm: DBG: notBefore: 2020-03-26 19:41:01
gpgsm: DBG: notAfter: 2063-04-05 17:00:00
gpgsm: DBG: issuer: CN=Root-CA 2020,OU=GnuPG.com,O=g10 Code GmbH,C=DE
gpgsm: DBG: subject: CN=Root-CA 2020,OU=GnuPG.com,O=g10 Code GmbH,C=DE
gpgsm: DBG: hash algo: 1.2.840.113549.1.1.11
gpgsm: DBG: SHA1 Fingerprint: D4:EC:A6:B4:69:AB:B5:44:08:27:CB:3F:C7:D7:91:08:3C:10:27:DB
gpgsm: DBG: END Certificate
gpgsm: after checking the fingerprint, you may want to add it manually to the list of trusted certificates.
gpgsm: validation model used: shell
gpgsm: can't sign using 'Edward Tester': Not trusted
[GNUPG:] FAILURE gpgsm-exit 50331649How does gpgsm react if you try to sign with the certificate?
Tue, Jan 6
Maybe it would be better to just not offer S/MIME certs with distrusted root cert?
Note: It does not seem to be possible to open a pdf from an URL, at least not via CLI okular.exe <URL> (it says Unknown protocol 'https').
I tried to get any error response but found those issues instead:
If all processes are killed before okular is opened, i get an error:
gpgsm.log (debug-all, whole process of signing)
Looks good to me on gpg4win-5.0.0-beta479 @ win11. The default path is now the same as the path of the opened file:
Dec 23 2025
Yes, Kleopatra quits again with the beta from yesterday:
Dec 22 2025
Fixed in gpg4win-5.0.0-beta476
Fixed by applying a patch to our version of MinGW. This affected all Qt programs build with Qt 6.10.




