SUMMARY plasma-systemmonitor crashes every time you are switching "Display Styles" from either "Application Table" or "Process Table" to anything else. STEPS TO REPRODUCE 1. Open systemmonitor 2. Click "Edit Page" and select any chart on it 3. Under "Display Styles", pick either Application Table or Process Table (skip if it already was one of them) 4. Under the same chart, switch the Display Style again to something else eg. Bar Chart OBSERVED RESULT systemmonitor will crash every time EXPECTED RESULT it should switch away from it seamlessly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch 5.11.11 (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION
crash reports need a backtrace to be actionable
I'was actually about to include it, but I thought it was not very helpful. Nevertheless, here is what Dr. Konqi presents me. ----------------------- Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x00007f364735049d in ?? () from /usr/lib/libQt5QuickTemplates2.so.5 #5 0x00007f36473459cf in QQuickControlPrivate::updateImplicitContentWidth() () from /usr/lib/libQt5QuickTemplates2.so.5 #6 0x00007f3647350632 in ?? () from /usr/lib/libQt5QuickTemplates2.so.5 #7 0x00007f364766d915 in QQuickItemPrivate::implicitWidthChanged() () from /usr/lib/libQt5Quick.so.5 #8 0x00007f364767182b in QQuickItem::setImplicitSize(double, double) () from /usr/lib/libQt5Quick.so.5 #9 0x00007f364412773f in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #10 0x00007f3644129e0b in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #11 0x00007f36441268e4 in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #12 0x00007f3644129ddf in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #13 0x00007f3644131403 in ?? () from /usr/lib/qt/qml/QtQuick/Layouts/libqquicklayoutsplugin.so #14 0x00007f3650abdd3e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #15 0x00007f3650ac8be5 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #16 0x00007f363fa0bc67 in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #17 0x00007f3650abdd3e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #18 0x00007f3650ac8be5 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #19 0x00007f363fa0d800 in ?? () from /usr/lib/qt/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #20 0x00007f3650abdd3e in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #21 0x00007f3650ac8be5 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #22 0x00007f363c243867 in ?? () from /usr/lib/qt/qml/org/kde/ksysguard/faces/libFacesPlugin.so #23 0x00007f3650abff70 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #24 0x00007f36515e5762 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #25 0x00007f3650a936aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #26 0x00007f3650a961a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #27 0x00007f3650aecbe4 in ?? () from /usr/lib/libQt5Core.so.5 #28 0x00007f364f4e9f9c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0x00007f364f53da49 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0x00007f364f4e76f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0x00007f3650aec221 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #32 0x00007f3650a9200c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5 #33 0x00007f3650a9a4c4 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #34 0x000055cdac4ca2a4 in ?? () #35 0x00007f365045ab25 in __libc_start_main () from /usr/lib/libc.so.6 #36 0x000055cdac4ca77e in ?? () [Inferior 1 (process 136276) detached]
It reminds me of the DialogButtonBox crash https://bugs.kde.org/show_bug.cgi?id=435192
It's the same. *** This bug has been marked as a duplicate of bug 435192 ***