Created attachment 188653 [details] Contains plasmashell logs On KDE Neon, clicking an launcher icon on the Task Manager multiple times in rapid succession causes the plasmashell process to crash. The wallpaper turns black, the panel disappears, and then restarts after a few seconds. Steps to reproduce: 1. Open launcher application. 2. Click its icon on the Task Manager very quickly 5-10 times. 3. Observe the shell crash. Actual Results: Plasmashell crashes with Signal 6 (ABRT) in libtaskmanagerplugin.so. Expected Results: The shell should handle rapid clicks gracefully without crashing. Additional Information: I've attached a coredump trace. The crash seems to be triggered by a qt_assert in libtaskmanagerplugin.so. System Information: KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Graphics Platform: Wayland
I’ll also add that it occurs during normal use as well.
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #10 0x000072405707ab3d n/a (libtaskmanagerplugin.so + 0xbb3d) #11 0x00007240570854d2 n/a (libtaskmanagerplugin.so + 0x164d2) 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!
I am unfortunately unable to provide a full backtrace with debug symbols at the moment. I have encountered significant dependency issues while trying to install -dbgsym packages on KDE Neon (Noble), due to version mismatches between the current Neon repositories and the base Ubuntu debug repos. However, I have found a very important lead: The crash only occurs in the Wayland session. > When I switch to the X11 session, everything works perfectly fine and the Task Manager does not crash upon clicking. This suggests the issue might be related to Wayland's handling of window popups, shell surfaces, or a specific interaction with the graphics driver under Wayland.