Per
https://forums.opensuse.org/t/where-to-report-xwayland-crash-the-cause-matters-right/172543/4,
I've had two different types of results after a crash of X, albeit always
caused when playing *Minecraft: Java Edition* via
https://flathub.org/apps/org.prismlauncher.PrismLauncher, whereby Minecraft
slowly becomes laggier, and eventually crashes:

1. The game became progressively slower, to the point where the game-reported
75 FPS felt like barely 30;

   2. Common:

         1. Firstly, the display freezes. Soon after, it becomes black. Then,
the PC fans momentarily cease to operate, and the display becomes artefacted as
the fans resume.
         2. Although the system responds (Alt+SysReq+B performs systemctl
reboot) Alt+F3 doesn't switch from the display server to a TTY. journalctl
--boot=-1 -e produces the log posted to
https://github.com/PrismLauncher/PrismLauncher/issues/2139#issue-2141081956.

   2. Uncommon:

         1. The X server actually crashed (see the last line of the log at
Forge 1.19.2 Server Log [#H1b3oft] - mclo.gs).
         2. Discord and Prism became 10% opacity.
         3. When I logged-out, I remained in TTY3 rather than TTY2, and
switching manually to TTY2 demonstrated that the handover hadn’t occurred. I
had to use TTY4 to systemctl reboot.

This doesn't occur on my brother's installation of Windows 11. In fact, I know
of solely one *potential* report by anyone else of this.