Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: I just clear the clipboard as usual. The same crash happens here and there. I don't know why. The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x00007fe3ef324639 in KWayland::Client::PlasmaWindow::requestActivate() () at /lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #7 0x000055729ed584da in ShellCorona::restorePreviousWindow() (this=0x5572a033e080) at ./shell/shellcorona.cpp:1229 #8 ShellCorona::restorePreviousWindow() (this=0x5572a033e080) at ./shell/shellcorona.cpp:1217 #9 0x000055729ed4645c in PanelView::refreshStatus(Plasma::Types::ItemStatus) (this=0x5572a19d2e70, status=<optimized out>) at ./shell/panelview.cpp:1429 #10 0x00007fe3eccf48f4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffdd7818ce0, r=0x5572a19d2e70, this=0x5572a1c545e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 The reporter indicates this bug may be a duplicate of or related to bug 473204. Reported using DrKonqi
Created attachment 160904 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
*** This bug has been marked as a duplicate of bug 473054 ***
Created attachment 161224 [details] New crash information added by DrKonqi plasmashell (5.27.7) using Qt 5.15.10 is there a point in sending a backtrace when it crashes and it's already reported? -- Backtrace (Reduced): #6 0x00007f6ffd517639 in KWayland::Client::PlasmaWindow::requestActivate() () at /lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #7 0x000055e66540b4da in ShellCorona::restorePreviousWindow() (this=0x55e666c0b670) at ./shell/shellcorona.cpp:1229 #8 ShellCorona::restorePreviousWindow() (this=0x55e666c0b670) at ./shell/shellcorona.cpp:1217 #9 0x000055e6653f945c in PanelView::refreshStatus(Plasma::Types::ItemStatus) (this=0x55e668905920, status=<optimized out>) at ./shell/panelview.cpp:1429 #10 0x00007f6ffaef48f4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffce3ed2070, r=0x55e668905920, this=0x55e66890f980) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
(In reply to aronkvh from comment #3) > is there a point in sending a backtrace when it crashes and it's already > reported? Not in a bug marked as a duplicate of another one, no. If you have a backtrace that's better than the one in the original report (e.g. because it contains debug symbols) then it can make sense to add there. Otherwise no.