Bug 495776 - Repeated interactions with music player plasmoid leads to crash
Summary: Repeated interactions with music player plasmoid leads to crash
Status: RESOLVED DUPLICATE of bug 480800
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.2.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-11-04 04:33 UTC by Aidan Coombs
Modified: 2024-11-04 19:12 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (93.59 KB, text/plain)
2024-11-04 04:33 UTC, Aidan Coombs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aidan Coombs 2024-11-04 04:33:15 UTC
Application: plasmashell (6.2.2)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.0
Frameworks Version: 6.7.0
Operating System: Linux 6.11.6-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.2.2 [CoredumpBackend]

-- Information about the crash:
When using the music player widget (which I had placed in my taskbar) to control the Spotify Linux client, repeated interactions with it lead to plasmashell crashing and restarting. 

Specifically, I was pressing the 'next track' button and seeking to random points in the track using my mouse 3-4 times per second, consistently for ~30 seconds, before the crash occurred. To reproduce, you might need to try for longer than that - it's a bit tricky to trigger but definitely possible.

This manifested the first 2 times as a crash followed by a restart of the desktop and the DrKonqi client appearing, and the third time as a freeze (the music player pop-up was desaturated by the 'Desaturate Unresponsive Appliactions' desktop effect). 

Using Plasma on Wayland, driver nvidia-open-dkms 565.57.01

Would appreciate any support you can offer :)

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  0x0000709d58c27423 in send_explicit_sync_points (display=0x5bbedc7793c0, surface=0x5bbedff376b0, image=0x0) at ../egl-wayland/src/wayland-eglsurface.c:205
#6  wlEglSendDamageEvent (surface=surface@entry=0x5bbedff376b0, queue=0x5bbedff37940) at ../egl-wayland/src/wayland-eglsurface.c:279
#7  0x0000709d58c2cba4 in wlEglSwapBuffersWithDamageHook (eglDisplay=<optimized out>, eglSurface=<optimized out>, rects=<optimized out>, n_rects=<optimized out>) at ../egl-wayland/src/wayland-eglswap.c:150
[...]
#10 0x0000709d5913e2ce in QtWaylandClient::QWaylandGLContext::swapBuffers (this=0x5bbedfd737f0, surface=<optimized out>) at /usr/src/debug/qt6-wayland/qtwayland/src/hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:374
#11 0x0000709d6010b67d in QRhiGles2::endFrame (this=0x5bbedfd82580, swapChain=0x5bbee013c710, flags=...) at /usr/src/debug/qt6-base/qtbase/src/gui/rhi/qrhigles2.cpp:2166


Reported using DrKonqi
Comment 1 Aidan Coombs 2024-11-04 04:33:17 UTC
Created attachment 175503 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Nate Graham 2024-11-04 19:12:17 UTC
It's an NVIDIA GPU driver bug, unfortunately.

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