mesa v25.2.7 + backport https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38252
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-82b66363b4Please log in to add feedback.
This update has been submitted for testing by jexposit.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
works without testing zink + wayland
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
Works for me..
Elite Dangerous fails to start from the Steam launcher for me after this update is applied (and works fine again after it's reverted). I can't see exactly what's going wrong, but both steam.exe and explorer.exe attempting to start the game just jump to 100% CPU and nothing happens.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
no game will launch in native steam launcher after this update as per above feedback
Hey @stevestorey @t3rm1n4l
Thanks a lot for testing and for reporting this issue!
Could you provide details about your hardware and, if available, Steam logs or a coredump, please?
Here are some details about how to generate one: https://fedoramagazine.org/file-better-bugs-coredumpctl/
My hardware is an AMD Ryzen 7700 CPU (iGPU disabled in UEFI Bios) on an AsRock B650 Pro RS motherboard with an nVidia 5060Ti 16GB GPU. Running kernel 6.17.8-300.fc43.x86_64, KDE 6.5.2 on Wayland, with nVidia drivers v580.105.08 from the negativo17 repos.
dnf upgrade transaction is:
There's no coredumps as nothing crashes - 2 processes - steam.exe and explorer.exe start, but just spin at 100% CPU, and I can't see what they're doing. If I kill those 2 processes, then it seems that the game does try to start, via another 2 explorer.exe and steam.exe processes with the command
Command: ['/mnt/extra/extra-home/steve/programs/linux-steam/steamapps/common/Elite Dangerous/EDLaunch.exe', '/Steam', '/novr']being run as args to explorer.exe.Having enabled game-specific logging, I do get logs from the second set of processes as they start up, and then nothing further is written as they spin at 100%:
I've also tried running with various different Proton versions, but they all do the same thing
See the same issues that steam games are not launching.
Hey @stevestorey, @t3rm1n4l, @valdyn,
Are you all using proprietary nvidia drivers? If not the used GPU would be helpful information.
Can you try the mesa-25.2.7-1.fc43 build. If that build is broken as well it's caused by change in mesa-25.2.7. If it works the issue is caused by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38252
mesa-25.2.7-1.fc43 works fine for me, so I think it's the MR that's the problem
@jannau: Sorry totally forgot. Running a RX 7800 XT. 25.2.7-1.fc43 works.
I'm running an AMD Ryzen 7 7700, MSI Mag Tomahawk X670E Wifi motherboard, NVIDIA RTX 4060 Ti 8 Gb (580.105.08-1 negativo17). I don't get any crashes when running mesa 25.7.2, but I get the same thing as @stevestorey where explorer.exe and steam.exe spin up 100% cpu and the games simply do not launch, for me it is any game with any version of proton in steam (native package from rpmfusion) I downgraded to mesa 25.2.6-1 and everything works fine again.
All is working here:
This update has been submitted for stable by leigh123linux.
This update has been pushed to stable.
Same issue as stated above. Steam games will not run underProton. Native Linux games run fine.
OS: Fedora Linux 43 (Sway) Kernel: 6.17.8-300.fc43.x86_64 Motherboard: MSI X670E Tomohawk WiFi CPU: AMD Ryzen 9700X GPU: AMD Radeon RX 7800 XT mesa-dri-drivers: 25.2.7.2.fc43
Since upgrading to mesa 25.2.7-2 I've encountered infinite recursion when trying to create a Vulkan instance that includes the validation layer. The reporter of https://bugzilla.redhat.com/show_bug.cgi?id=2416557 found a vulkan-tools app that seems to encounter a similar problem.
Segfault when launching some vulkan apps after latest mesa 25.2.7-2 and linux/amdgpu-firmware 20251111-1 updates. Links to bug tracking: https://bugzilla.redhat.com/show_bug.cgi?id=2415839 https://bugzilla.redhat.com/show_bug.cgi?id=2416557 https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/11111#issuecomment-3568220865 https://gitlab.freedesktop.org/mesa/mesa/-/issues/14322#note_3199622
Hi
Latest revision of https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38252 fixed a bug that was causing a stackoverflow when using MESA_device_select with any other vulkan layer enabled (can be reproduced with
vkcube --validate, which for example enables the validation layer), I'm guessing people complaining in the thread might have other layers, like mangohud, and/or other steam/proton related stuff.Not familiar with the process here, but would be nice if you could kickoff another build with the latest MR revision, and possibly backout 25.2.7-2, but not sure if doable or if the issue is bad enough to warrant that.
Thanks for your time!
@jiboo there is already a subsequent update with the fix.