Your message dated Thu, 12 Jun 2025 12:18:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#1107633: mesa-vulkan-drivers: games hang or fail to
start under Proton if gfxstream_vk_icd.json available
has caused the Debian Bug report #1107633,
regarding mesa-vulkan-drivers: games hang or fail to start under Proton if
gfxstream_vk_icd.json available
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1107633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107633
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mesa-vulkan-drivers
Version: 25.0.5-1
Severity: important
To reproduce:
- Reproducible in Tchia (https://steamdb.info/app/1496590/) and Apollo
Justice: Ace Attorney Trilogy (https://steamdb.info/app/2187220/),
likely also other Windows games, running under multiple versions of
Proton (tried 10.0, 9.0, 8.0)
- Launch the game via Steam and Proton
Expected result:
- game launches
Actual result:
- game hangs with a blank, black window, or does not start at all
Workaround:
- Disable /usr/share/vulkan/icd.d/gfxstream_vk_icd.json, for
example by renaming it to gfxstream_vk_icd.json.off, or by setting
VK_DRIVER_FILES to the path to the Vulkan ICD I expect my system
to be using
Other details:
Sometimes Wine/Proton logs a message when these failures happen,
typically looking like:
- wine client error:1a0: write: Invalid argument
- wine client error:1a0: read: Invalid argument
- wine client error:0: recvmsg: Socket operation on non-socket
- wine client error:128: write: Invalid argument
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.
My GPU is probably not relevant here, but it is a Radeon RX 7600:
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 33 [Radeon RX 7600/7600 XT/7600M
XT/7600S/7700S / PRO W7600] [1002:7480] (rev cf)
-- System Information:
Debian Release: 13.0
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-security'), (80, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.32-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mesa-vulkan-drivers depends on:
ii libc6 2.41-8
ii libdrm-amdgpu1 2.4.124-2
ii libdrm2 2.4.124-2
ii libelf1t64 0.192-4
ii libexpat1 2.7.1-1
ii libgcc-s1 14.2.0-19
ii libllvm19 1:19.1.7-3
ii libstdc++6 14.2.0-19
ii libvulkan1 1.4.309.0-1
ii libwayland-client0 1.23.1-3
ii libx11-xcb1 2:1.8.12-1
ii libxcb-dri3-0 1.17.0-2+b1
ii libxcb-present0 1.17.0-2+b1
ii libxcb-randr0 1.17.0-2+b1
ii libxcb-shm0 1.17.0-2+b1
ii libxcb-sync1 1.17.0-2+b1
ii libxcb-xfixes0 1.17.0-2+b1
ii libxcb1 1.17.0-2+b1
ii libxshmfence1 1.3.3-1
ii libzstd1 1.5.7+dfsg-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
mesa-vulkan-drivers recommends no packages.
mesa-vulkan-drivers suggests no packages.
Versions of packages xserver-xorg depends on:
ii x11-xkb-utils 7.7+9
ii xkb-data 2.42-1
ii xserver-xorg-core 2:21.1.16-1.1
ii xserver-xorg-input-all 1:7.7+24
ii xserver-xorg-input-libinput [xorg-driver-input] 1.5.0-1
ii xserver-xorg-input-wacom [xorg-driver-input] 1.2.3-1
ii xserver-xorg-video-amdgpu [xorg-driver-video] 23.0.0-1
ii xserver-xorg-video-fbdev [xorg-driver-video] 1:0.5.0-2
ii xserver-xorg-video-vesa [xorg-driver-video] 1:2.6.0-2
Versions of packages xserver-xorg recommends:
ii libgl1-mesa-dri 25.0.5-1
ii xserver-xorg-legacy 2:21.1.16-1.1
Versions of packages xserver-xorg-core depends on:
ii keyboard-configuration 1.237
ii libaudit1 1:4.0.2-2+b2
ii libc6 2.41-8
ii libdbus-1-3 1.16.2-2
ii libdrm2 2.4.124-2
ii libegl1 1.7.0-1+b2
ii libepoxy0 1.5.10-2
ii libgbm1 25.0.5-1
ii libgl1 1.7.0-1+b2
ii libnettle8t64 3.10.1-1
ii libpciaccess0 0.17-3+b3
ii libpixman-1-0 0.44.0-3
ii libselinux1 3.8.1-1
ii libsystemd0 257.6-1
ii libudev1 257.6-1
ii libunwind8 1.8.1-0.1
ii libxau6 1:1.0.11-1
ii libxcvt0 0.1.3-1
ii libxdmcp6 1:1.1.5-1
ii libxfont2 1:2.0.6-1+b3
ii libxshmfence1 1.3.3-1
ii udev 257.6-1
ii xserver-common 2:21.1.16-1.1
Versions of packages xserver-xorg-core recommends:
ii libgl1-mesa-dri 25.0.5-1
ii libpam-systemd [logind] 257.6-1
ii xcvt 0.1.3-1
Versions of packages xserver-xorg-core suggests:
pn xfonts-100dpi | xfonts-75dpi <none>
pn xfonts-scalable <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 25.0.7-1
On Thu, 12 Jun 2025 at 13:06:45 +0300, Timo Aaltonen wrote:
I have 25.0.7 (plus one revert for hasvk) ready to go now that the
previous upload migrated.
Thanks, marking this as closed in that version - I know you sent a
"fixed" message to the BTS control mechanism already, but that doesn't
actually mark the bug as resolved.
I haven't verified that 25.0.7 fixes this, but it should (that's where
the cherry-picked patch that I tested came from). I'll try to do that
this evening.
It will need an unblock (freeze exception) from the release team for
this to actually make it into trixie.
gfxstream got enabled in
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/53
and it's enabled also in Ubuntu 25.04 and while there have been issues
with it, the world didn't burn down.
Your judgement on this is better-informed than mine, I just wanted to
make sure that "is gfxstream really ready?" had been considered.
smcv
--- End Message ---
