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

[Bug 20482] New: Tunnelier Win32 SSH client shows a very tall dialog upon exiting
by wine-bugs＠winehq.org July 22, 2026

July 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=20482 Summary: Tunnelier Win32 SSH client shows a very tall dialog upon exiting Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: christianuceda(a)yahoo.com Created an attachment (id=24385) --> (http://bugs.winehq.org/attachment.cgi?id=24385) Anomalous confirmation dialog Tunnelier is a nice Win32 SSH graphical client. Get the software from: $wget http://dl.bitvise.com/Tunnelier-Inst.exe Then install: $wine Tunnelier-Inst.exe To run it: $wine tunnelier to reproduce the bug just log into any ssh enabled server, the console and the SFTP window will open automatically after logging in. Then click on exit, a requester stating that there is a session running will appear asking for exit confirmation. This confirmation dialog is anomalous, the text on it appears like a tall vertical column. See attached capture. -- 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 25

[Bug 58139] New: Empires: crashes on pressing "GO!" button
by WineHQ Bugzilla July 22, 2026

July 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=58139 Bug ID: 58139 Summary: Empires: crashes on pressing "GO!" button Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: contact(a)giganttech.net Distribution: ArchLinux Created attachment 78420 --> http://bugs.winehq.org/attachment.cgi?id=78420 Archive containing backtrace and terminal output Download Link: https://conspiracy.hu/get/74/cns!empf.zip Trying to run this demoscene by clicking the "GO!" button on the will result in a crash. NVIDIA GeForce GTX 1660 SUPER with proprietary drivers, Driver Version: 570.133.07 -- 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 56950] New: SRB2 Zone Builder throws exception when creating a new map (shader fails to compile with "E5000: syntax error, unexpected '<', expecting ';' or ','")
by WineHQ Bugzilla July 22, 2026

July 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=56950 Bug ID: 56950 Summary: SRB2 Zone Builder throws exception when creating a new map (shader fails to compile with "E5000: syntax error, unexpected '<', expecting ';' or ','") Product: vkd3d Version: 1.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 76766 --> https://bugs.winehq.org/attachment.cgi?id=76766 WINEDEBUG=+d3dcompiler Steps to reproduce: 1. Install and run Zone Builder from Zone_Builder_v3.0-rc3_Setup.exe 2. Click the Close button on the first error dialog 3. Click the New Map button, then OK and Yes A .NET exception dialog appears that says "CompilationException while loading effect display2d.fx: <anonymous>:35:1: E5000: syntax error, unexpected '<', expecting ';' or ','". The shader that fails to compile is https://git.do.srb2.org/STJr/ZoneBuilder/-/blob/e74f44adcf58669813059db161f… `winetricks d3dx9_43 d3dcompiler_43 micross` resolves the problem. First reported at https://mb.srb2.org/threads/another-zone-builder-error-on-wine.42640/ $ sha256sum Zone_Builder_v3.0-rc3_Setup.exe 4776d485ab32b3ae57dd01154d28ce5bccbe898b35002802c6451b4ba7c39cf0 -- 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 59303] New: FlatOut 2 has not yet implemented feature: Input mask 0xf reads components not written in output mask 0x3.
by WineHQ Bugzilla July 22, 2026

July 22, 2026

http://bugs.winehq.org/show_bug.cgi?id=59303 Bug ID: 59303 Summary: FlatOut 2 has not yet implemented feature: Input mask 0xf reads components not written in output mask 0x3. Product: vkd3d Version: 1.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 083c:fixme:d3d_shader:shader_spirv_compile_shader Shader log: 083c:fixme:d3d_shader:shader_spirv_compile_shader <anonymous>: E9000: Aborting due to not yet implemented feature: Input mask 0xf reads components not written in output mask 0x3. 083c:fixme:d3d_shader:shader_spirv_compile_shader 083c:err:d3d_shader:shader_spirv_compile_shader Failed to compile shader, ret -5. 083c:err:d3d:wined3d_context_vk_apply_draw_state No pipeline layout set. 083c:err:d3d:adapter_vk_draw_primitive Failed to apply draw state. vkd3d-1.18-211-gd9210a62 -- 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 11

[Bug 55011] New: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs
by WineHQ Bugzilla July 22, 2026

July 22, 2026

https://bugs.winehq.org/show_bug.cgi?id=55011 Bug ID: 55011 Summary: Cuda-application M/WarpEM got stuck or crashes in wine-staging/7.21, wine/8.9+nvidia-libs Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: nvcuda Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- M of WarpEM gets stuck very early and eventually crashes. The following steps are needed to reproduce this: 1) install WarpEM according to [1] into wine-staging between v7.17 and v7.21, or wine-8.9 with nvidia-libs. (do not try with wine-staging 7.22 or later, because that has cuda support disabled). This has been testing this with "Shared WoW64" configuration of Wine. Trying to use Wine with the "new WoW64 approach" using -enable-archs=i386,x86_64 did also not work for me, because it failed much earlier when trying to install Cuda/WarpEM. 2) Data (5.5TB!) for testing is available from here [1]. Download and unpack Warpem_test.tar.gz to a directory that is accessible from wine. The screenshots Step1-7 should help to understand how M is supposed to be used. 3) Start M.exe. In my case, I do this ulimit -s 655360 wine $WINEPREFIX/drive_c/Warp/M.exe or vglrun wine $WINEPREFIX/drive_c/Warp/M.exe 4) Within M, do the following steps (see also Step1-7 in [2]): - Step 1: In the GUI window click "LOAD EXISTING FROM FILE" - Step 2: select ...\M_j33\Gag_c2_processing.population - Step 3: Upper right corner Refine button. - Step 4: Click refine - Step 5+6: workers are now testing the memory - Step 7: Eventually (after several minutes), one of the works crash, and there is no further progress. On Windows, this finishes and a new screen appears for the next step. This is not the case here. It gets stuck, and and eventually I stopped wine with <ctrl-C>. A log file is also available [2], but it is too large (1.1 GB) to be included here. If you have suggestions with WINEDEBUG filter should be used, let me know. [1] https://appdb.winehq.org/objectManager.php?sClass=version&iId=40620&iTestin… [2] https://pub.ista.ac.at/~schloegl/warpem-test-data/ -- 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 58247] New: ABNT Keyboard Not Working Properly in Wine with Wayland Driver
by WineHQ Bugzilla July 21, 2026

July 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=58247 Bug ID: 58247 Summary: ABNT Keyboard Not Working Properly in Wine with Wayland Driver Product: Wine Version: 10.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: xnep1(a)hotmail.com Distribution: --- Created attachment 78588 --> http://bugs.winehq.org/attachment.cgi?id=78588 Tracefile with winedebug=keyboard,key showing "/" not working When running Wine applications using the Wayland driver, certain keys on the Brazilian ABNT2 keyboard (such as the slash /, question mark ?, and other special characters) do not function correctly. These keys either generate no character. In contrast, when using the X11 driver (wine X11), the same keys function as expected, and the correct characters are produced. Upon inspection, the scan codes received under Wayland are extended (e.g., 0x259 instead of 0x59 for the slash key), which seems to lead to incorrect mapping or interpretation by Wine. This issue appears to stem from incomplete or incorrect handling of extended scan codes or keyboard layout mapping for the br-abnt2 layout in the Wayland input. In my tests, I forced the correct scan code for the slash key (0x59), and after this adjustment, the key started working properly again. I have attached a trace log file showing the key input events during the failure. Although I am currently using a modified version of Wine to generate this trace, the problem also occurs on the stable Wine release. (It's late and I'm not going to redo the test just to have a clean trace file. Sorry.) -- 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 7

[Bug 59226] New: unimplemented function msvcp140_atomic_wait.dll.__std_tzdb_get_sys_info using the STL
by WineHQ Bugzilla July 21, 2026

July 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=59226 Bug ID: 59226 Summary: unimplemented function msvcp140_atomic_wait.dll.__std_tzdb_get_sys_info using the STL Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)list.winehq.org Reporter: winehq-bugzilla(a)asdff45.de Distribution: --- Created attachment 80130 --> http://bugs.winehq.org/attachment.cgi?id=80130 wine output when running the mentioned C++ code Using std::chrono::time_zone::to_local causes unhandled exception. Unhandled exception: unimplemented function msvcp140_atomic_wait.dll.__std_tzdb_get_sys_info called in 64-bit code (0x006fffffbfd817). The code i used to test this: #include <iostream> #include <chrono> int main() { std::cout << std::format("Encountered on: {:%F %T}", std::chrono::floor<std::chrono::seconds>(std::chrono::current_zone()->to_local(std::chrono::system_clock::now()))) << std::endl; return 0; } The crash happens in "to_local" which calls "_Get_info" which calls "__std_tzdb_get_sys_info". -- 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 54648] New: Call of Juarez needs "isnan" handling
by WineHQ Bugzilla July 21, 2026

