SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Touching the touchscreen while the Plasma Wayland session is starting results in the session crashing and restarting, though the restart is usually not successful and I have to do a full reboot. I'm unable to get a backtrace at the moment, will post one once I'm able to get it. STEPS TO REPRODUCE 1. Start a Plasma wayland session. 2. Touch the touchscreen before the desktop loads. OBSERVED RESULT Plasma Wayland crashes. EXPECTED RESULT Plasma Wayland should ignore the touch and keep loading. SOFTWARE/OS VERSIONS Linux: Gentoo Linux 2.9; kernel 6.0.18 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Using a ThinkPad T14 Gen 3 AMD with i2c-hid touchscreen.
Thread 1 "kwin_wayland" received signal SIGSEGV, Segmentation fault. KWin::Output::modeSize (this=0x0) at /var/tmp/portage/kde-plasma/kwin-5.26.5/work/kwin-5.26.5/src/core/output.cpp:189 189 /var/tmp/portage/kde-plasma/kwin-5.26.5/work/kwin-5.26.5/src/core/output.cpp: No such file or directory. Thread 1 (Thread 0x7efc092e3640 (LWP 5346) "kwin_wayland"): #0 KWin::Output::modeSize() const (this=0x0) at /var/tmp/portage/kde-plasma/kwin-5.26.5/work/kwin-5.26.5/src/core/output.cpp:189 #1 0x00007efc1018e11b in KWin::LibInput::Connection::processEvents() (this=0x562a98fa5a40) at /var/tmp/portage/kde-plasma/kwin-5.26.5/work/kwin-5.26.5/src/backends/libinput/connection.cpp:347 #2 0x00007efc0e86fab5 in QObject::event(QEvent*) (this=0x562a98f1c1f0, e=0x7efbe4005a10) at /var/tmp/portage/dev-qt/qtcore-5.15.8/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:1347 #3 0x00007efc0df085db in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x562a98f1c1f0, e=0x7efbe4005a10) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qapplication.cpp:3640 #4 0x00007efc0e84e198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x562a98f1c1f0, event=0x7efbe4005a10) at /var/tmp/portage/dev-qt/qtcore-5.15.8/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qcoreapplication.cpp:1064 #5 0x00007efc0e84e383 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x562a98dabbf0) at /var/tmp/portage/dev-qt/qtcore-5.15.8/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qcoreapplication.cpp:1821 #6 0x00007efc0e899685 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x562a98daf340, flags=flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.15.8/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qeventdispatcher_unix.cpp:468 #7 0x0000562a97d3c371 in QUnixEventDispatcherQPA::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=<optimized out>, flags=...) at /var/tmp/portage/dev-qt/qtgui-5.15.8-r1/work/qtbase-everywhere-src-5.15.8/src/platformsupport/eventdispatchers/qunixeventdispatcher.cpp:63 #8 0x00007efc0e84d3fb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ffd263680d0, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.8/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/global/qflags.h:69 #9 0x00007efc0e84e75a in QCoreApplication::exec() () at /var/tmp/portage/dev-qt/qtcore-5.15.8/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/global/qflags.h:121 #10 0x00007efc0ecfce10 in QGuiApplication::exec() () at /var/tmp/portage/dev-qt/qtgui-5.15.8-r1/work/qtbase-everywhere-src-5.15.8/src/gui/kernel/qguiapplication.cpp:1870 #11 0x00007efc0df06929 in QApplication::exec() () at /var/tmp/portage/dev-qt/qtwidgets-5.15.8/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qapplication.cpp:2832 #12 0x0000562a97c6bb38 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /var/tmp/portage/kde-plasma/kwin-5.26.5/work/kwin-5.26.5/src/main_wayland.cpp:609
*** This bug has been marked as a duplicate of bug 463385 ***