https://bugs.kde.org/show_bug.cgi?id=493286
--- Comment #10 from renne...@protonmail.com --- (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? -- You are receiving this mail because: You are watching all bug changes.
