Fix GNOME and KDE crash with certain AMD GPUs:
Fix wrong colors due to fix for s390x:
Fix GNOME crash due to a bug in eglQueryDmaBufModifiersEXT:
Fix egl on s390x
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-2024-337ebae0a7
Please login 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 has obsoleted mesa-24.1.2-3.fc40, and has inherited its bugs and notes.
jexposit edited this update.
jexposit edited this update.
jexposit edited this update.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
No regressions noted
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Works.
This update has been submitted for stable by bodhi.
Working fine.
Note I'm having the problems in cs9 with mesa 24.1.0 currently, previous version works.
@nixuser thanks for testing! I submitted this same version of mesa to CentOS Stream 9. I should be available in a few days. If you have problems with it, please open a bug report and I'll look into it.
works
This update has been pushed to stable.
24.1.2-7 works with my R7 370, while 24.1.2-2 Gnome-Wayland sessions could not launch any app. Hooray!
Breaks LLVM shader compilation in a few apps. Here is the relevant log from Spectacle.
I'm getting the same issues related to LLVM shader compilation in "Steam" after update to this MESA package when trying to establish "Remote Play" session.
AMD Radeon RX 6650M (RADV NAVI23)
@veilink @dm-zharov I think it is the same issue as: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10927
The commit that is described as the culprit ("ac, radeonsi: remove has_syncobj, has_fence_to_handle") is already addressed in this mesa release, so as mentioned in the last comment, there might be another error: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10927#note_2439112
If you could comment on that bug report or open a new one it'd be helpful.
It looks like an AMD-only issue. I tested it on Intel and the problem is not present.
I think it is related to the backport this version of mesa includes from: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29876
As a workaround, you can downgrade mesa to the previous version (mesa-24.1.2-2.fc40 if I remember correctly).
Yes, I have downgraded to 24.1.2-2.fc40 and everything works as intended.
It looks like you have already mentioned the issue in the related issue pages and MRs. I will chime in there when there is more development on the issue. Thanks
@jexposit one thing i forgot to mention is that this issue doesn't happen for me on mesa-git. For posterity this is the mesa-git build i used that had no issues.
P.S. The log I shared is actually someone from the Nobara community and not mine. However, I can also reproduce it with my integrated AMD graphics (Radeon 660M from a Ryzen 5 6600HS)
@veilink I think it is caused by the patch backported from: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29876
Adding a comment in that issue clarifying the problem. If you could test mesa-git + that MR it'd be super useful.
I only backported 1 patch from the MR and it'd be good to know if the other patches fix the issue or the MR will introduce a regression.
@jexposit The build is fine actually. The error happens because I assume that mesa-va-drivers-freeworld from RPMFusion doesn't carry the patch and there is a mismatch between how the two handle stuff. If I uninstall mesa-va-drivers-freeworld or use mesa-va-drivers from Fedora's repos. I can open Spectacle fine but with no VAAPI.
As there has been an official reply from mesa dev too, I assume that the patches aren't getting pulled from here. I will proceed to create a bugzilla in RPMFusion to prompt a rebuild with these patches.
Giving good karma now since its already fixed on RPMFusion's end. I have installed the freeworld va driver packages locally and am using this build of mesa. We just need to wait for those freeworld packages to propagate to all mirrors. Thanks again Jose!
@veilink: Where do you see a fix?
I am observing the error, you decribed above when running vlc with mesa-va-drivers-freeworld-24.1.2-1.fc40.x86_64 mesa-vdpau-drivers-freeworld-24.1.2-1.fc40.x86_64 and mesa-*-24.1.2-7.fc40.x86_64 on both my radeon machines.
Downgrading to mesa-*-24.1.2-3.fc40.x86_64 helped.
@corsepiu https://download1.rpmfusion.org/free/fedora/updates/40/x86_64/repoview/mesa-va-drivers-freeworld.html Download the new builds manually from here or wait for it to reach your local mirrors.
@veilink It's all right now. Thanks for great work!
These package do NOT work for me:
vlc foo.mp4
VLC media player 3.0.21 Vetinari (revision 3.0.21-0-gdd8bfdbabe8) [0000560c3a5d06a0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. libva info: VA-API version 1.21.0 libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_21 libva info: va_openDriver() returns 0 amdgpu: The CS has cancelled because the context is lost. This context is innocent. Aborted (core dumped)
Apologies, scratch my previous comment - I was looking at the wrong machine.
The mesafreeworld-24.1.2-2.fc40.x86_64 packages seem to work.
HP EliteBook 745 here with radeon R6 gpu
This update fixes gnome-shell crashes in wayland when any app is launched, but browsing with firefox or opening gnome settings the screen goes black and unresponsive in both wayland and xorg sessions (almost random). The only option is to force poweroff. And the logs doesn't show any core dump. Downgrading mesa-* to 24.0.5-1 is my workaround.
@injiniero I'd recommend to comment in the upstream issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11352
Or open a new one if you don't consider that they are similar. Hopefully the developers would be able to point into the right direction.