Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/
issues/13122
Control: tags -1 + patch fixed-upstream
On Tue, 10 Jun 2025 at 23:52:02 +0100, Simon McVittie wrote:
I think this might be caused by the gfxstream driver closing a file
descriptor that does not belong to it (as fixed upstream in
https://gitlab.freedesktop.org/mesa/mesa/-/commit/
ecf46edd8a4c3c237f4844d38bf79c0a8489fe66
and 25.0.6) but I have not yet confirmed this.
Looks like this guess was correct. After cherry-picking that commit
(https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/58) the
affected games load successfully.
This could either be solved by applying the one-line patch, or by the
larger change of upgrading to 25.0.6 or later before trixie, ideally
25.0.7 (#1105831).
Talking about this with some upstream contributors, we also wondered
whether gfxstream is really mature enough yet to be enabled in Debian
13. If I understand correctly, it's intended for container/
virtualization use cases on ChromeOS and Android, which doesn't
necessarily seem like a huge benefit if it's being balanced against
gfxstream regressing "ordinary" desktop use-cases.
Normally a driver being broken only affects users of that driver, but
because Vulkan driver enumeration involves loading every driver in order
to probe whether they can find any compatible devices, it's necessary
for at least the load/probe/unload part to be reliable and avoid leaking
resources or damaging existing state in the host process.
smcv