Wayland broken using mesa-23

[Crashdummyy]

Infos about my system

OS: Fedora release 37 (Thirty Seven) x86_64
DS: Wayland 
DE: GNOME 43.2 
WM: Mutter 
CPU: AMD Ryzen 9 6900HS with Radeon Graphics (16) @ 4.925GHz 
GPU: NVIDIA Geforce RTX 3070 Ti Laptop GPU 
GPU: AMD ATI Radeon 680M 
Memory: 3112MiB / 31329MiB
Kernel Version: 6.2.0-0.rc3.20230110git5a41237ad1d4.25.vanilla.1.fc37.x86_64
--- packages
Mesa-*: 22.3.2-1.fc37
Displaylink: 1.12.0-2
Evdi: 1.12.0 ( well latest git )

Besides this is an optimus based laptop but thats not the issue for once...

Issue

I need to emphasize here that I currently downgraded mesa to 22.3 which allows evdi to work on wayland again.

When I try to use mesa from git ( eg https://copr.fedorainfracloud.org/coprs/xxmitsu/mesa-git/ ) evdi cant be used ( on wayland ) anymore.
The moment I plug the docking station in ( without any device connected to it ) the gnome-shell immediately.

It is then restarted on x11 resulting in horrible performance.

Jan 11 12:28:03 crashphyrus kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
Jan 11 12:28:03 crashphyrus kernel: usb 3-1: New USB device found, idVendor=14b0, idProduct=040d, bcdDevice= 7.04
Jan 11 12:28:03 crashphyrus kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 12:28:03 crashphyrus kernel: usb 3-1: Product: USB2.0 Hub             
Jan 11 12:28:03 crashphyrus kernel: usb 3-1: Manufacturer: VIA Labs, Inc.         
Jan 11 12:28:03 crashphyrus kernel: usb 3-1: SerialNumber: 000000001
Jan 11 12:28:03 crashphyrus kernel: hub 3-1:1.0: USB hub found
Jan 11 12:28:03 crashphyrus kernel: hub 3-1:1.0: 5 ports detected
Jan 11 12:28:03 crashphyrus kernel: usb 6-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
Jan 11 12:28:03 crashphyrus kernel: usb 6-1: New USB device found, idVendor=14b0, idProduct=040c, bcdDevice= 7.04
Jan 11 12:28:03 crashphyrus kernel: usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 12:28:03 crashphyrus kernel: usb 6-1: Product: USB3.1 Hub             
Jan 11 12:28:03 crashphyrus kernel: usb 6-1: Manufacturer: VIA Labs, Inc.         
Jan 11 12:28:03 crashphyrus kernel: usb 6-1: SerialNumber: 000000001
Jan 11 12:28:03 crashphyrus kernel: hub 6-1:1.0: USB hub found
Jan 11 12:28:03 crashphyrus kernel: hub 6-1:1.0: 4 ports detected
Jan 11 12:28:04 crashphyrus kernel: usb 3-1.3: new high-speed USB device number 3 using xhci_hcd
Jan 11 12:28:04 crashphyrus kernel: usb 3-1.3: New USB device found, idVendor=14b0, idProduct=040f, bcdDevice=90.23
Jan 11 12:28:04 crashphyrus kernel: usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 12:28:04 crashphyrus kernel: usb 3-1.3: Product: USB2.0 Hub             
Jan 11 12:28:04 crashphyrus kernel: usb 3-1.3: Manufacturer: VIA Labs, Inc.         
Jan 11 12:28:04 crashphyrus kernel: usb 3-1.3: SerialNumber: 000000000
Jan 11 12:28:04 crashphyrus kernel: hub 3-1.3:1.0: USB hub found
Jan 11 12:28:04 crashphyrus kernel: hub 3-1.3:1.0: 4 ports detected
Jan 11 12:28:04 crashphyrus kernel: usb 6-1.3: new SuperSpeed USB device number 3 using xhci_hcd
Jan 11 12:28:04 crashphyrus kernel: usb 6-1.3: New USB device found, idVendor=14b0, idProduct=040e, bcdDevice=90.23
Jan 11 12:28:04 crashphyrus kernel: usb 6-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 12:28:04 crashphyrus kernel: usb 6-1.3: Product: USB3.0 Hub             
Jan 11 12:28:04 crashphyrus kernel: usb 6-1.3: Manufacturer: VIA Labs, Inc.         
Jan 11 12:28:04 crashphyrus kernel: usb 6-1.3: SerialNumber: 000000000
Jan 11 12:28:04 crashphyrus kernel: hub 6-1.3:1.0: USB hub found
Jan 11 12:28:04 crashphyrus kernel: hub 6-1.3:1.0: 4 ports detected
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: new SuperSpeed USB device number 4 using xhci_hcd
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: New USB device found, idVendor=17e9, idProduct=6000, bcdDevice=35.05
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: Product: Hybrid Dock 1001
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: Manufacturer: DisplayLink
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: SerialNumber: FINK293100978
Jan 11 12:28:05 crashphyrus mtp-probe[3866]: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:08.3/0000:08:00.3/usb6/6-1/6-1.4"
Jan 11 12:28:05 crashphyrus mtp-probe[3866]: bus: 6, device: 4 was not an MTP device
Jan 11 12:28:05 crashphyrus kernel: usbcore: registered new interface driver cdc_ether
Jan 11 12:28:05 crashphyrus systemd[1]: Starting displaylink-driver.service - DisplayLink Driver Service...
Jan 11 12:28:05 crashphyrus kernel: cdc_ncm 6-1.4:1.5: MAC-Address: e8:ea:6a:96:86:fe
Jan 11 12:28:05 crashphyrus kernel: cdc_ncm 6-1.4:1.5: setting rx_max = 16384
Jan 11 12:28:05 crashphyrus kernel: cdc_ncm 6-1.4:1.5: setting tx_max = 16384
Jan 11 12:28:05 crashphyrus kernel: cdc_ncm 6-1.4:1.5 eth0: register 'cdc_ncm' at usb-0000:08:00.3-1.4, CDC NCM (SEND ZLP), e8:ea:6a:96:86:fe
Jan 11 12:28:05 crashphyrus kernel: usbcore: registered new interface driver cdc_ncm
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: Warning! Unlikely big volume range (=767), cval->res is probably wrong.
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: [4] FU [Mic Capture Volume] ch = 2, val = -4592/7680/16
Jan 11 12:28:05 crashphyrus NetworkManager[1493]: <info>  [1673436485.1735] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5)
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: Warning! Unlikely big volume range (=672), cval->res is probably wrong.
Jan 11 12:28:05 crashphyrus kernel: usb 6-1.4: [7] FU [USB Audio Playback Volume] ch = 6, val = -10752/0/16
Jan 11 12:28:05 crashphyrus kernel: usbcore: registered new interface driver snd-usb-audio
Jan 11 12:28:05 crashphyrus kernel: usbcore: registered new interface driver cdc_wdm
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Initialising logging on level 4
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Atomic driver: yes
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Increasing device count to 4
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] (card2) Opened by Task 3880 (modprobe) of process 3880 (modprobe)
Jan 11 12:28:05 crashphyrus kernel: evdi evdi.0: [drm] Cannot find any crtc or sizes
Jan 11 12:28:05 crashphyrus kernel: evdi: [W] evdi_painter_send_update_ready_if_needed:693 Painter does not exist!
Jan 11 12:28:05 crashphyrus kernel: [drm] Initialized evdi 1.12.0 20220713 for evdi.0 on minor 2
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Evdi platform_device create
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] (card3) Opened by Task 3880 (modprobe) of process 3880 (modprobe)
Jan 11 12:28:05 crashphyrus kernel: evdi evdi.1: [drm] Cannot find any crtc or sizes
Jan 11 12:28:05 crashphyrus kernel: evdi: [W] evdi_painter_send_update_ready_if_needed:693 Painter does not exist!
Jan 11 12:28:05 crashphyrus kernel: [drm] Initialized evdi 1.12.0 20220713 for evdi.1 on minor 3
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Evdi platform_device create
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] (card4) Opened by Task 3880 (modprobe) of process 3880 (modprobe)
Jan 11 12:28:05 crashphyrus kernel: evdi evdi.2: [drm] Cannot find any crtc or sizes
Jan 11 12:28:05 crashphyrus kernel: evdi: [W] evdi_painter_send_update_ready_if_needed:693 Painter does not exist!
Jan 11 12:28:05 crashphyrus kernel: [drm] Initialized evdi 1.12.0 20220713 for evdi.2 on minor 4
Jan 11 12:28:05 crashphyrus kernel: usbcore: registered new interface driver cdc_mbim
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Evdi platform_device create
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] (card5) Opened by Task 3880 (modprobe) of process 3880 (modprobe)
Jan 11 12:28:05 crashphyrus kernel: evdi evdi.3: [drm] Cannot find any crtc or sizes
Jan 11 12:28:05 crashphyrus kernel: evdi: [W] evdi_painter_send_update_ready_if_needed:693 Painter does not exist!
Jan 11 12:28:05 crashphyrus kernel: [drm] Initialized evdi 1.12.0 20220713 for evdi.3 on minor 5
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] Evdi platform_device create
Jan 11 12:28:05 crashphyrus systemd[1]: Started displaylink-driver.service - DisplayLink Driver Service.
Jan 11 12:28:05 crashphyrus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=displaylink-driver comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 11 12:28:05 crashphyrus mtp-probe[3887]: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:08.3/0000:08:00.3/usb6/6-1/6-1.4"
Jan 11 12:28:05 crashphyrus mtp-probe[3887]: bus: 6, device: 4 was not an MTP device
Jan 11 12:28:05 crashphyrus kernel: cdc_ncm 6-1.4:1.5 enp8s0f3u1u4i5: renamed from eth0
Jan 11 12:28:05 crashphyrus kernel: evdi: [I] (card3) Opened by Task 1061 (systemd-logind) of process 1061 (systemd-logind)
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: MESA-LOADER: failed to retrieve device information
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: MESA-LOADER: failed to open evdi: /usr/lib64/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
Jan 11 12:28:05 crashphyrus NetworkManager[1493]: <info>  [1673436485.1945] device (eth0): interface index 4 renamed iface from 'eth0' to 'enp8s0f3u1u4i5'
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: MESA-LOADER: failed to retrieve device information
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: MESA-LOADER: failed to retrieve device information
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: ATTENTION: default value of option mesa_glthread overridden by environment.
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: kmsro: driver missing
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: double free or corruption (!prev)
Jan 11 12:28:05 crashphyrus gnome-shell[1754]: == Stack trace for context 0x55dfa3db0310 ==
Jan 11 12:28:05 crashphyrus audit[1754]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=1754 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=6 res=1
Jan 11 12:28:05 crashphyrus NetworkManager[1493]: <info>  [1673436485.1990] device (enp8s0f3u1u4i5): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jan 11 12:28:05 crashphyrus NetworkManager[1493]: <info>  [1673436485.2000] settings: (enp8s0f3u1u4i5): created default wired connection 'Wired connection 2'
Jan 11 12:28:05 crashphyrus systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
Jan 11 12:28:05 crashphyrus audit: BPF prog-id=83 op=LOAD
Jan 11 12:28:05 crashphyrus audit: BPF prog-id=84 op=LOAD
Jan 11 12:28:05 crashphyrus audit: BPF prog-id=85 op=LOAD
Jan 11 12:28:05 crashphyrus systemd[1615]: Reached target sound.target - Sound Card.
Jan 11 12:28:05 crashphyrus systemd[1]: Started systemd-coredump@0-3911-0.service - Process Core Dump (PID 3911/UID 0).
Jan 11 12:28:05 crashphyrus audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@0-3911-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Those entries look suspicious besides the gnome-shell crashing immediately afterwards

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open evdi: /usr/lib64/dri/evdi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)

[Crashdummyy]

I guess theres been just a range of "bad" commits.
I tried it today with mesa 23.1.0-0.3.20230305.15.9b09f24 and kernel 6.3.0-0.rc0.20230305gtb01fe98d.214.vanilla.fc37.x86_64