https://bugs.kde.org/show_bug.cgi?id=420039
--- Comment #13 from Mircea Kitsune <sonichedgehog_hyperblas...@yahoo.com> --- Created attachment 127563 --> https://bugs.kde.org/attachment.cgi?id=127563&action=edit dbus-run-session gdb --args startplasma-wayland --xwayland --x11-display $DISPLAY --exit-with-session=/usr/lib64/libexec/startplasma-waylandsession > ./output 2>&1 Here's the output of the gdb session directed to a file as: dbus-run-session gdb --args startplasma-wayland --xwayland --x11-display $DISPLAY --exit-with-session=/usr/lib64/libexec/startplasma-waylandsession > ./output 2>&1 I'm also glad to announce I've apparently discovered an essential piece of the puzzle, just tested this heavily and will continue to do so. It appears this glitch only occurs when minimized windows are present in the session; If there are either no other windows or the existing windows are all maximized or restored, opening a new application seems to work just fine. This further caught my attention as some existing windows also rarely freeze (still rendered but visually unchanged) until I minimize and restore them... one of the similar bug reports additionally stated that minimizing and restoring hidden windows with a shortcut might recover them (I don't have this shortcut to test). -- You are receiving this mail because: You are watching all bug changes.
