| Summary: | Okular crashed after using the yellow marker | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | leanwei |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | aacid |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 21.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-5708-0.html
attachment-2988-0.html |
||
|
Description
leanwei
2022-05-08 13:06:51 UTC
Can you run the application from konsole (or other terminal) and attach the error you get there when this crash happens? Created attachment 148678 [details] attachment-5708-0.html Dear Mr Cid I tried to follow your instruction. Okular crashed again and I got the following error: leander@leander-System-Product-Name:~$ okular The Wayland connection broke. Did the Wayland compositor die? KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = okular path = /usr/bin pid = 6407 KCrash: Arguments: /usr/bin/okular KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Angehalten okular leander@leander-System-Product-Name:~$ QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. Thank you very much for solving this problem. Yours sincerely, Leander Weihs Am 08.05.22 um 23:26 schrieb Albert Astals Cid: > https://bugs.kde.org/show_bug.cgi?id=453540 > > Albert Astals Cid<aacid@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |aacid@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > > --- Comment #1 from Albert Astals Cid<aacid@kde.org> --- > Can you run the application from konsole (or other terminal) and attach the > error you get there when this crash happens? > > The reporter is unsure if this crash is reproducible.
How can you be unsure? Can't you try again and see if it crashes again?
Created attachment 148707 [details]
attachment-2988-0.html
Dear Mr Cid
I am unsure which information you are needing. I already reproduced the
crash and sent the error message to you, but I will send it again.
Error message from Konsole:
leander@leander-System-Product-Name:~$ okular
The Wayland connection broke. Did the Wayland compositor die?
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = okular path = /usr/bin pid = 6407
KCrash: Arguments: /usr/bin/okular
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
[1]+ Angehalten okular
leander@leander-System-Product-Name:~$ QSocketNotifier: Invalid socket 8
and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
Yours sincerely
Leander Weihs
Does it happen with any file? Also your Okular is a bit old, can you try okular from flathub at https://flathub.org/apps/details/org.kde.okular and see if it still crashes for you? 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! |