Bug 486680 - Okular does not accept blank certificate password when digitally signing PDFs
Summary: Okular does not accept blank certificate password when digitally signing PDFs
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: PDF backend (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Other
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-06 18:50 UTC by Matej Kovacic
Modified: 2024-05-07 15:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Matej Kovacic 2024-05-06 18:50:07 UTC 
SUMMARY
I have installed Okular through Flatpak. I am using Slovenian language version. Since version from 2024-03-12 15:38:44 (Flahub commit: dd1a5b8b88fe55a569a9e38a3855f945be8d9ef46cb42c54884af55892828c39), I can not digitally sign PDF's anymore.

Reason: it keeps asking me for certificate password. I don't have one, but when I press enter (and leave input fields empty), it keeps asking for password.

STEPS TO REPRODUCE
1. Select Tools- Digitally sign
2. Select certificate and background image
3. Okular asks for a certificate password (if exists)
4. Press enter (because I do not have a password), it keeps asking again...

OBSERVED RESULT
Cannot digitally sign PDF, because it keeps asking for (nonexistent) password

EXPECTED RESULT
Should be able to move forward with blank password?

SOFTWARE/OS VERSIONS
flatpak remote-info --log flathub org.kde.okular

All versions after and including this: 

    Commit: dd1a5b8b88fe55a569a9e38a3855f945be8d9ef46cb42c54884af55892828c39
   Subject: Update ghostscript & poppler (a178ad4a)
      Date: 2024-03-12 15:38:44 +0000
Comment 1 Sune Vuorela 2024-05-07 06:40:42 UTC 
Hi

What does the version in 'about okular' report?

If it is 24.02, you likely need to actually click the certificate even if it looks selected. It is a bug fixed in 24.05
Comment 2 Matej Kovacic 2024-05-07 15:42:14 UTC 
The latest version from Flathub is 24.02.2. Yes, I can confirm that if I select certificate manually, it works. Thanks for the tip and explanation. :)