Bug 478946 - Plasmashell can sometimes crash on a fast workspace switch
Summary: Plasmashell can sometimes crash on a fast workspace switch
Status: RESOLVED DUPLICATE of bug 443352
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.27.10
Platform: openSUSE Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-12-23 17:46 UTC by Dmitry Sharshakov
Modified: 2024-01-15 14:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
New crash information added by DrKonqi (92.78 KB, text/plain)
2023-12-23 17:47 UTC, Dmitry Sharshakov 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Sharshakov 2023-12-23 17:46:59 UTC 
Application: plasmashell (5.27.10)

Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.6.6-1-default x86_64
Windowing System: Wayland
Distribution: openSUSE Tumbleweed
DrKonqi: 5.27.10 [CoredumpBackend]

-- Information about the crash:
I scrolled and clicked the mouse wheel, that caused a short plasmashell crash

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x00007f4d16cfab2a in KIO::FileUndoManager::undo() () at /lib64/libKF5KIOWidgets.so.5
[...]
#7  0x00007f4d1879e8b2 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5
#8  0x00007f4d187a142f in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5
#9  0x00007f4d187a21e3 in QAction::qt_metacall(QMetaObject::Call, int, void**) () at /lib64/libQt5Widgets.so.5
[...]
#12 0x00007f4d18fc01db in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /lib64/libQt5Qml.so.5


Reported using DrKonqi
Comment 1 Dmitry Sharshakov 2023-12-23 17:47:00 UTC 
Created attachment 164406 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Akseli Lahtinen 2024-01-15 14:36:07 UTC 

*** This bug has been marked as a duplicate of bug 443352 ***