Appears on shutdowns and reboots, e.g. when kwin_x11 is killed by systemd. I got this backtrace by attaching to kwin_x11 with gdb and running "init 3" from within the session. Thread 1 "kwin_x11" received signal SIGHUP, Hangup. 0x00007f377db1fbd9 in pselect () from /lib64/libc.so.6 (gdb) c Continuing. [Thread 0x7f3764b1a700 (LWP 4153) exited] Thread 1 "kwin_x11" received signal SIGTERM, Terminated. 0x00007f377e004690 in ?? () from /usr/lib64/libkdeinit5_kwin_x11.so (gdb) Continuing. [Thread 0x7f375d0fa700 (LWP 4260) exited] [Thread 0x7f376159f700 (LWP 4258) exited] [Thread 0x7f3762c3c700 (LWP 4157) exited] Thread 1 "kwin_x11" received signal SIGSEGV, Segmentation fault. 0x00007f377b1a8d4a in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 (gdb) bt #0 0x00007f377b1a8d4a in QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #1 0x00007f377beafe78 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #2 0x00007f377beb449a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #3 0x00007f377b1a8fa5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #4 0x00007f377b1daaa2 in QObjectPrivate::setParent_helper(QObject*) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f377b1dafd2 in QObject::~QObject() () from /usr/lib64/libQt5Core.so.5 #6 0x00007f376221cf79 in KWin::X11StandalonePlatform::~X11StandalonePlatform() () from /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #7 0x00007f377b19d2a1 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007f377b19eb3d in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x00007f377da7449f in __cxa_finalize () from /lib64/libc.so.6 #10 0x00007f377afbc3e3 in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x00007ffe00908ca0 in ?? () #12 0x00007f377e21a21a in _dl_fini () from /lib64/ld-linux-x86-64.so.2 Reproducible: Sometimes Qt 5.6.1 on openSUSE Leap 42.2 Beta 3. Nouveau driver used, which shouldn't matter here AFAICT.
Could you get a backtrace with debug symbols?
Setting status.
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 set the bug status 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!
Didn't happen anymore on that machine.