Application: okular (22.04.1) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.18.13-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Okular crashes everytime I close it with signed document. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x00007f2ff246ca1e in ?? () from /opt/e-dowod/e-dowod-pkcs11-64.so #5 0x00007f2ff2483bc2 in ?? () from /opt/e-dowod/e-dowod-pkcs11-64.so #6 0x00007f2ffb724eec in PK11_DestroySlot () from /lib64/libnss3.so #7 0x00007f2ffb729952 in SECMOD_DestroyModule () from /lib64/libnss3.so #8 0x00007f2ffb729c9e in SECMOD_DestroyModuleListElement () from /lib64/libnss3.so #9 0x00007f2ffb72a105 in SECMOD_DestroyModuleList () from /lib64/libnss3.so #10 0x00007f2ffb72a18d in SECMOD_Shutdown () from /lib64/libnss3.so #11 0x00007f2ffb6e13d0 in nss_Shutdown () from /lib64/libnss3.so #12 0x00007f2ffb6e14b8 in NSS_Shutdown () from /lib64/libnss3.so #13 0x00007f2ff2e637bd in shutdownNss() () from /lib64/libpoppler.so.117 #14 0x00007f301aa41085 in __run_exit_handlers () from /lib64/libc.so.6 #15 0x00007f301aa41200 in exit () from /lib64/libc.so.6 #16 0x00007f301aa29557 in __libc_start_call_main () from /lib64/libc.so.6 #17 0x00007f301aa29609 in __libc_start_main_impl () from /lib64/libc.so.6 #18 0x00005613ca75d775 in _start () [Inferior 1 (process 52143) detached] The reporter indicates this bug may be a duplicate of or related to bug 424056. Reported using DrKonqi
You may want to figure out who wrote that e-dowod-pkcs11-64.so end tell them. I don't think there's much we can do here. I guess I would be silly in hoping the Polish goverment released that as free software?
*** Bug 467642 has been marked as a duplicate of this bug. ***
This is mostly a poppler bug, it needs not to call shutdownNss from an exit handler
*** Bug 469044 has been marked as a duplicate of this bug. ***
*** Bug 477053 has been marked as a duplicate of this bug. ***
(In reply to fanzhuyifan from comment #5) > *** Bug 477053 has been marked as a duplicate of this bug. *** The backtrace for 477053 is highly similar to that of 469044, which has been marked a duplicate of this one.
*** Bug 478005 has been marked as a duplicate of this bug. ***
(In reply to fanzhuyifan from comment #7) > *** Bug 478005 has been marked as a duplicate of this bug. *** Same reason for marking as above
Is this an upstream problem? If not I think this should be marked as confirmed just by the number of duplicates.