llvmpipe with Mesa Master is really weird with Wayland display servers now.
I can't explain it but I can provide this video. It seems there is some regression in llvmpipe, where updates are weird, and blocky, and looks kind of like VNC or something over a slow connection.
At first I thought something was up with virt-manager and Spice screen updates, but if I knock back Mesa to something earlier like b5619464 it works
I also get similar behavior with Cage and foot. The terminal acts really weird. I don't seem to get anything tasty in Weston's log, but I do get this from cage
00:00:00.007 [ERROR] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
00:00:00.007 [ERROR] [EGL] command: eglQueryDeviceStringEXT, error: EGL_BAD_PARAMETER (0x300c), message: "eglQueryDeviceStringEXT"
pci id for fd 14: 1013:00b8, driver (null)
MESA-LOADER: failed to open cirrus: /opt/lib/x86_64-linux-gnu/dri/cirrus_dri.so: cannot open shared object file: No such file or directory (search paths /opt/lib/x86_64-linux-gnu/dri, suffix _dri)
failed to load driver: cirrus
pci id for fd 18: 1013:00b8, driver (null)
MESA-LOADER: failed to open cirrus: /opt/lib/x86_64-linux-gnu/dri/cirrus_dri.so: cannot open shared object file: No such file or directory (search paths /opt/lib/x86_64-linux-gnu/dri, suffix _dri)
failed to load driver: cirrus
00:00:00.061 [ERROR] [types/wlr_linux_dmabuf_v1.c:664] Failed to get DRM FD from renderer
00:00:00.061 [ERROR] [types/wlr_linux_dmabuf_v1.c:965] Failed to init default linux-dmabuf feedback
info: main.c:420: version: 1.11.0-74-g6e536e7e (Mar 07 2022, branch 'master') -pgo +ime -graphemes -assertions
info: main.c:427: arch: Linux x86_64/64-bit
info: main.c:439: locale: en_US.UTF-8