Bug 489369

Summary: Crash after extended screen off
Product: [Plasma] plasmashell Reporter: jaxad0127
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: duha.bugs
Priority: NOR Keywords: drkonqi
Version: 6.1.1   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: New crash information added by DrKonqi

Description jaxad0127 2024-06-28 12:18:36 UTC
Application: plasmashell (6.1.1)

Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.6-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.1.1 [CoredumpBackend]

-- Information about the crash:
I had the computer running overnight with the screen off (Powerdevil method). Woke it up and crash.

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  QtWaylandClient::QWaylandWindow::waylandScreen (this=0x56067856f840) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:956
#6  QtWaylandClient::QWaylandWindow::devicePixelRatio (this=0x56067856f840) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:1519
#7  0x000072ac05dcdf0c in QtWaylandClient::QWaylandEglWindow::updateSurface (this=0x56067856f840, create=true) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandeglwindow.cpp:70
#8  0x000072ac05dce905 in QtWaylandClient::QWaylandGLContext::makeCurrent (this=this@entry=0x72ab30002210, surface=<optimized out>) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:318
#9  0x000072ac0d0adc28 in QOpenGLContext::makeCurrent (this=0x72ab30001f60, surface=0x560678591b60) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qopenglcontext.cpp:664


Reported using DrKonqi
Comment 1 jaxad0127 2024-06-28 12:18:37 UTC
Created attachment 171127 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 duha.bugs 2024-06-28 18:57:06 UTC

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