Arch Linux

Please test mesa-20.1.4-2

Dear lordheavy,

I moved from mesa-git (AUR) 20.2.0_devel to the mesa-20.1.4-2 which I found in testing - thank you for the quick turnaround!

MESA booted to KDE without issue. To confirm zink was in working order, I ran 3 graphical programs, 2 native & 1 through wine: glxgears, glhexen2, and Ion Fury.exe.

For all commands I had the env:
MESA_LOADER_DRIVER_OVERRIDE=zink GALLIUM_HUD=cpu+fps `program`

As glxgears and glhexen2 provide some easy log outputs, I was able to confirm zink was in use just as it was in mesa-git.

HOWEVER, I lost the GALLIUM_HUD! Looking back and forth between both PKGBUILDS, -D gallium-extra-hud=true exists in both. I see no obvious reason why I would lose my FPS and CPU monitoring HUD.

mesa-git provides libva-mesa-driver, mesa, mesa-vdpau, opencl-driver, opencl-mesa, opengl-driver, vulkan-driver, vulkan-intel, vulkan-mesa-layer, vulkan-radeon
mesa provides mesa-libgl, opengl-driver

Maybe, in removing mesa-git, I lost a file that allowed the GALLIUM_HUD to spawn.

Otherwise, 20.1.4-2 works without error. I have been using mesa-git for quite some time now so I do not know if it is normal for those users not to have the GALLIUM_HUD function.

*accidentally refreshed and double posted please delete*

@bobberb GALLIUM_HUD seems to work just fine here with 20.1.4-2. https://i.imgur.com/tluqDNq.png

@katt well this is odd, GALLIUM_HUD only fails with zink selected, it's working as expected with LLVM. I wish I knew how to troubleshoot this further.

# pacman -Qqn | pacman -S - && pacman -U mesa-20.1.4.-2-x86_64.pkg.tar.zst
fixed this issue for me.

@lordheavy everything is working as expected.