Bug 496323

Summary: Plasmashell crash on suspend
Product: [Plasma] plasmashell Reporter: Carson <kde.glance851>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: nate
Priority: NOR Keywords: drkonqi
Version: 6.2.3   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/93959/events/249e026fe61a42acb02bf70fa1628d4d/
Attachments: New crash information added by DrKonqi

Description Carson 2024-11-15 22:33:03 UTC
Application: plasmashell (6.2.3)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.0
Frameworks Version: 6.8.0
Operating System: Linux 6.8.5-301.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 41 (Sway)"
DrKonqi: 6.2.3 [CoredumpBackend]

-- Information about the crash:
- I had Firefox, VSCode, and Konsole open
- OS: Fedora Sway 41
- GPU: Dual AMD Cards -- 6800 and 6600 XT
- Plasmashell 6.2.3

I just went away from my machine for a while, and the screens went dark. I assume it suspended. A few minutes later (maybe 15?) the fans spun down and it seemed like it either turned off or hibernated. When I wiggled the mouse or pressed the keys of the keyboard, it did not resume. I pressed the power button once, and it seemed to resume at the SDDM (notably, it did not do a full boot). I logged in as normal and it worked fine. In other words, I didn't really notice anything was wrong, except that it didn't resume from keyboard/mouse input. 

I installed the KDE DE with `sudo dnf group install kde-desktop-env --skip-broken`. The --skip-broken was because of a conflict between the Sway SDDM version and the KDE SDDM version. Since this happened on suspend, I suspect that this might have had something to do with it. Another clue to this is that it seems KDE knows I'm using SDDM, but the settings panel doesn't seem to be able to change the settings like the theme for example. It does, however, show what I am listening to on the lock screen, so something is a little funky there.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  QWindow::screen (this=<optimized out>) at /usr/src/debug/qt6-qtbase-6.8.0-4.fc41.x86_64/src/gui/kernel/qwindow.cpp:2200
#6  0x00007fa81bd2db75 in QPlatformWindow::screen (this=this@entry=0x556aef106ab0) at /usr/src/debug/qt6-qtbase-6.8.0-4.fc41.x86_64/src/gui/kernel/qplatformwindow.cpp:70
#7  0x00007fa81ccc1e69 in QtWaylandClient::QWaylandWindow::calculateScreenFromSurfaceEvents (this=this@entry=0x556aef106aa0) at /usr/src/debug/qt6-qtwayland-6.8.0-2.fc41.x86_64/src/client/qwaylandwindow.cpp:554
#8  0x00007fa81ccc6b0a in QtWaylandClient::QWaylandWindow::handleScreensChanged (this=0x556aef106aa0) at /usr/src/debug/qt6-qtwayland-6.8.0-2.fc41.x86_64/src/client/qwaylandwindow.cpp:1439
#9  0x00007fa81b55bac1 in QtPrivate::QSlotObjectBase::call (this=0x556aeed27c20, r=<optimized out>, a=0x7ffd2e2deba8) at /usr/src/debug/qt6-qtbase-6.8.0-4.fc41.x86_64/src/corelib/kernel/qobjectdefs_impl.h:486


Reported using DrKonqi
Comment 1 Carson 2024-11-15 22:33:05 UTC
Created attachment 175855 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-11-19 19:25:09 UTC

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