Hard to reproduce wayland bug. Not sure where to find appropriate log. I was using chrome/intellij on separate virtual desktops. While typing in intellij, it was abruptly terminated. When I try to restart it, I get the following (which leads me to believe that something in wayland crashed): Start Failed Failed to initialize graphics environment java.awt.AWTError: Can't connect to X11 window server using ':1' as the value of the DISPLAY variable. at java.desktop/sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at java.desktop/sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:104) When I attempt to restart chrome, I get (less usefully): “google-chrome” terminated by signal SIGTRAP (Trace or breakpoint trap) Other apps remained open or can be started (firefox, terminator).
This is repeatable. Running under lightdm this time (previously under sddm) it brought up the KDE crash handler, which showed that plasmashell had exited unexpectedly (IIRC error 1826). This had the result of crashing most of my applications; terminator was still present but wouldn't accept input. I could bring up krunner but couldn't type into it either. Please let me know where to find relevant logs and I can try again. Version: 4:5.22.5-0ubuntu1
This appears to have been fixed in 5.23.4 (pending a full day's testing without it happening). However, the version I was encountering it on is the one shipped with kubuntu 21.10, so you may want to push a patch down to 5.22 given that there are another 4 months before kubuntu users will get the fix (without using backports), given that it's a showstopper to using wayland.
Unfortunately 5.22 is no longer supported, so it would be up to distros to patch it. Only LTS Plasma versions continue to receive support after the next version is released.