SUMMARY Okular segfaults when opening any PDF document produced using the Adobe Sign service. STEPS TO REPRODUCE 1. Open a PDF produced using Adobe Sign in Okular A sample PDF is available here: https://www.rathbonelaw.com/~logan/blah.pdf SOFTWARE/OS VERSIONS Linux Operating System: Slackware Current KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Kernel Version: 4.14.59 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4710HQ CPU @ 2.50GHz Memory: 7.7 GiB of RAM ADDITIONAL INFORMATION This is likely the same issue as bug 408254 which was closed automatically due to a lack of information. I cannot reproduce on Chromium, xpdf or Master PDF Editor.
(In reply to Logan Rathbone from comment #0) > SUMMARY > > Okular segfaults when opening any PDF document produced using the Adobe Sign > service. Can you 1. Post the poppler version ("pdftotext -v" in console). 2. Attach a file to test. ? Can it be a duplicate of https://bugs.kde.org/show_bug.cgi?id=407731 ? Thanks in advance for your answers.
Created attachment 127546 [details] sample pdf
Output of pdftotext -v: *** pdftotext version 0.68.0 Copyright 2005-2018 The Poppler Developers - http://poppler.freedesktop.org Copyright 1996-2011 Glyph & Cog, LLC *** I'm not sure if it's a duplicate of bug 407731. The sample PDF attached to that bug report works fine for me.
(In reply to Logan Rathbone from comment #3) > Output of pdftotext -v: > > *** > pdftotext version 0.68.0 > Copyright 2005-2018 The Poppler Developers - http://poppler.freedesktop.org > Copyright 1996-2011 Glyph & Cog, LLC > *** > > I'm not sure if it's a duplicate of bug 407731. The sample PDF attached to > that bug report works fine for me. Ok. Maybe https://bugs.kde.org/show_bug.cgi?id=407338 then? If so, you just need to patch your poppler with https://gitlab.freedesktop.org/poppler/poppler/commit/eaeac5c7dba6f53acef3f0be6b226facecfc5f28.diff It's a fixed poppler bug anyway. Your file does not crash my Okular 20.07.70 with poppler 0.87.0.
(In reply to Yuri Chornoivan from comment #4) > [snip] > > If so, you just need to patch your poppler with > > https://gitlab.freedesktop.org/poppler/poppler/commit/ > eaeac5c7dba6f53acef3f0be6b226facecfc5f28.diff > > It's a fixed poppler bug anyway. Your file does not crash my Okular 20.07.70 > with poppler 0.87.0. That patch doesn't apply cleanly against poppler 0.68 so I can't test. I also couldn't produce a patch that applies cleanly as the functions that are being added to don't exist on 0.68 and I don't know the codebase well enough to adapt it. Anyway, it sounds like it's highly unlikely to be an Okular bug based on what you're saying. This can be closed IMO as worksforme or otherwise. When Okular does crash on XFce on my machine when opening such PDFs, it doesn't close cleanly and it launches drkonqi, which in turn hangs and takes up 100% cpu until I manually kill all of the processes, but that's a different story.
Meanwhile you can always try Okular from flathub, it has it's own different set of issues caused by the flatpak technology but it is a mode moden version that whatever old stuff slackware provides https://flathub.org/apps/details/org.kde.okular Now i just realized slackware probably doesn't provide flatpak either