https://bugs.kde.org/show_bug.cgi?id=432884
--- Comment #6 from Nate Graham <n...@kde.org> --- Oh so you did! My mistake, sorry. Here's the relevant part: Stack trace of thread 28126: #0 0x00007f47a0484ae5 raise (libc.so.6 + 0x3dae5) #1 0x00007f47a1d6ee70 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x6e70) #2 0x00007f47a0484b70 __restore_rt (libc.so.6 + 0x3db70) #3 0x00007f47a0484ae5 raise (libc.so.6 + 0x3dae5) #4 0x00007f47a046d864 abort (libc.so.6 + 0x26864) #5 0x00007f47a09010e7 qt_message_fatal (libQt5Core.so.5 + 0xbb0e7) #6 0x00007f479f349f79 _ZNK15QtWaylandClient15QWaylandDisplay10checkErrorEv (libQt5WaylandClient.so.5 + 0x70f79) #7 0x00007f479f358e0a _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x7fe0a) #8 0x00007f47a0b53900 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x30d900) #9 0x00007f47a0b7487c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x32e87c) #10 0x00007f47a0b1bcab _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d5cab) #11 0x00007f47a0b23f20 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2ddf20) #12 0x0000557b301b0189 n/a (drkonqi + 0x32189) #13 0x00007f47a046f152 __libc_start_main (libc.so.6 + 0x28152) #14 0x0000557b301b120e _start (drkonqi + 0x3320e) -- You are receiving this mail because: You are watching all bug changes.