Bug 495660

Summary:	Plasmashell crash when interacting with widgets in the panel or adjusting volume
Product:	[Plasma] plasmashell	Reporter:	tsweet64
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	kdedev, nate
Priority:	NOR	Keywords:	drkonqi
Version:	6.2.2
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 tsweet64 2024-10-31 22:47:10 UTC

Application: plasmashell (6.2.2)

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

-- Information about the crash:
This is mostly the same symptoms and triggers as https://bugs.kde.org/show_bug.cgi?id=493854 , but as that bug was marked as resolved upstream, i'm reporting a new bug with the current backtrace in case it is unrelated.

The crash happens 100% of the time upon adjusting volume or brightness (even with keyboard buttons), using the application launcher, clicking on menus on applets (e.g., removable devices), or opening apps with the panel. The crash occurs when the corresponding UI element (e.g., the volume bar or the application launcher) tries to disappear

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x0000707f3d6a5463 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x0000707f3d64c120 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x0000707f3d6334c3 in __GI_abort () at abort.c:79
#9  0x0000707f407da734 in wl_abort (fmt=fmt@entry=0x707f407df7f0 "Tried to add event to destroyed queue\n") at ../wayland-1.23.1/src/wayland-util.c:476


Reported using DrKonqi

Comment 1 tsweet64 2024-10-31 22:47:13 UTC

Created attachment 175425 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 TraceyC 2024-11-01 13:28:53 UTC

Searchable backtrace

Thread 1 (Thread 0x707f35a006c0 (LWP 2612)):
[KCrash Handler]
#5  __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#6  0x0000707f3d6a5463 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78
#7  0x0000707f3d64c120 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#8  0x0000707f3d6334c3 in __GI_abort () at abort.c:79
#9  0x0000707f407da734 in wl_abort (fmt=fmt@entry=0x707f407df7f0 "Tried to add event to destroyed queue\n") at ../wayland-1.23.1/src/wayland-util.c:476
#10 0x0000707f407dcd86 in queue_event (display=<optimized out>, len=8) at ../wayland-1.23.1/src/wayland-client.c:1617
#11 read_events (display=0x601d6dc68ce0) at ../wayland-1.23.1/src/wayland-client.c:1713
#12 wl_display_read_events (display=0x601d6dc68ce0) at ../wayland-1.23.1/src/wayland-client.c:1796
#13 0x0000707f3ed6e431 in QtWaylandClient::EventThread::run (this=0x601d6dd736f0) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylanddisplay.cpp:191
#14 0x0000707f3ded840f in operator() (__closure=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:335
#15 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:263
#16 QThreadPrivate::start (arg=0x601d6dd736f0) at /usr/src/debug/qt6-base/qtbase/src/corelib/thread/qthread_unix.cpp:294
#17 0x0000707f3d6a339d in start_thread (arg=<optimized out>) at pthread_create.c:447
#18 0x0000707f3d72849c in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

Comment 3 TraceyC 2024-11-01 13:35:12 UTC

This is definitely a different backtrace. It may be in Wayland and the nVidia drivers. I'll let one of the more experienced contributors take a closer look.

Comment 4 Nate Graham 2024-11-01 14:44:54 UTC

This one is Bug 482754.

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