SUMMARY plasma-discover crashed a moment after it starts STEPS TO REPRODUCE 1. run `plasma-discover` in Konsole 2. see discover's window 3. crash OBSERVED RESULT Discover crashed EXPECTED RESULT running normally SOFTWARE/OS VERSIONS Windows: / macOS: / Linux/KDE Plasma: Kubuntu 22.04, plasma 5.23.3 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION LANG: zh-cn UTF8 console: ``` QObject::startTimer: Timers cannot have negative intervals kf.kio.core: Malformed JSON protocol file for protocol: "trash" , number of the ExtraNames fields should match the number of ExtraTypes fields adding empty sources model QStandardItemModel(0x5616f86693f0) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" org.kde.plasma.libdiscover: the following categories seem to be the same but they're not entirely "applications-games-strategy" "applications-games" -- "模拟" "模拟" -- QVector(QPair(1,"Simulation")) QVector(QPair(1,"Emulator")) -- false false file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:261:18: QML QQuickItem*: Binding loop detected for property "implicitWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/RefreshableScrollView.qml:175:13: QML Binding: Not restoring previous value because restoreMode has not been set. This behavior is deprecated. You have to import QtQml 2.15 after any QtQuick imports and set the restoreMode of the binding to fix this warning. In Qt < 6.0 the default is Binding.RestoreBinding. In Qt >= 6.0 the default is Binding.RestoreBindingOrValue. ** flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) Bail out! flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 133016 KCrash: Arguments: /usr/bin/plasma-discover amdgpu: amdgpu_cs_query_reset_state failed. (-9) QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 28 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... QSocketNotifier: Invalid socket 43 and type 'Read', disabling... QSocketNotifier: Invalid socket 45 and type 'Read', disabling... QSocketNotifier: Invalid socket 46 and type 'Read', disabling... QSocketNotifier: Invalid socket 42 and type 'Read', disabling... QSocketNotifier: Invalid socket 48 and type 'Read', disabling... QSocketNotifier: Invalid socket 50 and type 'Read', disabling... QSocketNotifier: Invalid socket 47 and type 'Read', disabling... amdgpu: amdgpu_cs_query_reset_state failed. (-9) QSocketNotifier: Invalid socket 51 and type 'Read', disabling... amdgpu: amdgpu_cs_query_reset_state failed. (-9) QSocketNotifier: Invalid socket 52 and type 'Read', disabling... QSocketNotifier: Invalid socket 53 and type 'Read', disabling... QSocketNotifier: Invalid socket 54 and type 'Read', disabling... QSocketNotifier: Invalid socket 55 and type 'Read', disabling... QSocketNotifier: Invalid socket 56 and type 'Read', disabling... amdgpu: amdgpu_cs_query_reset_state failed. (-9) The X11 connection broke (error 1). Did the X11 server die? KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi QSocketNotifier: Invalid socket 104 and type 'Read', disabling... QSocketNotifier: Invalid socket 94 and type 'Read', disabling... QSocketNotifier: Invalid socket 44 and type 'Read', disabling... QSocketNotifier: Invalid socket 73 and type 'Read', disabling... QSocketNotifier: Invalid socket 101 and type 'Read', disabling... ```
Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
(In reply to Nate Graham from comment #1) > Can you attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports DrKonqi says the debugger exited unexpectedly and cannot generate a backtrace. However, this problem only occurred a few times and after a restart it's running normally
OK, if it happens again let's re-open, hopefully with a backtrace. :)