https://bugs.kde.org/show_bug.cgi?id=430111
--- Comment #11 from Mathew Robinson <mat...@chasinglogic.io> --- Based on the line "#3 QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffefef4eb40, msg=msg@entry=0x7fe8b70350b8 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:893" from the previous backtrace I decided to try and run gdb on kwin_wayland and it looks like there's perhaps a segfault? Breakpoint 1 at 0x7f4c29c00490 Breakpoint 2 at 0x7f4c29c004e0 Continuing. Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. 0x00007f4c2b4afc08 in KWaylandServer::SurfaceInterface::frameRendered(unsigned int) () from /usr/lib64/libKWaylandServer.so.5 -- You are receiving this mail because: You are watching all bug changes.
