Mesa 25 on latest stable?

I’ve ran the system updater and it isn’t finding any updates (I’m not sure how you can check the version date of your Bazzite install but it should be the latest stable which is 41.20250315) but my mesa version is still 24.3.4. The changelog for stable 41.20250314 said it updated mesa from 24.3.4-5 to 25.0.1-5 and stable 41.20250315 went from that version to 25.0.1-6. Discover also shows no updates - is there something that I need to do to get my mesa version to update? Did these updates get pulled or something?

Edit: So I discovered the bazzite-rollback-helper current command and can confirm that I am on build 41.20250315 so yeah I am confused on why my mesa version is lagging behind. Also, running bazzite-rollback-helper list stable shows a version stable-41.20250317 that is nowhere in the Github releases (they jump from 3/15 to 3/18) - any idea what this ghost version is about?

I’m still super new but I think you might be running an older bazzite image.

When I run: rpm-ostree status, I can see the version date and other details.

I ran it just now, here’s what I found:

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:e43ec4fa563576dac7c8ea2c1db47895a608f4c18326c570ca23b0ddb395a10b
                  Version: 41.20250317 (2025-03-17T05:11:31Z)
          LayeredPackages: coolercontrol lact liquidctl openrazer-meta razergenie

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:4d7eef9f3e76d9f16648274daf3c8bac291ed06da27b2f35c6d886a2366cc9dd
                  Version: 41.20250315 (2025-03-16T00:40:37Z)
          LayeredPackages: coolercontrol lact liquidctl openrazer-meta razergenie

Based on this output, I think my gaming machine is running 41.20250317 from March 17, 2025.

I also checked my mesa versions by running rpm -qa mesa-dri-drivers and here’s the output:

mesa-dri-drivers-25.0.1-6.fc41.x86_64
mesa-dri-drivers-25.0.1-6.fc41.i686

I hope this is helpful.

(By the way, I think you need to reboot in order to get the update. I always forget to do that. Not sure if this might help you too)

1 Like

Oh, I guess my Mesa version is 25 - it shows 25 when I run the command you used. I was going off of all the packages in Discover - there are many identical Mesa packages and every one is v24.

Not sure about that ghost 3/17 version that isn’t mentioned in any releases and my system wouldn’t auto update to but 3/25 just hit stable and is installing now so nothing too concerning I guess.

Thanks for the help!

You can always check the release notes:

Glad I was able to help! I’m brand new and I’m trying to learn.

I just took a look in Discover too and saw a bunch of “mesa” packages listed—I think these are mesa runtimes that Flatpaks use. From what I understand, Flatpaks link to these runtimes, and each Flatpak has to be updated to use a newer mesa version. Until that happens, your system won’t install a newer mesa runtime. All of my mesa runtimes are version 24 as well, so I think my Flatpaks are still using the older mesa too.

(Since Mesa 25 is still pretty new, I don’t think most Flatpaks have been updated to use it yet. There might be a way to force a Flatpak to use a newer runtime, but in most cases it probably only matters if you’re gaming.)

Out of curiosity—are you trying to get the latest Mesa specifically for gaming? That’s my reason too. Thankfully, it looks like Bazzite really delivers here. From what I can tell, Steam is installed through the Containerfile, so I believe it uses Mesa 25. I’m actually pretty impressed—we get the newest packages, and it’s still super stable :grinning_face:

If you’re curious, here’s how our bazzite image gets steam:

Hope that helps!

As stated in my original post, the issue stemmed from me reading the release notes and not seeing what I was expecting based on them. Until this other user pointed out the correct way of verifying the mesa version. :slightly_smiling_face:

1 Like