Call for testing: mesa-2404 (25.2.8 update)

snap
1

The candidate track of the mesa-2404 snap has been updated to 25.2.8. It’s been in Ubuntu for a few weeks now.

The snaps using this include:

You may be using mesa-2404 indirectly as it is a content snap, not an application. To check run the following command will list any snaps using it:

snap connections mesa-2404

To test, just switch to the candidate channel. For example:

snap refresh --channel candidate mesa-2404

And use as normal. Please let us know any results here.

If no problems are identified we aim to promote to stable on 17th February

2026-02-13T00:00:00Z

We have found and are resolving an issue with libdrm

I will update candidate once builds have completed and pass initial testing.

We now aim to promote to stable on 23rd February

1 Like
2

This can surface problems with Snaps that include parts of Mesa that conflict with the gpu-2404 interface. For example:

1 Like
3

Through lab testing we discovered that this update breaks Vulkan support in base: core24 snaps on Ubuntu 22.04 or older on Raspberry Pi:

WARNING: [../src/broadcom/vulkan/v3dv_device.c:1325] Code 0 : Kernel driver doesn't have required features. (VK_ERROR_INITIALIZATION_FAILED)
ERROR: [Loader Message] Code 0 : setup_loader_term_phys_devs:  Call to ICD 8's 'vkEnumeratePhysicalDevices' failed with error 0xfffffffd
ERROR at ./vulkaninfo/./vulkaninfo.h:245:vkEnumeratePhysicalDevices failed with ERROR_INITIALIZATION_FAILED

A plausible workaround would be using the HWE kernel, but that doesn’t help Ubuntu Core deployments as there’s no pi-kernel/22-hwe published.

We’re looking for how we can address this and will update this post as we work out the next steps. For now the update will remain available in the candidate channel, particularly for armhf and arm64 to not affect existing deployments.

1 Like
4

We’ve looked through the usage of mesa-2404 on the affected Ubuntu Core 22 systems and couldn’t find a significant enough number to hold this back further.

I’ve released this update to 20% 50% 75% 100% of machines at this point.

5

NB: we needed to temporarily revert this to let downstream snaps deal with a change in how the content is laid out. We’ll soon bring the newest Mesa back without this change, and then bring that back again after a grace period.

We’ll soon bring the newest Mesa back without this change

This is now done for 20% 50% of devices.