Bug 32436

Summary:	Okular crashes when multiple digital signatures are entered in a document
Product:	Mageia	Reporter:	Jose Manuel López <joselp>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, geiger.david68210, marja11
Version:	9
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	Okular	CVE:
Status comment:

Description Jose Manuel López 2023-10-24 11:54:19 CEST

Description of problem: When I need to sign a document on several sheets, okular saves the first signature correctly, but it crashes when I sign the next sheet and I can no longer open the document. However, I can open that document signed twice with Firefox.

If I need to sign three pages, I cannot finish the task because Okular crashes when I enter the second signature and then try to open the document.

I have seen that the version we currently have is 23.04 and the latest stable version is 23.08, so is it possible that the update will solve the problem?


Version-Release number of selected component (if applicable): Okular in Mageia 9


How reproducible: Install Okular and try to sign a document digitally on two different sheets.

Steps to Reproduce:
1. Install Okular
2. Open a document with several sheets and sign one by one
3. On the second okular signature it crashes and the document cannot be reopened.

Comment 1 Jose Manuel López 2023-10-24 11:59:23 CEST

Trying to open the signed document on the second page from okular in terminal, the following appears: Segmentation violation (`core' generated).

The document does contain the second signature on the second page, but Okular cannot open it.

Comment 2 Marja Van Waes 2023-10-24 22:34:00 CEST

Assigning to the KDE maintainers.

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 3 Jose Manuel López 2023-11-28 13:28:28 CET

Hello!

I have verified that on a computer updated from Mageia 8 I can open the document, so I have also checked which Okular packages the computer had installed.

Apparently, the culprit of the bug is the lib64okular5core10 package. In the update from Mageia 8, the lib64okular5core9 package is maintained, but in the clean installation of Mageia 9, this package evidently does not exist, which is why the Okular crash is generated.

So, it seems that we have a construction error in this package, or it has lost some feature that it had previously.

Comment 4 Jose Manuel López 2023-11-28 13:30:36 CET

As a temporary solution, I have searched for the Mageia 8 package and installed it on Mageia 9, but this is obviously not a good solution for our users. So we should check the new version lib64okular5core10.

Comment 5 Jose Manuel López 2024-04-02 12:59:01 CEST

Hello,

In a clean installation of Mageia 9, I have detected that this library is already loaded with Okular, so I think we should remove this bug.

Greetings!

Comment 6 Morgan Leijström 2024-04-02 18:04:51 CEST

IMO, If this is a fault that appear in upgrade from mga8 it should go into errata.  And even better, getting fixed by an updated package.

I am not clear what you say in Comment 3 & 4, do you mean that after a system upgrade to mga9, the lib64okular5core9 from mga8 is still in the system?

And uninstalling lib64okular5core9 is the fix?

If so optimally it should have been replaced automatically by lib64okular5core10?

CC: (none) => fri

Comment 7 Jose Manuel López 2024-04-03 12:17:02 CEST

Hi all,

When I started upgrading my equipment from Mageia 8, the dependency in question remained. But in a clean installation of Mageia 9 it was not installed.

Currently, in the last clean installs I have done, I have verified that this dependency "lib64okular5core10" is installed, and therefore, the problem is solved, so we can consider the bug closed.

Comment 8 Morgan Leijström 2024-04-03 12:25:54 CEST

Am I correct to add to errata:
On a system upgraded from mga8 to mga9, users have to delete lib64okular5core9?

Comment 9 Jose Manuel López 2024-04-03 12:34:05 CEST

No, no, if that library is also updated during the update, the problem does not occur.

The bug referred to the fact that in a clean installation, that library did not appear as installed, which is why the bug occurred.

Comment 10 Morgan Leijström 2024-04-03 13:53:16 CEST

Ah now i get it :)

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 11 David GEIGER 2024-04-03 16:31:52 CEST

Normally after an update/upgrade if a library is no more used by anything "urpme --auto-orphans" remove it.

CC: (none) => geiger.david68210