Bug 485747

Summary:	PDF signature dialog should preselect (only) certificate
Product:	[Applications] okular	Reporter:	Frank Siegert <frank.siegert>
Component:	PDF backend	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	kde
Priority:	NOR
Version First Reported In:	24.02.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Frank Siegert 2024-04-18 17:30:16 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When signing a PDF document with Okular, and even with only one certificate being available, no certificate is preselected. This leads to unnecessary work, but more importantly, it leads to a spurious error message if the user does not notice this being inactive: "Enter certificate password" (even if there is no password for the certificate).

STEPS TO REPRODUCE
1. Open PDF in Okular
2. Tools - Digitally Sign
3. Choose a position and click.

OBSERVED RESULT
The first field (Select certificate to sign with) is inactive, even despite looking active in my Qt style.

EXPECTED RESULT
The first field should have a certificate selected by default, at least if there is only one certificate.

SOFTWARE/OS VERSIONS
Linux/Sway
KDE Plasma Version: 
KDE Frameworks Version: 24.02.2
Qt Version: 6.7.0

ADDITIONAL INFORMATION

Comment 1 Sune Vuorela 2024-04-19 06:56:13 UTC

(In reply to Frank Siegert from comment #0)
> When signing a PDF document with Okular, and even with only one certificate
> being available, no certificate is preselected. This leads to unnecessary
> work, but more importantly, it leads to a spurious error message if the user
> does not notice this being inactive: "Enter certificate password" (even if
> there is no password for the certificate).

Should be fixed in master around 6 weeks ago; there are no further 24.02 branch releases planned, so will be available with 24.05

Comment 2 Frank Siegert 2024-04-19 09:42:47 UTC

Oh, that's great, thanks for the information and work on this!