*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open System Monitor 2. Select "Applications" from the sidebar 3. Select an application OBSERVED RESULT System Monitor will crash EXPECTED RESULT Just selecting the application clicked on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION
I have to add that it seems more stable (no crashes) on Wayland. X11 still crashing.
We will need a backtrace to be able to figure out what's going on.
(In reply to Arjen Hiemstra from comment #2) > We will need a backtrace to be able to figure out what's going on. I'd like to make it but I haven't done one before. I've seen the HowTo page but I'm not sure which part I've to do because I can't clearly understand what I should do using KDE Neon. If you could help me on this I'll be more than help to send the backtrace. Thanks in advance.
Here the backtrace with GDB (modified just the username and name of the pc) ------- USERNAME@NAME_PC:~$ gdb plasma-systemmonitor GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1 Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from plasma-systemmonitor... This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.ubuntu.com Enable debuginfod for this session? (y or [n]) y Debuginfod has been enabled. To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit. (No debugging symbols found in plasma-systemmonitor) (gdb) run Starting program: /usr/bin/plasma-systemmonitor [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". QML debugging is enabled. Only use this in a safe environment. [New Thread 0x7ffff17ff640 (LWP 5642)] [New Thread 0x7ffff0ffe640 (LWP 5643)] [New Thread 0x7fffe0fba640 (LWP 5644)] kf.config.core: KConfigIni: In file /home/username/.local/share/plasma-systemmonitor/temperature.page, line 30: Invalid escape sequence: «\+» [New Thread 0x7fffd9303640 (LWP 5646)] [New Thread 0x7fffd8b02640 (LWP 5647)] [New Thread 0x7fffd3fff640 (LWP 5648)] [New Thread 0x7fffd37fe640 (LWP 5649)] [New Thread 0x7fffd2ffd640 (LWP 5651)] [New Thread 0x7fffd1cfb640 (LWP 5660)] qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=history.page:223:9: QML Loader: Binding loop detected for property "height" file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" [Detaching after vfork from child process 5667] file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" [New Thread 0x7fffd08b5640 (LWP 5669)] [New Thread 0x7fffb7fff640 (LWP 5670)] [New Thread 0x7fffb77fe640 (LWP 5671)] [New Thread 0x7fffb6ffd640 (LWP 5672)] [New Thread 0x7fffb67fc640 (LWP 5673)] [New Thread 0x7fffb5ffb640 (LWP 5674)] [New Thread 0x7fffb57fa640 (LWP 5675)] [New Thread 0x7fffb4ff9640 (LWP 5676)] [New Thread 0x7fff97fff640 (LWP 5677)] [New Thread 0x7fff977fe640 (LWP 5678)] qrc:/qt/qml/org/kde/ksysguard/page/EditablePage.qml?page=overview.page:223:9: QML Loader: Binding loop detected for property "height" file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" Thread 9 "QSGRenderThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd2ffd640 (LWP 5651)] 0x00007ffff60614ee in QSortFilterProxyModel::sibling(int, int, QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt6Core.so.6 (gdb) bt #0 0x00007ffff60614ee in QSortFilterProxyModel::sibling(int, int, QModelIndex const&) const () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #1 0x00007fffdb0541df in ?? () from /usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #2 0x00007fffebcbbb45 in QSGDefaultPainterNode::paint() () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #3 0x00007fffebcbc048 in QSGDefaultPainterNode::update() () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #4 0x00007fffebd2bc00 in QQuickPaintedItem::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #5 0x00007fffebd99ac7 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #6 0x00007fffebd9a094 in QQuickWindowPrivate::updateDirtyNodes() () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #7 0x00007fffebd8f99e in QQuickWindowPrivate::syncSceneGraph() () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #8 0x00007fffebbbb865 in ?? () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #9 0x00007ffff6183c9d in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #10 0x00007ffff5694ac3 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 #11 0x00007ffff5726850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 (gdb) quit A debugging session is active. Inferior 1 [process 5639] will be killed. Quit anyway? (y or n) y -------- Is it the kind of backtrace you need? I hope it helps. Thanks in advance.
Yeah, this looks like it's a duplicate of 482169 that is fixed with Qt 6.7.1. *** This bug has been marked as a duplicate of bug 482169 ***