Application: plasmashell (6.1.5) Qt Version: 6.7.3 Frameworks Version: 6.6.0 Operating System: Linux 6.11.2-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.1.5 [CoredumpBackend] -- Information about the crash: As said in the title, everytime I touch the taskbar, either use the start menu or sound/bluetooth etc controls are used (even when pressing the volume up/down key on the keyboard) will crash the plasma shell, it does recover most of the time and will be fin until interacted with again. Might be relevant to note it does work correctly up until it loses foucus and should go back to some idle state. This started after there was a problem with the nvidia driver update earlier this week, and I was forced to enable nvidia_drm.fbdev=1 on the kernel. That issue has been solved and I've since disabled that option on the kernel. As far as I've been able to gather the shell is trying to add an event to a destroyed display events queue, which leads into an assert and therefore a crash. 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 0x000077f0416a5463 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:78 #7 0x000077f04164c120 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x000077f0416334c3 in __GI_abort () at abort.c:79 #9 0x000077f04470b734 in wl_abort (fmt=fmt@entry=0x77f0447107f0 "Tried to add event to destroyed queue\n") at ../wayland-1.23.1/src/wayland-util.c:476 Reported using DrKonqi
Created attachment 174537 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Did you use the hidden settings to change Plasma to use Vulkan for rendering?
Hey Nicolas, no it should be using what ever default rendering API it ships with enabled
Correction, somehow it was using Vulkan, no idea why, I didn't change it. Changing it to OpenGL/Threaded corrected the issue.
(In reply to Cotrim from comment #4) > Correction, somehow it was using Vulkan, no idea why, I didn't change it. > > Changing it to OpenGL/Threaded corrected the issue. That would explain it, it's a known thing *** This bug has been marked as a duplicate of bug 482754 ***