Every article tag can be clicked to get a list of all articles in that category. Every article tag also has an RSS feed! You can customize an RSS feed too!
We do often include affiliate links to earn us some pennies. See more here.

The latest update for the open source graphics drivers is here with Mesa 24.2.7 out now. Plus we might see Mesa 24.3 a bit sooner than expected.

For Mesa 24.2.7 the release notes mention these fixes:

  • brw_fs_opt_copy_propagation incorrectly handles size changes of uniforms.
  • nouveau paraview msaa corruption 23.1 bisected regression.
  • Missing xshmfence dependency for X11 WSI on macOS.
  • [AMDGPU RDNA3] Black square artifacts in viewport renders in Blender.
  • radv: test_sm67_sample_cmp_level test in vkd3d-proton fails.
  • [ANV] LNL tiled corruption in background traci Blackops3-trace-dx11-1080p-high.
  • [anv] Possible regression in e3814dee1ac0f90771b921a4f6f5aed10f06e8d4.
  • Confidential issue #12092.

No new features, since it's a point-release for the last stable release.

However, we also have news that Mesa 24.3 development has gone seemingly better than expected, which will have new features. In the release announcement email for the second Release Candidate, developer Dylan Baker mentioned:

We have a fairly small RC2 today, with a bit of work across the board. We currently only have 2 open blocking issues, and given that we delayed the branchpoint by 3 weeks, I wouldn't object to pulling in the RC period by 1 week and have rc3 rather than rc4 be the final release, if we can get all of the issues closed in time.

Based on the release schedule, that might then put the Mesa 24.3 release around November 20th.

Article taken from GamingOnLinux.com.
12 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
6 comments

redneckdrow 7 days ago
QuoteConfidential issue #12092

What? I switched to AMD specifically to use drivers that offer a first-class FOSS experience, and to avoid this kind of vague chicanery.

Part of the point of FOSS is, you know, being open about issues! I get paranoid about this crap ever since I first started reading the likes of Brian Krebs and Bruce Schneier years ago.
axredneck 7 days ago
Quoting: redneckdrow
QuoteConfidential issue #12092

What? I switched to AMD specifically to use drivers that offer a first-class FOSS experience, and to avoid this kind of vague chicanery.

Part of the point of FOSS is, you know, being open about issues! I get paranoid about this crap ever since I first started reading the likes of Brian Krebs and Bruce Schneier years ago.
It's a common practice in almost any opensource when dealing with vulnerabilities.
whizse 7 days ago
View PC info
  • Supporter
Quoting: redneckdrow
QuoteConfidential issue #12092

What? I switched to AMD specifically to use drivers that offer a first-class FOSS experience, and to avoid this kind of vague chicanery.

Part of the point of FOSS is, you know, being open about issues! I get paranoid about this crap ever since I first started reading the likes of Brian Krebs and Bruce Schneier years ago.
This seems to be the fix for the confidential bug:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31914

It's related to WebGL so I'm guessing a security issue in a browser, that's about to be disclosed?


Last edited by whizse on 14 November 2024 at 4:39 pm UTC
LoudTechie 7 days ago
Quoting: whizse
Quoting: redneckdrow
QuoteConfidential issue #12092

What? I switched to AMD specifically to use drivers that offer a first-class FOSS experience, and to avoid this kind of vague chicanery.

Part of the point of FOSS is, you know, being open about issues! I get paranoid about this crap ever since I first started reading the likes of Brian Krebs and Bruce Schneier years ago.
This seems to be the fix for the confidential bug:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/31914

It's related to WebGL so I'm guessing a security issue in a browser, that's about to be disclosed?

Kind of, based on their description it's WebGL reachable, implying that it's a wider attack demonstrated to them in the form of webGL code, which is an understandable angle to take, because webGL is basically the least trusted rendering tool in the entire system.

Edit: based on the patch I would guess it's a buffer overflow attack.


Last edited by LoudTechie on 14 November 2024 at 6:53 pm UTC
KROM 7 days ago
View PC info
  • Supporter
I was hoping for a fix for a game that currently is under NDA, which somewhat would justify a confidential issue. But, by the looks, it's not. :/
Just to say that there can be reasons for such things, despite all openness.
nnohonsjnhtsylay 6 days ago
I hope vulkan video encoding becomes usable soon. Nvidia has supported it for quite a while now.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register


Or login with...
Sign in with Steam Sign in with Google
Social logins require cookies to stay logged in.

Buy Games
Buy games with our affiliate / partner links: