Comment 8 for bug 2069477

There are two separate issues here, and both seem to result in an int3:

[ 14.366966] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 770048 bytes), total 32768 (slots), used 288 (slots)
[ 14.440052] traps: gnome-shell[1377] trap int3 ip:76f0445210df sp:7ffe06de1b10 error:0 in libglib-2.0.so.0.8000.0[76f0444dd000+a0000]
[ 14.958767] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 360448 bytes), total 32768 (slots), used 22 (slots)
[ 15.015203] traps: gnome-shell[1397] trap int3 ip:7f04827000df sp:7ffc222971e0 error:0 in libglib-2.0.so.0.8000.0[7f04826bc000+a0000]

^^^ That's bug 2062426 with workarounds listed in bug 2060268.

Jun 14 20:45:57 acrylic gnome-shell[1377]: No cursor theme available, please install a cursor theme
Jun 14 20:45:57 acrylic gnome-shell[1377]: Received an X Window System error.
                                           This probably reflects a bug in the program.
                                           The error was 'BadCursor (invalid Cursor parameter)'.
                                             (Details: serial 925 error_code 6 request_code 95 (core protocol) minor_code 0)
                                             (Note to programmers: normally, X errors are reported asynchronously;
                                              that is, you will receive the error a while after causing it.
                                              To debug your program, run it with the MUTTER_SYNC environment
                                              variable to change this behavior. You can then get a meaningful
                                              backtrace from your debugger if you break on the mtk_x_error() function.)
Jun 14 20:45:57 acrylic kernel: traps: gnome-shell[1377] trap int3 ip:76f0445210df sp:7ffe06de1b10 error:0 in libglib-2.0.so.0.8000.0[76f0444dd000+a0000]

^^^ That's bug 2062377.