Application: okular (21.08.0) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.10.0-8-amd64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Debian GNU/Linux bookworm/sid -- Information about the crash: - What I was doing when the application crashed: I connected a Wacom tablet via Bluetooth. Crashes like these have been happening (about once a day or every two days) but I haven't found a way to reproduce them. The backtrace is only shown for Okular, but all KDE applications that have been running at the time produced a similar (probably for the most part identical) backtrace (akonadi, kontact, dolphin, among others). The crash can be reproduced sometimes. -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x00007f970e21f537 in __GI_abort () at abort.c:79 #6 0x00007f970e65cbf1 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007f970c8bef99 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x00007f970c8cddfa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x00007f970e8af5e0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f970e8b29df in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f970e8b31db in QSocketNotifier::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f970f3c215f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x00007f970e878fca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007f970e8d10d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f970cdcf85b in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007f970cdcfb08 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x00007f970cdcfbbf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x00007f970e8d051f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x00007f970e87798b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x00007f970e87fc00 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x000055e6b176dad2 in ?? () #22 0x00007f970e220d0a in __libc_start_main (main=0x55e6b176d3c0, argc=2, argv=0x7ffd1fe73498, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd1fe73488) at ../csu/libc-start.c:308 #23 0x000055e6b176e86a in ?? () [Inferior 1 (process 20663) detached] Possible duplicates by query: bug 440777, bug 429344, bug 427384, bug 424911, bug 423222. Reported using DrKonqi
The version of Okular, Frameworks and Plasma are from Debian testing/unstable - I've changed the "platform" field to Debian unstable, please feel free to change it to testing if needed (it's not stable for sure). You are running on wayland, could you please test this on X11 too?
I'm running Debian unstable I used X11 exclusively until recently and I have experienced no such problems. I will try to gather more information, but that may take a while because crashes happen by far not every time. I can't say for sure whether connecting the bluetooth tablet is causing the crash, it's just what I did when the crash happened.
I think this may be related to bug 437709. The cause of the crash is probably a different one, but I suppose it was kwin which crashed and took everything with it. Next time this happens I will try to get the backtrace for kwin instead.
Apparently, kwin_wayland doesn't crash when the tablet is connected, but when it first receives input. If it didn't crash during the first input, it won't crash for as long as the tablet is connected. I'm still figuring out how to reproduce the bug. Possibly it's not even related to bluetooth, I will do more testing with the tablet connected via USB.