Application: plasmashell (6.3.2) ApplicationNotResponding [ANR]: false Qt Version: 6.8.2 Frameworks Version: 6.11.0 Operating System: Linux 6.13.2 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.3.2 [CoredumpBackend] -- Information about the crash: plasma shell constantly crashed when interacted with and somtimes even when the volume change osds show up. i've updated my system and no updated fixed it. i deleted .config/plasma* (i cannot loose my kwin config bedcause i have hundreds of shortcuts and rules) and restarted plasmashell and it still crashed. it did not crash when logged in with a new test user. this behaviour also happenes with krunner 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 0x00007f8881ea56d3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89 #7 0x00007f8881e4bba0 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x00007f8881e33582 in __GI_abort () at abort.c:73 #9 0x00007f88852376cc in ??? () at /usr/lib/libwayland-client.so.0 Reported using DrKonqi
Created attachment 179727 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
Thank you for the bug report. Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: 9 0x00007f88852376cc in ??? () at /usr/lib/libwayland-client.so.0 #11 0x00007f88836d0721 in ??? () at /usr/lib/libQt6WaylandClient.so.6 #12 0x00007f88826f223b in ??? () at /usr/lib/libQt6Core.so.6 Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Created attachment 179866 [details] attachment-2511112-0.html Hello, the issue seems to have been gone after a recent kernel+driver update Kernel-6.14(compiled from source) Driver-nvidia proprietary 570.133.07 On Wed, Mar 26, 2025, 2:29 AM TraceyC <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=501987 > > TraceyC <kdedev@tlcnet.info> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |BACKTRACE > CC| |kdedev@tlcnet.info > Status|REPORTED |NEEDSINFO > > --- Comment #2 from TraceyC <kdedev@tlcnet.info> --- > Thank you for the bug report. Unfortunately the backtrace is incomplete and > missing debug symbols for the following lines that we need to figure out > exactly what's going wrong: > > 9 0x00007f88852376cc in ??? () at /usr/lib/libwayland-client.so.0 > #11 0x00007f88836d0721 in ??? () at /usr/lib/libQt6WaylandClient.so.6 > #12 0x00007f88826f223b in ??? () at /usr/lib/libQt6Core.so.6 > > Could you please install debug symbols and attach a new symbolicated > backtrace > generated by using `coredumpctl gdb` in a terminal window? See > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > for details about how to do this. Thanks again! > > -- > You are receiving this mail because: > You reported the bug.
That's great news. I'll close this out for now. If you get the same crash, feel free to re-open this report