Bug 493286

Summary:	host plasmashell repeatedly crashes when trying to launch a nested plasma session from within kde neon distrobox
Product:	[Plasma] plasmashell	Reporter:	renner0
Component:	generic-crash	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	nate
Priority:	NOR
Version First Reported In:	6.1.4
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	relevant shell history dr konqi output dolphin coredump for good measure

Description renner0 2024-09-17 18:00:57 UTC

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

Comment 1 renner0 2024-09-17 18:07:46 UTC

Created attachment 173785 [details]
dr konqi output

Comment 2 renner0 2024-09-17 18:14:30 UTC

link to plasmashell coredump because bigger than 4MB

https://0x0.st/X3SK.zst

Comment 3 renner0 2024-09-17 18:18:14 UTC

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)

Comment 4 renner0 2024-09-17 18:19:33 UTC

Created attachment 173787 [details]
dolphin coredump for good measure

Comment 5 renner0 2024-09-17 18:24:21 UTC

vm coredump link https://0x0.st/X3SN.zst

Comment 6 renner0 2024-09-17 18:26:48 UTC

Oh btw how could I undo my fuckery?

Comment 7 renner0 2024-09-17 18:50:47 UTC

funnily enough the nested session in the kde-neon distrobox still works

Comment 8 renner0 2024-09-17 19:13:54 UTC

Solution/How to make it work again:

rm -r ~/.cache/plasmashell

It was that simple lol

Comment 9 Nate Graham 2024-09-17 20:25:21 UTC

...So now it works with no crashes? If so, this is probably Bug 418148.

Comment 10 renner0 2024-09-18 14:47:23 UTC

(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?

Comment 11 Nate Graham 2024-09-18 15:04:53 UTC


*** This bug has been marked as a duplicate of bug 418148 ***