SUMMARY System became unresponsive so I tried to kill kwin_wayland which resulted in a segmentation fault. > #0 0x00007fe2c7de448c in KWin::ModifierOnlyShortcuts::keyEvent(KWin::KeyEvent*) () at /usr/lib/libkwin.so.5 > #1 0x00007fe2c7cc7f51 in KWin::KeyboardInputRedirection::processKey(unsigned int, KWin::InputRedirection::KeyboardKeyState, unsigned int, KWin::LibInput::Device*) () at /usr/lib/libkwin.so.5 > #2 0x00007fe2c6f769d0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 > #3 0x00007fe2c7e2f3aa in () at /usr/lib/libkwin.so.5 > #4 0x00007fe2c7dfb05f in () at /usr/lib/libkwin.so.5 > #5 0x00007fe2c6f77152 in QObject::event(QEvent*) () at /usr/lib>/libQt5Core.so.5 > #6 0x00007fe2c735ae24 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 > #7 0x00007fe2c73626e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 > #8 0x00007fe2c6f4be99 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 > #9 0x00007fe2c6f4ef38 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 > #10 0x00007fe2c6f9eefd in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 > #11 0x00007fe2bee54e9e in () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so > #12 0x000055e8e70e28fb in () > #13 0x000055e8e70e0421 in () > #14 0x00007fe2c6978223 in __libc_start_main () at /usr/lib/libc.so.6 > #15 0x000055e8e70e131e in _start ()
Please provide steps to reproduce. Also, the backtrace lacks debug symbols. Please repackage kwin and submit a new backtrace. https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#CMAKE_(KDE)_applications https://wiki.archlinux.org/index.php/Arch_Build_System#Retrieve_PKGBUILD_source_using_Git
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 mark the bug 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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!
Created attachment 124433 [details] Backtrace Had unrelated to that the debugger running and something similar happened on logout. Backtrace attached.
That's a good backtrace! I assume that crash happens here !workspace()->globalShortcutsDisabled()) { Most likely, we process libinput events after Workspace is deleted.
Urgh, the problem is much deeper. InputRedirection and Workspace have completely unrelated lifetimes.
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!