https://bugs.kde.org/show_bug.cgi?id=519923
Tobias Zwick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #4 from Tobias Zwick <[email protected]> --- The journal log indeed shows that the calculator produces a segfault and then somehow takes Wayland with it. This is the reason why all applications running on Wayland also exited (some applications tried to reconnect to Wayland). A snippet from the logs: Mai 06 16:35:16 um780xtx kernel: calculator[679649]: segfault at 10 ip 00007fa1bdae5e48 sp 00007fa19ac7e5d8 error 4 in libgmp.so.10.5.0[70e48,7fa1bda86000+7e000] likely on CPU 4 (core 4, socket 0) Mai 06 16:35:16 um780xtx kernel: Code: 48 89 de ff 15 01 4d 03 00 48 89 c1 8b 83 c0 09 00 00 89 81 c0 09 00 00 5b 41 5c 5d c3 0f 1f 44 00 00 f3 0f 1e fa 48 8b 47 18 <ff> 60 10 0f 1f 44 00 00 f3 0f 1e fa 48 8b 46 18 ff 60 18 0f 1f 44 Mai 06 16:35:16 um780xtx systemd-coredump[679678]: Process 676041 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing... I'll set to confirmed because this might already be enough information for developers (I am just a fellow bug reporter, trying to help with triage). -- You are receiving this mail because: You are watching all bug changes.
