Comment # 34 on bug 1222156 from Togan Muftuoglu

(In reply to Jeff Stern from comment #32)
> (The following is just conjecture, FYI)
> 
> Indeed, following t neo's last (#31) comment, I see that Mesa 24.0 and 24.01
> have both had various radeonsi fixes.
> 
> - https://docs.mesa3d.org/relnotes/24.0.0.html
> 
> - https://docs.mesa3d.org/relnotes/24.0.1.html
> 
> And, as it states at the top of each of both pages:
> 
> ---------------
> "Mesa 24.0.1 implements the OpenGL 4.6 API, but the version reported by
> glGetString(GL_VERSION) or glGetIntegerv(GL_MAJOR_VERSION) /
> glGetIntegerv(GL_MINOR_VERSION) depends on the particular driver being used.
> Some drivers don’t support all the features required in OpenGL 4.6. OpenGL
> 4.6 is only available if requested at context creation. Compatibility
> contexts may report a lower version depending on each driver.
> 
> Mesa 24.0.1 implements the Vulkan 1.3 API, but the version reported by the
> apiVersion property of the VkPhysicalDeviceProperties struct depends on the
> particular driver being used."
> ---------------
> 
> And my /guess/ is this is the issue: Probably some feature of Vulkan is not
> (yet) implemented in this older radeon driver (?)

There was a similar problem in Flatpak as well previously and even though the
normal graphic display would work with the radeon driver none of the flatpak
apps that were using flatpak mesa packages were working. Before current
situation flatpak had solved the radeon issue in 24.0.2 release. Could it what
ever fixed was never upstreamed?