July 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=54648 Bug ID: 54648 Summary: Call of Juarez needs "isnan" handling Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 0718:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0718:err:d3dcompiler:D3DCompile2 Shader log: 0718:err:d3dcompiler:D3DCompile2 <anonymous>:18:6: E5005: Function "isnan" is not defined. 1.6-195-g2880be64 -- 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 6

[Bug 24063] New: World in conflict fails to start in DX10 mode
by wine-bugs＠winehq.org July 21, 2026

July 21, 2026

http://bugs.winehq.org/show_bug.cgi?id=24063 Summary: World in conflict fails to start in DX10 mode Product: Wine Version: 1.3.1 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Created an attachment (id=30246) --> (http://bugs.winehq.org/attachment.cgi?id=30246) Log +d3d10 World in Conflict is unable to start in DX10 mode. Native dxdiagn.dll was used to avoid http://bugs.winehq.org/show_bug.cgi?id=11114 and sh winetricks d3dx10 was run too. I uploaded a +d3d10 log. If you need other debug channels, please ask. -- 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 15

[Bug 39394] New: Panic Room by Fairlight 64K scene demo crashes on start up
by wine-bugs＠winehq.org July 21, 2026

July 21, 2026

https://bugs.winehq.org/show_bug.cgi?id=39394 Bug ID: 39394 Summary: Panic Room by Fairlight 64K scene demo crashes on start up Product: Wine Version: 1.7.52 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Distribution: --- Created attachment 52508 --> https://bugs.winehq.org/attachment.cgi?id=52508 panic_room_by_fairlight.zip Perhaps because of this: "d3dcompiler:compile_shader Compilation target "tx_1_0" not yet supported" fixme:win:EnumDisplayDevicesW ((null),0,0x19ff8b8,0x00000000), stub! fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table fixme:d3dcompiler:compile_shader Compilation target "tx_1_0" not yet supported wine: Unhandled page fault on read access to 0x00000000 at address 0x4073f1 (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x004073f1). err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:004073f1 ESP:019ff93c EBP:019ff94c EFLAGS:00010286( R- -- I S - -P- ) EAX:00000000 EBX:00000001 ECX:019ff918 EDX:00000000 ESI:00000000 EDI:01a09fe8 Stack dump: 0x019ff93c: 019ff940 00000080 00000000 00000000 0x019ff94c: 019ffdd0 0040186a 01a09fe8 000005a0 0x019ff95c: 0012cbc8 00000000 5f34766e 70736964 0x019ff96c: 6c6c642e 00000000 00000000 00000000 0x019ff97c: 00000000 00000000 00000000 00000000 0x019ff98c: 00000000 00000000 00000000 00000000 Backtrace: =>0 0x004073f1 in flt_panic_room (+0x373f1) (0x019ff94c) 1 0x0040186a in flt_panic_room (+0x31869) (0x019ffdd0) 2 0x0040157a in flt_panic_room (+0x31579) (0x019ffde4) 0x004073f1: movl 0x0(%eax),%ecx Modules: Module Address Debug info Name (76 modules) PE 3d0000- 1226000 Export flt_panic_room ELF 7872d000-7a800000 Deferred libnvidia-glcore.so.355.06 ELF 7a800000-7a8f2000 Deferred opengl32<elf> -- 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 16