Your message dated Sat, 08 Aug 2026 15:49:41 +0000
with message-id <[email protected]>
and subject line Bug#1142299: fixed in vkd3d 2.0+ds-2
has caused the Debian Bug report #1142299,
regarding vkd3d: FTBFS on riscv64: Several tests segfault
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.)
--
1142299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142299
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: vkd3d
Version: 2.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: [email protected], [email protected]
User: [email protected]
Usertags: riscv64
vkd3d 2.0 fails many of its build-time tests on riscv64, with 6 tests
segfaulting and one test failing gracefully:
https://buildd.debian.org/status/fetch.php?pkg=vkd3d&arch=riscv64&ver=2.0%2Bds-1&stamp=1784232926&raw=0
>Segmentation fault
>FAIL tests/d3d12 (exit status: 139)
>Segmentation fault
>FAIL tests/hlsl_d3d12 (exit status: 139)
>Segmentation fault
>FAIL tests/hlsl/compute.shader_test (exit status: 139)
>shader_runner.c:1964: non-const-indexing.shader_test:398: Model 2.0: Test
>failed: Got {5.00000000e+00, 6.00000000e+00, 7.00000000e+00, 8.00000000e+00},
>expected {1.00000000e+00, 2.00000000e+00, 3.00000000e+00, 4.00000000e+00} at
>(0, 0).
>FAIL tests/hlsl/non-const-indexing.shader_test (exit status: 1)
>Segmentation fault
>FAIL tests/hlsl/rasteriser-ordered-views.shader_test (exit status: 139)
>Segmentation fault
>FAIL tests/hlsl/tgsm.shader_test (exit status: 139)
>Segmentation fault
>FAIL tests/hlsl/uav-rwbuffer.shader_test (exit status: 139)
As with the similar armhf bug #1142206, these might well be problems
with Mesa llvmpipe/lavapipe, rather than genuinely being a bug in vkd3d.
This is probably not actually a regression in vkd3d. Version 1.2
compiled successfully on riscv64 buildds, but version 1.2 also didn't
actually run the majority of the tests on buildds: the buildd log claims
that all tests passed, but if you build locally in a buildd-like
environment and look at tests/*.log (which unfortunately are not
reflected into the buildd log), you'll see that most (all?) of the tests
were skipped because there was no working Vulkan driver. This is
because, before
https://salsa.debian.org/wine-team/vkd3d/-/commit/d2dcaf91440111271a285b119d2a05ba8409a8b6,
there was no build-dependency on mesa-vulkan-drivers.
Wine upstream seems unlikely to be actively supporting riscv64, and
nothing in Debian seems to depend on vkd3d (yet?), so I think it might
be most realistic to drop vkd3d from the riscv64 architecture and then
ask the ftp team to remove the old "cruft" binaries, unless a riscv64
porter is available to investigate this in detail.
Alternatively, if maintainers of vkd3d and/or riscv64 (and armhf)
porters are reasonably confident that it does work on systems with an
actual GPU, another possible workaround would be to skip the tests or
ignore their results on riscv64 (and armhf).
smcv
--- End Message ---
--- Begin Message ---
Source: vkd3d
Source-Version: 2.0+ds-2
Done: Stephen Kitt <[email protected]>
We believe that the bug you reported is fixed in the latest version of
vkd3d, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stephen Kitt <[email protected]> (supplier of updated vkd3d package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 08 Aug 2026 17:29:02 +0200
Source: vkd3d
Architecture: source
Version: 2.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party <[email protected]>
Changed-By: Stephen Kitt <[email protected]>
Closes: 1055135 1142191 1142192 1142193 1142206 1142299
Changes:
vkd3d (2.0+ds-2) unstable; urgency=medium
.
[ Simon McVittie ]
* d/control: Add missing dependency libvkd3d-headers -> libvulkan-dev.
* d/tests/control: Add missing dependencies for -dev test (Closes: #1142191).
* d/tests/libvkd3d-dev: Use cross-compile-friendly executable names.
.
[ Stephen Kitt ]
* Limit builds to supportable architectures
(Closes: #1142192, #1142193, #1142206, #1142299).
* Build on loong64 (Closes: #1055135).
Checksums-Sha1:
009fa48024d57e93ea12bc5485f6e751e3d002ff 2993 vkd3d_2.0+ds-2.dsc
339876145b6b9cf93d6f0040adeb4b87578d4f68 11708 vkd3d_2.0+ds-2.debian.tar.xz
65cc82c444fcccdbda20215a7a6dc8505730c232 6933 vkd3d_2.0+ds-2_source.buildinfo
Checksums-Sha256:
fc87d075f2328f57492ecbca1b6691ccb35d13164cc61a4410ebb1f5fc94c483 2993
vkd3d_2.0+ds-2.dsc
0a028e6c9db08d2f57f303343b32222cc83cd675f115c8705b3c104497f68a1f 11708
vkd3d_2.0+ds-2.debian.tar.xz
0a2b8d6ac223fb47392d5742594b6f861cf11e533ce06f3dedd537c12c44327a 6933
vkd3d_2.0+ds-2_source.buildinfo
Files:
0a8534eeecd0c04f84bdc5f42e1c6aca 2993 libs optional vkd3d_2.0+ds-2.dsc
86ce189af23fe5e355d7c1258dfa509c 11708 libs optional
vkd3d_2.0+ds-2.debian.tar.xz
7bfb202298eb3cd16005993e32612305 6933 libs optional
vkd3d_2.0+ds-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmp3S0wACgkQgNMC9Yht
g5xZyg//QXeqH0a8yd9Nhrad19eakx7gkIdLl28mW3nPJDCCevQwZphWMnHJKZdt
+MgVrOITYVugsESQsKImrMWJWq7HSjrHO187bVAmsCP/OWr8VKansjMvUgr041ZD
85diosGS8W/sGauMRZCMohLHXKe5NODfNg3+5ZbzJz4Kq/yqxKnIVioQc4wA2XI4
LKAq8avk8NYKH+IjKVTc/MhiCDJRBWv7X2toXq/jLu/P5VgNT4rTgK+vq0S2EB54
HdC0ZNuJLNKBh1ZUHFqb6FBUzCkPpKewhe8k0NnG1C2Q7vCa206ZGkQ8yIs+m9KN
agR7QAtwgx8XMzS9ofy864pGxjSRlwdA3U40a+iZCwciZMMRPKc+u4h0eQLXdItR
NjToy/RgEYwAr+Oqz/iZHHssnFR1wQWNF/ASdPLGhTBDM//hGswZNZhHaduvI55A
IWSMd+fpnfOZkPWIgk4Mj/609r8FUjoEjbWWqk7Y/KpcjhGyJbNoTTq9vPrpemwY
RpX3JSWJZ2R9u2/kWEV+KBsY/2auMF+p7M5edTJypow/Koaywx2qVuurVc+8DSt7
JFTfjJjINpkItfqefn9qKZXJPZPE6hgKM5WWxHhQ3urFmWM24SkrSmZtfe1Fbsn2
kgHGg4KCVoXDfxFyw6xnR4nB1k/YMonInuTlEU6FW0jYfosWVao=
=TBY9
-----END PGP SIGNATURE-----
pgpjh6Wh39GuJ.pgp
Description: PGP signature
--- End Message ---
