Bug 501502

Summary: Plasmashell crashed after monitor setup change
Product: [Plasma] plasmashell Reporter: Jerzy Kołosowski <kde>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: nate
Priority: NOR Keywords: drkonqi
Version First Reported In: 6.3.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Jerzy Kołosowski 2025-03-14 18:30:13 UTC 
Application: plasmashell (6.3.3)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.12.10-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.3.3 [CoredumpBackend]

-- Information about the crash:
Plasmashell crashed after monitor setup change, for example plugging new monitor.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::get (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/tools/qscopedpointer.h:110
[...]
#8  QWindow::screen (this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qwindow.cpp:2199
#9  0x00007d64266191ac in QPlatformWindow::screen (this=this@entry=0x589e44c83610) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qplatformwindow.cpp:70
#10 0x00007d6426dc086a in QtWaylandClient::QWaylandWindow::calculateScreenFromSurfaceEvents (this=0x589e44c83600) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:554
#11 0x00007d6426dcd49a in QtWaylandClient::QWaylandWindow::handleScreensChanged (this=0x589e44c83600) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:1446


Reported using DrKonqi
Comment 1 Jerzy Kołosowski 2025-03-14 18:30:15 UTC 
Created attachment 179396 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2025-03-17 17:44:35 UTC 

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