Application: okular (21.08.1) Qt Version: 5.15.2 Frameworks Version: 5.86.0 Operating System: Linux 5.13.0-40-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.22.5 Distribution: Ubuntu 21.10 -- Information about the crash: - What I was doing when the application crashed: I marked some excerpts with the yellow marker and changing back to the normal mode. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140498820476480) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140498820476480) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140498820476480, signo=signo@entry=6) at pthread_kill.c:91 #7 0x00007fc8721c9476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007fc8721af7b7 in __GI_abort () at abort.c:79 #9 0x00007fc872658ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007fc870bd9e45 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x00007fc870bea06a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x00007fc8728b8a88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007fc8728bbf63 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007fc8728bc793 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007fc8734016b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x00007fc87288116a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007fc8728db155 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007fc870f2a8bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007fc870f7df08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007fc870f28003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007fc8728da548 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x00007fc87287fa9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x00007fc872888024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x000055848a9e3c4a in ?? () #25 0x00007fc8721b0fd0 in __libc_start_call_main (main=main@entry=0x55848a9e2700, argc=argc@entry=2, argv=argv@entry=0x7ffd3a8f6e38) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x00007fc8721b107d in __libc_start_main_impl (main=0x55848a9e2700, argc=2, argv=0x7ffd3a8f6e38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd3a8f6e28) at ../csu/libc-start.c:409 #27 0x000055848a9e4665 in ?? () [Inferior 1 (process 16493) detached] Possible duplicates by query: bug 452621, bug 451511, bug 450494, bug 450084, bug 449552. Reported using DrKonqi
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!