August 2026 - Wine-Bugs - list.winehq.org

[Bug 53978] New: d3dx9_*, d3dx10_* and d3dx11_* dlls missing on some TestBot VMs
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=53978 Bug ID: 53978 Summary: d3dx9_*, d3dx10_* and d3dx11_* dlls missing on some TestBot VMs Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The d3dx9_*, d3dx10_* and d3dx11_* dlls are missing on some TestBot VMs. Specifically: * w7pro64 Only runs the 64-bit tests which report that these dlls are missing (plus atl100, atl110 and d3d8). w7u runs the 32-bit tests and, surprisingly, does not report any of these dlls to be missing. Adding the missing dlls on w7pro64 probably is not worth it. * w1064v1507 missing the 32- and 64-bit dlls Not worth adding them. * w10pro64v2004 missing the 32- and 64-bit dlls Not worth adding them. * w11pro64 32- and 64-bit dlls -> Add them. w11pro64_nv actually had a couple of these before I fixed the Windows Update issue. It seems that they got installed for the NVIDIA GUI and did not get installed when I rebuilt the VM with just the NVIDIA driver. * fgtb-w10pro64-64 missing the 32- and 64-bit dlls Not a TestBot VM but add them anyway. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 31609] New: TestLauncher says a required DLL is missing, but the test runs fine without TestLauncher
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=31609 Bug #: 31609 Summary: TestLauncher says a required DLL is missing, but the test runs fine without TestLauncher Product: Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified http://source.winehq.org/git/tools.git/blob/HEAD:/testbot/src/TestLauncher/… has a function AllImportedDllsPresent() that tries to avoid running tests that implicitly link against DLLs that aren't present. Unfortunately, in the case of dlls with manifests, it reports it can't find dlls that are in fact present. What it needs is a good dose of the medicine that cured the same problem in winetest: http://www.winehq.org/pipermail/wine-cvs/2010-July/068410.html A quick test shows that this works. I'll send a patch soon. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

3 14

