Summary: | Crash on pdf file opening (file compiled in latex) | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Respawner289 |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aacid, Respawner289 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 22.04.3 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Respawner289
2022-08-17 17:25:45 UTC
Please include a backtrace with debug symbols. (In reply to Albert Astals Cid from comment #1) > Please include a backtrace with debug symbols. How do I can do this? I installed okular-debuginfo. If crash happened again, I attach more info to this bug. Thanks for your replies and attention to issue. Created attachment 151425 [details]
New crash information added by DrKonqi
okular (22.04.3) using Qt 5.15.5
Now Okular crashed again. Debug backtrace attached below.
-- Backtrace (Reduced):
#7 0x00007ff7a8452aa8 in OutlineItem::open() () from /lib64/libpoppler.so.123
#8 0x00007ff7a8452ae9 in OutlineItem::hasKids() () from /lib64/libpoppler.so.123
#10 0x00007ff7a86cd542 in PDFGenerator::generateDocumentSynopsis (this=0x56078deb0360) at /usr/src/debug/okular-22.04.3-1.1.x86_64/generators/poppler/generator_pdf.cpp:963
#11 PDFGenerator::generateDocumentSynopsis (this=0x56078deb0360) at /usr/src/debug/okular-22.04.3-1.1.x86_64/generators/poppler/generator_pdf.cpp:945
#12 0x00007ff7b15ed7fc in TOC::notifySetup (this=0x56078ddffd10, setupFlags=<optimized out>) at /usr/src/debug/okular-22.04.3-1.1.x86_64/part/toc.cpp:78
You're still missing the poppler debug information. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |