https://bugs.kde.org/show_bug.cgi?id=460513
--- Comment #8 from Jason Playne <ja...@jasonplayne.com> --- (In reply to space9301 from comment #7) > (In reply to Jason Playne from comment #6) > > *** Bug 460336 has been marked as a duplicate of this bug. *** > > I'm not sure this is a duplicate. For me, my programs remained open -- only > plasmashell crashed. They were only lost when I killed kwin_wayland. There > were no segfaults in either kwin_wayland or plasmashell. > > To reproduce the black screen with movable cursor: > - killall plasmashell (the screen is now black, as the desktop background > is handled by plasmashell, but all the programs are open. In the original > bug, plasmashell failed to relaunch) > - ps $(pgrep kwin_wayland) > PID TTY STAT TIME COMMAND > 220965 ? Ssl 0:00 /usr/bin/kwin_wayland_wrapper --xwayland > 237394 ? Sl 0:02 /usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayland-fd 9 > - killall kwin_wayland (the screen is black, and all the programs are > gone, but I can still move my cursor and launch a terminal with ctrl-alt-t) > - ps $(pgrep kwin_wayland) > PID TTY STAT TIME COMMAND > 220965 ? Ssl 0:00 /usr/bin/kwin_wayland_wrapper --xwayland > 238586 ? Sl 0:02 /usr/bin/kwin_wayland --wayland-fd 7 --socket > wayland-0 --xwayland-fd 8 --xwayland-fd 9 > (kwin_wayland has automatically been restarted. Killing kwin_wayland_wrapper > gets me to the login screen) > - kstart plasmashell (I can now use my session again) > > Sorry if the original bug description was misleading. "Output of journalctl > /usr/bin/kwin_wayland, including crashes" should have been "including > crashes of plasmashell". Your description describes what I am seeing (better than I am able to put into words) The segfault's and back traces I have seen I am thinking are incidental. I believe what I see is what you are describing. I suddenly get a back screen with a movable cursor, kwin_wayland is still running - lots of complains from the apps about losing their connection to the wayland server. I *think* the apps are still alive - I work around the problem with restarting sddm (the big hammer approach) -- You are receiving this mail because: You are watching all bug changes.
