SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Variably, though It usually happens the most in panel/desktop editing mode (right click on the panel, choose enter edit mode). 2. Add multiple addons (plasmoids) very quickly, then right-click and choose remove that plasmoids for all of them. 3. Several popups will show up, click to "x" to close all the popups. OBSERVED RESULT Plasmashell either freezes or crashes most of the times. EXPECTED RESULT The widgets/plasmoid remove completely popups should be closed, or the widgets should be added to the desktop SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS (KDE components from Arch repositories) / KDE Plasma 5.27.5. Kernel version: Linux 6.1.30-1-lts (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 (built against 5.15.9) ADDITIONAL INFORMATION Backtrace logs (first one I get from the coredump after it crashed), second time I tried to reproduce the bug by this guide through gdb: https://wiki.archlinux.org/title/Debugging/Getting_traces#Getting_the_trace , and it freezes when I adding new plasmoids after removing multiple of them (I used privatebin, it only save the logs for one month, so I tried paste.debian.net instead): https://paste.debian.net/1281529/ https://paste.debian.net/1281530/ Window manager theme: Breeze (revert from another theme to test another bug in my system), Application theme: Plasma, GTK application theme: Adwaita Dark Compositor: KWin (Wayland) Icons: Papirus-Light Login manager: SDDM Startup services: Account, GNOME/GTK Settings Synchronization Service, Keyboard Daemon, Kmix Daemon, KSysguard, Network Proxy, Network Status, Plasma Network Management Module, Print Manager, SMB Watcher, Status Notifer Manager, Timezone, Touchpad
Can intermittently reproduce with those steps. It's not 100% though.
*** This bug has been marked as a duplicate of bug 468180 ***