The fatal exceptions in question are (from memory) mostly in the DRM code (running in the compositor thread) from the XMir public testing. I know this only from the log files showing single line exception output.
These are not things we can handle at runtime in any sensible way. They are exceptional circumstances which are not recoverable. The most sensible and useful thing you can do is produce a clean core file and stack trace to facilitate fixing of the bug so it doesn't happen again.
The fatal exceptions in question are (from memory) mostly in the DRM code (running in the compositor thread) from the XMir public testing. I know this only from the log files showing single line exception output.
These are not things we can handle at runtime in any sensible way. They are exceptional circumstances which are not recoverable. The most sensible and useful thing you can do is produce a clean core file and stack trace to facilitate fixing of the bug so it doesn't happen again.
See all the duplicates of this bug...