| Summary: | crash on highlighter usage only after save | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | e.sodja816 |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | aacid, qydwhotmail |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 1.11.2 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
updated backtrace
Valgrind output New crash information added by DrKonqi |
||
|
Description
e.sodja816
2021-03-30 20:37:10 UTC
Can you please follow the instructions from https://wiki.ubuntu.com/Debug%20Symbol%20Packages and install libqt5core5a-dbgsym libqt5widgets5-dbgsym libokular5core9-dbgsym and then attach an updated backtrace that you get when it crashes that will contain more information? Created attachment 137200 [details]
updated backtrace
Does this happen with every single file or just wiht one in particular? If just one, can you share it? If not can you run valgrind okular myfile.pdf and do what you do to make okular crash and then attach the output of valgrind? Created attachment 137238 [details]
Valgrind output
With other documents (smaller ones, ~1.1MB) it reloads before highlight annotations are saved (asks if I would like to save changes as it spontaneously closes the document and reloads it), but not every time, and hasn't crashed all the way so far. With the original document (~2.9MB) it tries to reload after highlighting but crashes without the option to save. This output is from valgrind on smaller file.
There's nothing really there that is useful, without the document so we can try to reproduce and figure it out what's happening there's nothing we can do. 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! Created attachment 149408 [details]
New crash information added by DrKonqi
okular (22.07.70) using Qt 5.15.2
1. Highlight a sentence
2. Save
3. Highlight another sentence
4. Crash
-- Backtrace (Reduced):
#6 0x00007ffb33334a80 in Okular::Page::number() const () from /lib64/libOkular5Core.so.10
[...]
#8 0x00007ffb3f802cde in QWidget::event (this=this@entry=0x562d25e6bd30, event=event@entry=0x7fff5109fe50) at kernel/qwidget.cpp:9020
#9 0x00007ffb3f8af5fe in QFrame::event (this=0x562d25e6bd30, e=0x7fff5109fe50) at widgets/qframe.cpp:550
#10 0x00007ffb3eb7c8c2 in QCoreApplicationPrivate::sendThroughObjectEventFilters (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.cpp:1190
#11 QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x562d25f08970, event=event@entry=0x7fff5109fe50) at kernel/qcoreapplication.cpp:1179
Still nothing really useful in that backtrace #6 0x00007ffb33334a80 in Okular::Page::number() const () from /lib64/libOkular5Core.so.10 #7 0x00007ffb334af496 in ?? () from /usr/lib64/qt5/plugins/okularpart.so Should not be ?? but actual information. Please install debug symbols and try to reproduce again. 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! |