Created attachment 173784 [details] relevant shell history SUMMARY STEPS TO REPRODUCE 1. podman pull invent-registry.kde.org/neon/docker-images/plasma:unstable 2. distrobox-create -n kde-neon --image invent-registry.kde.org/neon/docker-images/plasma:unstable 3. distrobox upgrade kde-neon 4. distrobox-enter kde-neon 5. chown -f -R $USER:$USER /tmp/.X11-unix 6. execute PlasmaNested.sh from within the container 7. reboot/crash plasma OBSERVED RESULT at first everything works as expected and you get a kde neon nested wayland session after that I closed the nested session and accidentally opened ~700 folders (CTRL+A, Right Click open) at once in dolphin which caused plasmashell to crash and dropped me into a black screen with a one line of "@" symbols I pressed CTRL+C to exit it and I switched to another tty to kill my user session, I restarted sddm logged into my user and I am immediately greeted with 3 dr konqi crash windows on login. A reboot did not fix anything Another user is not affected I can still launch programs with Shortcuts restarting plasmashell with systemctl --user restart plasma-plasmashell.service results in a crash EXPECTED RESULT plasma recovers in a usable state plasma does not crash SOFTWARE/OS VERSIONS Operating System: Bazzite 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.9.12-205.fsync.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION link to davided nested script https://gist.github.com/davidedmundson/8e1732b2c8b539fd3e6ab41a65bcab74 how to run latest plasma from distrobox https://distrobox.it/posts/run_latest_gnome_kde_on_distrobox/#running-latest-plasma kde neon container stuff https://community.kde.org/Neon/Containers
Created attachment 173785 [details] dr konqi output
link to plasmashell coredump because bigger than 4MB https://0x0.st/X3SK.zst
I did the similiar things on a Fedora Kinoite virtual machine and after a reboot plasmashell also is broken (no wallpaper, panel, 3 crash windows, reboot did not help)
Created attachment 173787 [details] dolphin coredump for good measure
vm coredump link https://0x0.st/X3SN.zst
Oh btw how could I undo my fuckery?
funnily enough the nested session in the kde-neon distrobox still works
Solution/How to make it work again: rm -r ~/.cache/plasmashell It was that simple lol
...So now it works with no crashes? If so, this is probably Bug 418148.
(In reply to Nate Graham from comment #9) > ...So now it works with no crashes? If so, this is probably Bug 418148. Yes, once you nuke the plasmashell cache after launching the PlasmaNested.sh it no longer crashes until you launch the script again. It does not affect the currently running session at all until the next session is started by a new login or restarting plasmashell via systemd or just plasmashell It might show 3 Crash windows because of # StartLimitBurst=3 in the systemd file of plasma-plasmashell.service Should we mention somewhere on this page: https://community.kde.org/Neon/Containers that you should not launch nested sessions from a distrobox unless you absolutely know what you are doing (which I am not) If so, then I could update the page. Is this a plasma version/cache mismatch or some dbus(?) shenanigans? Or is there a better way to test latest Plasma/KDE-neon without dual-boot/another session from sddm (VMs suck for my testing purposes). Running the container as another user entirely?
*** This bug has been marked as a duplicate of bug 418148 ***