https://bugs.kde.org/show_bug.cgi?id=420039
--- Comment #6 from Mircea Kitsune <sonichedgehog_hyperblas...@yahoo.com> --- Created attachment 127542 --> https://bugs.kde.org/attachment.cgi?id=127542&action=edit dbus-run-session startplasma-wayland --xwayland --x11-display $DISPLAY --exit-with-session=/usr/lib64/libexec/startplasma-waylandsession Thanks again Fabian Vogt from the openSUSE tracker for the new suggestions. Sharing the tests and results here too once more. Regarding whether this affects just Wayland or X11 clients: I don't know how to check which is which. However the issue does affect both Qt and GTK applications, KDE components or otherwise; So far I've seen it happen to KWrite, Konsole, KSysGuard, Firefox, Thunderbird, Audacious, etc. Since the first are default KDE components I'm assuming they're ran as native WL clients? In a console I set "export WAYLAND_DEBUG=1" followed by repeatedly launching and closing "kwrite". When eventually it opened with a hidden window, nothing was printed to this console. I killed the process and it only said "Terminated". I took a backup of ~/.config/plasma-org.kde.plasma.desktop-appletsrc to save my widget config, then successfully managed to use "dbus-run-session startplasma-wayland --xwayland --x11-display $DISPLAY --exit-with-session=/usr/lib64/libexec/startplasma-waylandsession" and start another session in a smaller window from within my normal session... I also set "export WAYLAND_DEBUG=1" in the console that spawned this debug session. I could reproduce the crash in this controlled environment too! Here's the output that was produced in the console running the nested session as that session collapsed. -- You are receiving this mail because: You are watching all bug changes.