[Bug 59835] New: xinput: Xbox 360 controller detected as DirectInput instead of XInput since 11.1 (pdo_pnp code 0xc not implemented)
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59835 Bug ID: 59835 Summary: xinput: Xbox 360 controller detected as DirectInput instead of XInput since 11.1 (pdo_pnp code 0xc not implemented) Product: Wine-staging Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: albmm(a)live.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Summary: Since Wine Staging 11.1, Xbox 360 controllers are detected as DirectInput instead of XInput, causing the D-pad up direction to be permanently pressed. This is a regression from 11.0, where the controller works correctly. Steps to reproduce: Connect a Microsoft Xbox 360 Controller (045e:028e) via USB Launch any XInput game under Wine Staging 11.1 or later Open wine control — controller appears under DirectInput instead of XInput Expected behavior: Controller detected as XInput, as it was in Wine Staging 11.0 Actual behavior: Controller detected as DirectInput, D-pad up permanently pressed Debug output: fixme:xinput:pdo_pnp code 0xc, not implemented! fixme:xinput:pdo_pnp code 0xc, not implemented! System info: OS: Debian 13.5 + kernel 7.0.9 Kernel driver: xpad (working correctly) SDL2 i386: installed (2.32.4) Hardware: Microsoft Xbox 360 Controller (045e:028e) Regression: Works in 11.0, broken in 11.1 and later. Additional information: Testing with an Xbox One Wireless Controller connected via Bluetooth (kernel driver: uhid + hid_microsoft) shows that this device is correctly detected as XInput in Wine 11.1 and later. This suggests the regression is specific to the xpad USB driver path, and not a general issue with the XInput subsystem in Wine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 59654] New: FlatOut 2 needs combined sampler instruction "texreg2ar"
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59654 Bug ID: 59654 Summary: FlatOut 2 needs combined sampler instruction "texreg2ar" Product: vkd3d Version: 1.19 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: vkd3d-shader Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 05a0:err:d3d_shader:shader_spirv_scan_shader Failed to scan shader, ret -5. 05a0:fixme:d3d_shader:shader_spirv_scan_shader Shader log: 05a0:fixme:d3d_shader:shader_spirv_scan_shader <anonymous>:3:0: E9000: Aborting due to unimplemented feature: Combined sampler instruction "texreg2ar" (0x128). vkd3d-1.19-149-g7ecb7c52 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 52115] New: Horizon Zero Dawn crashes during loading
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=52115 Bug ID: 52115 Summary: Horizon Zero Dawn crashes during loading Product: vkd3d Version: 1.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Hello, I tried this game from GoG with vkd3d-git and it crashes during the 1st loading (see https://youtu.be/3qpdE9FUBQg) - The game works with vkd3d-proton without issue (https://youtu.be/MA3ehphVWsg) I attach the WINEDEBUG=+vkd3d VKD3D_DEBUG="trace" log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 13

[Bug 58510] New: Submitting new test results lists all versions of Wine
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=58510 Bug ID: 58510 Summary: Submitting new test results lists all versions of Wine Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Regression SHA1: a0e96bdcdbb5f3b950574685d9d9a66c9e9985a9 Distribution: --- Created attachment 78978 --> http://bugs.winehq.org/attachment.cgi?id=78978 HTML A recent change has made submitting a new test result list all versions of Wine, whereas before it was only the last few and the stable release. I'm guessing a0e96bdcdbb5f3b950574685d9d9a66c9e9985a9 may be the commit in question. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 29

[Bug 56508] New: Wine 9.1-9.5 - vkd3d component fails to compile.
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=56508 Bug ID: 56508 Summary: Wine 9.1-9.5 - vkd3d component fails to compile. Product: vkd3d Version: 1.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: jonfarr87(a)gmail.com Distribution: --- Attempting to compile Wine 9.1 up to 9.5 fails during vkd3d component. The error is present regardless if staging patches are applied or not. The issue wasn't up to Wine 9.0 I've tried GCC compilers 8.x up to 11.x but issue persists. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 8

[Bug 54983] New: Hearts of Iron IV crashes with 'Assertion failed: instr->reg.allocated' in DX11 mode
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54983 Bug ID: 54983 Summary: Hearts of Iron IV crashes with 'Assertion failed: instr->reg.allocated' in DX11 mode Product: vkd3d Version: 1.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 74522 --> https://bugs.winehq.org/attachment.cgi?id=74522 +d3dcompiler,+vkd3d Assertion failed: instr->reg.allocated, file ../vkd3d/libs/vkd3d-shader/tpf.c, line 3499 1.7-231-gea7d8c65 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 5

[Bug 54468] New: Separable Subsurface Scattering crashes due to HLSL syntax error 'unexpected KW_BLENDSTATE'
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54468 Bug ID: 54468 Summary: Separable Subsurface Scattering crashes due to HLSL syntax error 'unexpected KW_BLENDSTATE' Product: vkd3d Version: 1.6 Hardware: x86-64 URL: http://www.iryoku.com/separable-sss/downloads/Separabl e-SSS-DX10-v1.0.exe OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 00e4:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x800. 00e4:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 00e4:err:d3dcompiler:D3DCompile2 Shader log: 00e4:err:d3dcompiler:D3DCompile2 <anonymous>:1:116: E5000: syntax error, unexpected KW_BLENDSTATE 00e4:err:d3dcompiler:D3DCompile2 1.6-110-g240b2f96 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 51451] New: Many Windows 10 VMs are incompletely localized
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=51451 Bug ID: 51451 Summary: Many Windows 10 VMs are incompletely localized Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The localized w10pro64* VMs don't have the right UserDefaultLCID and are sometimes missing even more: w10pro64 fr_FR SystemDefaultLCID 040c UserDefaultLCID 0409 <--- should be 040c ThreadLocale 0409 ??? SystemPreferredUILanguages 040C,0409 UserDefaultUILanguage 040c ThreadUILanguage 040c w10pro64 ar_MA SystemDefaultLCID 0c01 UserDefaultLCID 0409 <--- should be 0c01 ThreadLocale 0409 ??? SystemPreferredUILanguages 0409 <--- should contain 0c01 UserDefaultUILanguage 0409 <--- should be 0c01 ThreadUILanguage 0409 <--- should be 0c01 w10pro64 he_IL UserDefaultLCID 0409 <--- should be 40d w10pro64 hi_IN Being a Unicode-only language means setting the system locale to Hindi was not possible in older Windows versions (up to early Windows 10). Now it is but it's considered Beta and uses the UTF-8 encoding in ANSI APIs. So it's not clear if it should be changed (and how to do it programmatically). SystemDefaultLCID 0409 <--- Unicode-only language UserDefaultLCID 0409 <--- should be 0439 ThreadLocale 0409 ??? SystemPreferredUILanguages 0439,0409 UserDefaultUILanguage 0439 ThreadUILanguage 0439 w10pro64 ja_JP UserDefaultLCID 0409 <--- should be 411 w10pro64 ko_KO UserDefaultLCID 0409 <--- should be 412 w10pro64 pt_BR UserDefaultLCID 0409 <--- should be 416 w10pro64 ru_RU UserDefaultLCID 0409 <--- should be 419 w10pro64 zh_CN UserDefaultLCID 0409 <--- should be 804 This prevents testing how Windows behaves when formatting and parsing their currencies in oleaut32:varformat for instance. Strangely enough the w7u* VMs don't have this issue: w7u de_DE SystemDefaultLCID 0407 UserDefaultLCID 0407 ThreadLocale 0407 SystemPreferredUILanguages 0407 UserDefaultUILanguage 0407 ThreadUILanguage 0407 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3