Bug 500653 - Plasmashell crash when enabling and disabling 3rd monitor
Summary: Plasmashell crash when enabling and disabling 3rd monitor
Status: RESOLVED DUPLICATE of bug 499383
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.3.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-02-24 06:55 UTC by XandonVincent
Modified: 2025-02-24 09:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/114947/events/288996b7193546bf90e1d916a0d24d45/


Attachments
New crash information added by DrKonqi (102.95 KB, text/plain)
2025-02-24 06:55 UTC, XandonVincent
Details

Note You need to log in before you can comment on or make changes to this bug.
Description XandonVincent 2025-02-24 06:55:21 UTC
Application: plasmashell (6.3.0)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.10.0
Operating System: Linux 6.12.11-200.fc41.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 41 (Forty One)"
DrKonqi: 6.3.0 [CoredumpBackend]

-- Information about the crash:
Plasma shell seems to crash and wish for me to file a crash report every time I make changes that enable/disable my 3rd monitor, which is a 4k roku TV. I'm not always using this TV as a monitor and thus I enable and disable it often, and every time Plasma Shell reports that it crashed, but it immediately recovers and I don't experience any obvious negative effects other than the crash report window appearing. If it has any larger effects on my system I have yet to notice them and have had this happen several times. I suspect it's not unreasonable to believe this could have something to do with the fact I use an NVidia RTX 2080 TI as my graphics card. 

Full PC specs for referrence:
MOBO: X570 AORUS MASTER
CPU: AMD RyZEN 9 5950X
GPU: NVIDIA RTX 2080TI
MEMORY: 32GB DDR4 

I hope this helps.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  QWindow::screen (this=<optimized out>) at /usr/src/debug/qt6-qtbase-6.8.2-2.fc41.x86_64/src/gui/kernel/qwindow.cpp:2200
#6  0x00007fa16492e775 in QPlatformWindow::screen (this=this@entry=0x562a84576d60) at /usr/src/debug/qt6-qtbase-6.8.2-2.fc41.x86_64/src/gui/kernel/qplatformwindow.cpp:70
#7  0x00007fa16593c259 in QtWaylandClient::QWaylandWindow::calculateScreenFromSurfaceEvents (this=this@entry=0x562a84576d50) at /usr/src/debug/qt6-qtwayland-6.8.2-1.fc41.x86_64/src/client/qwaylandwindow.cpp:554
#8  0x00007fa165940f8a in QtWaylandClient::QWaylandWindow::handleScreensChanged (this=0x562a84576d50) at /usr/src/debug/qt6-qtwayland-6.8.2-1.fc41.x86_64/src/client/qwaylandwindow.cpp:1446
#9  0x00007fa16415a26e in QtPrivate::QSlotObjectBase::call (this=0x562a834e3ca0, r=<optimized out>, a=0x7ffea350d9c8) at /usr/src/debug/qt6-qtbase-6.8.2-2.fc41.x86_64/src/corelib/kernel/qobjectdefs_impl.h:486


Reported using DrKonqi
Comment 1 XandonVincent 2025-02-24 06:55:23 UTC
Created attachment 178790 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 cwo 2025-02-24 09:01:25 UTC
Thank you for the bug report! This issue is already being tracked; marking as a duplicate.

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