SUMMARY Sometime xwayland apps lead to a kwin_plasmashell crash. If I use only wayland-native apps no crashes are encountered. STEPS TO REPRODUCE 1. Open any xwayland app (tested onlyoffice and pycharm community edition) 2. Do stuff normally 3. OBSERVED RESULT The application crashes together with kwin_plasmashell and all open applications EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS with alhp "v3" repositories turned on: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Backtrace: #0 0x0000754622e1888c in ??? () at /usr/lib/libQt6Core.so.6 #1 0x0000754622e047a5 in QtPrivate::compareStrings(QStringView, QStringView, Qt::CaseSensitivity) () at /usr/lib/libQt6Core.so.6 #2 0x00007545f75d59da in MapProxySource::item(int) const () at /usr/lib/libQuickCharts.so.1 #3 0x00007545f75c3396 in ??? () at /usr/lib/libQuickCharts.so.1 #4 0x00007545f75c513b in BarChart::onDataChanged() () at /usr/lib/libQuickCharts.so.1 #5 0x0000754622d97679 in ??? () at /usr/lib/libQt6Core.so.6 #6 0x0000754622d97679 in ??? () at /usr/lib/libQt6Core.so.6 #7 0x0000754622d97679 in ??? () at /usr/lib/libQt6Core.so.6 #8 0x0000754622f2e490 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QList<int> const&) () at /usr/lib/libQt6Core.so.6 #9 0x0000754616b17f85 in KSysGuard::SensorDataModel::onValueChanged(QString const&, QVariant const&) () at /usr/lib/libKSysGuardSensors.so.2 #10 0x0000754622d97679 in ??? () at /usr/lib/libQt6Core.so.6 #11 0x0000754616b30a64 in ??? () at /usr/lib/libKSysGuardSensors.so.2 #12 0x0000754622d97679 in ??? () at /usr/lib/libQt6Core.so.6 #13 0x0000754616af45d7 in OrgKdeKsystemstats1Interface::newSensorData(QList<KSysGuard::SensorData>) () at /usr/lib/libKSysGuardSystemStats.so.2 #14 0x0000754616af8481 in ??? () at /usr/lib/libKSysGuardSystemStats.so.2 #15 0x0000754616afbf33 in OrgKdeKsystemstats1Interface::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libKSysGuardSystemStats.so.2 #16 0x0000754623bb108f in ??? () at /usr/lib/libQt6DBus.so.6 #17 0x0000754622d88454 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6 #18 0x0000754624cfbfcb in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #19 0x0000754622d3db38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #20 0x0000754622d3dec4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #21 0x0000754622f86154 in ??? () at /usr/lib/libQt6Core.so.6 #22 0x0000754621874199 in ??? () at /usr/lib/libglib-2.0.so.0 #23 0x00007546218d33bf in ??? () at /usr/lib/libglib-2.0.so.0 #24 0x0000754621873712 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #25 0x0000754622f83e64 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #26 0x0000754622d45cce in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt6Core.so.6 #27 0x0000754622d41738 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #28 0x000060c186e2f24b in ??? () #29 0x0000754622643cd0 in ??? () at /usr/lib/libc.so.6 #30 0x0000754622643d8a in __libc_start_main () at /usr/lib/libc.so.6 #31 0x000060c186e2fa55 in ??? ()
The backtrace indicates that it's crashing in system stats code and has likely nothing to do with XWayland window. Unfortunately it's missing debug symbols, so it's not clear what exactly is happening. Can you please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports to get a backtrace with debug symbols?
Thank you for taking time to get through my report. Sadly that's the only output I get when invoking "coredumpctl gdb [paste the number]". Instead, gdb provides the following warning "Unable to find libthread_db matching inferior's thread library, thread debugging will not be available." In any case, my hardware diagnostic tool started to fail CPU stress tests, so I'm scared that the sudden plasma hangs and reboots I experience are not software-related. If you agree, I would suggest to flag the Bug as "Resolved - not a bug". I'll keep you informed about the issue.