In openQA testing of the new mesa 22.1.0 update on Rawhide, several GNOME tests failed. One failed because the top bar was not visible after log in: https://openqa.stg.fedoraproject.org/tests/1805240#step/_graphical_wait_login_2/9 two failed because somehow password entry at GDM failed (which is an odd failure case, not something the test system usually has problems with). Not quite sure what's causing that. Stepping through video of the failed test and even of tests that passed, there's obvious visual glitching, things not getting fully redrawn. One instance of glitching was caught in a screenshot: https://openqa.stg.fedoraproject.org/tests/1805240#step/_graphical_wait_login_2/7 and you can see others by stepping through the videos: https://openqa.stg.fedoraproject.org/tests/1805240/video?filename=video.ogv https://openqa.stg.fedoraproject.org/tests/1805241/video?filename=video.ogv https://openqa.stg.fedoraproject.org/tests/1805242/video?filename=video.ogv Even this passed test shows glitching in the video: https://openqa.stg.fedoraproject.org/tests/1801934/video?filename=video.ogv Watch from about 0:57 when log in to the updated system starts. The VMs used in openQA are qemu VMs with virtio graphics. Full qemu command line: /usr/bin/qemu-system-x86_64 -vga virtio -only-migratable -chardev ringbuf,id=serial0,logfile=serial0,logappend=on -serial chardev:serial0 -audiodev none,id=snd0 -device intel-hda -device hda-output,audiodev=snd0 -global isa-fdc.fdtypeA=none -m 2048 -cpu Nehalem -netdev user,id=qanet0,net=172.16.2.0/24 -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -boot order=c -device qemu-xhci -device usb-tablet -smp 2 -enable-kvm -no-shutdown -vnc :114,share=force-shared -device virtio-serial -chardev pipe,id=virtio_console,path=virtio_console,logfile=virtio_console.log,logappend=on -device virtconsole,chardev=virtio_console,name=org.openqa.console.virtio_console -chardev pipe,id=virtio_console1,path=virtio_console1,logfile=virtio_console1.log,logappend=on -device virtconsole,chardev=virtio_console1,name=org.openqa.console.virtio_console1 -chardev socket,path=qmp_socket,server=on,wait=off,id=qmp_socket,logfile=qmp_socket.log,logappend=on -qmp chardev:qmp_socket -S -device virtio-scsi-pci,id=scsi0 -blockdev driver=file,node-name=hd0-overlay0-file,filename=/var/lib/openqa/pool/24/raid/hd0-overlay0,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0-overlay0,file=hd0-overlay0-file,cache.no-flush=on -device virtio-blk,id=hd0-device,drive=hd0-overlay0,bootindex=0,serial=hd0
Also affecting KDE, actually, see e.g.: https://openqa.stg.fedoraproject.org/tests/1806759#step/_boot_to_anaconda/5
System logs from one of the failures seem to show llvmpipe having some trouble: May 25 03:36:19 fedora audit[1235]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1235 comm="llvmpipe-0" exe="/usr/bin/kwin_wayland" sig=11 res=1 May 25 03:52:34 fedora kernel: llvmpipe-0[987]: segfault at 7f66fd6ec100 ip 00007f672840e7af sp 00007f6723ffe7d0 error 4 May 25 03:52:34 fedora audit[950]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=950 comm="llvmpipe-1" exe="/usr/bin/kwin_wayland" sig=11 res=1
https://bodhi.fedoraproject.org/updates/FEDORA-2022-fd7d44188c fixes this in my local testing.
*** Bug 2090807 has been marked as a duplicate of this bug. ***