| Summary: | Okular exits every time I open a digitally signed PDF | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | meso5 <meso5> |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | aacid, kde |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 23.08.4 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
meso5
2023-12-09 14:43:14 UTC
Would it be possible for us to have access to that file? (In reply to Albert Astals Cid from comment #1) > Would it be possible for us to have access to that file? The file is technically confidential even though there is nothing particularly exciting in there. Would the file still be useful if I redacted identifying info? The digital signature would then fail but the file may still reveal the problem. If I could locate more digitally signed PDFs I could try them out. (In reply to meso5 from comment #2) > (In reply to Albert Astals Cid from comment #1) > > Would it be possible for us to have access to that file? > > The file is technically confidential even though there is nothing > particularly exciting in there. Would the file still be useful if I redacted > identifying info? The digital signature would then fail but the file may > still reveal the problem. If I could locate more digitally signed PDFs I > could try them out. If it crashes it's useful, but be careful redacting most of the times doesn't really hide the text and tools like pdftotext can still extract it. As it turns out, Acrobat Pro won't let me redact anything because the file is signed, which makes sense. As I said, there is nothing important or interesting in the file and I wouldn't mind sending it to you somehow for debugging as long as it's not publicly available on the web and you commit to discarding it afterwards, but I can't find a way to submit a file confidentially. You can send it to me via email to aacid@kde.org I just emailed it to you. (In reply to meso5 from comment #6) > I just emailed it to you. I'll probably end up reviewing Albert's fix, if not helping implementing it; any chance I can get a copy as well ? sune@kde.org It looks like I touched the crashing code in question last. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! |