IS this the same hardware that you see the garbled images on?
I see this in the logs, that would be a kernel bug
Feb 25 17:45:14 ubuntu-gnome /usr/lib/gdm3/gdm-x-session[3595]: [intel_init_bufmgr:1092] Error initializing buffer manager.
Feb 25 17:45:14 ubuntu-gnome acpid[1021]: client connected from 3597[0:0]
Feb 25 17:45:14 ubuntu-gnome /usr/lib/gdm3/gdm-x-session[3595]: (EE) AIGLX error: Calling driver entry point failed
Feb 25 17:45:14 ubuntu-gnome /usr/lib/gdm3/gdm-x-session[3595]: (EE) AIGLX: reverting to software rendering
Feb 25 17:45:14 ubuntu-gnome /usr/lib/gdm3/gdm-x-session[3595]: (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
Feb 25 17:45:14 ubuntu-gnome acpid[1021]: 1 client rule loaded
Feb 25 17:45:14 ubuntu-gnome /usr/lib/gdm3/gdm-x-session[3595]: (II) AIGLX: Loaded and initialized swrast
Feb 25 17:45:14 ubuntu-gnome /usr/lib/gdm3/gdm-x-session[3595]: (II) GLX: Initialized DRISWRAST GL provider for screen 0
IS this the same hardware that you see the garbled images on?
I see this in the logs, that would be a kernel bug gdm3/gdm- x-session[ 3595]: [intel_ init_bufmgr: 1092] Error initializing buffer manager. gdm3/gdm- x-session[ 3595]: (EE) AIGLX error: Calling driver entry point failed gdm3/gdm- x-session[ 3595]: (EE) AIGLX: reverting to software rendering gdm3/gdm- x-session[ 3595]: (II) AIGLX: enabled GLX_MESA_ copy_sub_ buffer gdm3/gdm- x-session[ 3595]: (II) AIGLX: Loaded and initialized swrast gdm3/gdm- x-session[ 3595]: (II) GLX: Initialized DRISWRAST GL provider for screen 0
Feb 25 17:45:14 ubuntu-gnome /usr/lib/
Feb 25 17:45:14 ubuntu-gnome acpid[1021]: client connected from 3597[0:0]
Feb 25 17:45:14 ubuntu-gnome /usr/lib/
Feb 25 17:45:14 ubuntu-gnome /usr/lib/
Feb 25 17:45:14 ubuntu-gnome /usr/lib/
Feb 25 17:45:14 ubuntu-gnome acpid[1021]: 1 client rule loaded
Feb 25 17:45:14 ubuntu-gnome /usr/lib/
Feb 25 17:45:14 ubuntu-gnome /usr/lib/