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

[Bug 59815] New: damavand/vk vsir_program_remap_output_signature input_mask check fails too early causing much less rendering than able just by continuing
by WineHQ Bugzilla June 8, 2026

June 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=59815 Bug ID: 59815 Summary: damavand/vk vsir_program_remap_output_signature input_mask check fails too early causing much less rendering than able just by continuing Product: vkd3d Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d-shader Assignee: wine-bugs(a)list.winehq.org Reporter: wineryyyyy(a)gmail.com Distribution: --- Created attachment 81073 --> http://bugs.winehq.org/attachment.cgi?id=81073 Screenshots of Witcher mostly blackscreen vs mostly rendered by not failing too early Allowing vsir_program_remap_output_signature() to proceed instead of returning for unhandled input_masks often results in much more rendering. Witcher screenshots attached showcase this which has also been encountered for other games: https://bugs.winehq.org/show_bug.cgi?id=54372#c9 https://bugs.winehq.org/show_bug.cgi?id=50182 Failing early makes errors much more obvious for unhandled cases which may useful for dev purposes on the one hand but on the other hand seems more misleading and less informative than continuing rendering which often reveals more about what actually is failing such as the case of the witcher which clearly shows that the menu is actually what is unhandled rather than most of the rest of the game which renders nearly consistent with WINED3D/gl. Often splash screens, intro videos, and/or start menus are only unhandled but unclear those in particular have bugs when everything is rendered the same blackscreen. Having DAMAVAND/vk renderer able to render as much as it is able allows it to be used more reliably as a dev tool for comparison with WINED3D/gl when debugging game bugs. -- 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 7

[Bug 59651] New: Greenfish Icon Editor errors on launch with MDB error: Input/Output error
by WineHQ Bugzilla June 7, 2026

June 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=59651 Bug ID: 59651 Summary: Greenfish Icon Editor errors on launch with MDB error: Input/Output error Product: Wine Version: 11.6 Hardware: x86-64 URL: https://greenfishsoftware.org/gfie.php OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tobbi.bugs(a)googlemail.com % ./wine --version wine-11.6-112-g504683b22d3 % openssl sha256 gfie4.5.zip SHA2-256(gfie4.5.zip)= 7cc9b150b3e09e1d59b162fc5aa1073387c91003f1dd6e75749067ae4af3f533 Steps to reproduce: 1. Extract the zip file and start gfie.exe using wine. Expected results: Program starts. Actual results: Error message: MDB error: Input/Output error. -- 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 8

[Bug 59832] New: Virpil Joysticks Sometimes Not Detected
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59832 Bug ID: 59832 Summary: Virpil Joysticks Sometimes Not Detected Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: sour.bead7396(a)fastmail.com Distribution: --- Sometimes when I start up *Star Citizen* in Wine, my joysticks aren't detected by the game. When this happens, wine control joy.cpl has no devices listed. I have verified that my devices are still attached on USB, they are visible in the KDE options and in the hidraw devices in the Linux system tree. For reference, the devices are: ID 3344:8198 Leaguer Microelectronics (LME) L-VPC MongoosT-50CM3 ID 3344:40cb Leaguer Microelectronics (LME) R-VPC Stick WarBRD ID 3344:80cb Leaguer Microelectronics (LME) L-VPC Stick WarBRD After upgrading to Wine 11.9, I started having this issue, and it continued with 11.10. Thank you for your time, and thank you for all your work producing this excellent software. -- 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 1

[Bug 59831] New: Zombie Army 4: Dead War running launcher leads to a memory leak
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59831 Bug ID: 59831 Summary: Zombie Army 4: Dead War running launcher leads to a memory leak Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com CC: zzhang(a)codeweavers.com Regression SHA1: 29ef555d2749e95eca67fe2fbf4d06d2f83b91c2 Distribution: --- Output has lots of '0258:err:seh:user_callback_handler ignoring exception c0000005' Mentioned commit makes the window be a white (bug 51825) and in the same time brings a memory leak. Just run the launcher and see the memory usage with system monitor. -- 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 0

[Bug 59828] New: Windows 7 calculator not running (unimplemented function COMCTL32.dll.392)
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59828 Bug ID: 59828 Summary: Windows 7 calculator not running (unimplemented function COMCTL32.dll.392) Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: comctl32 Assignee: wine-bugs(a)list.winehq.org Reporter: Cristiangaurii(a)gmail.com Distribution: --- Created attachment 81101 --> http://bugs.winehq.org/attachment.cgi?id=81101 output of running in terminal (wine calc1.exe), and the backtrace After merging the .mui with the .exe using Resource Hacker, the calculator that came with windows 7, and downloaded from https://win7games.com/#calc, does not open -- 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 1

[Bug 59827] New: winedbg: Ctrl-C segfaults 32-bit deguggees in new WoW64 mode
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59827 Bug ID: 59827 Summary: winedbg: Ctrl-C segfaults 32-bit deguggees in new WoW64 mode Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winedbg Assignee: wine-bugs(a)list.winehq.org Reporter: lahvuun(a)gmail.com Distribution: Gentoo Running a 32-bit executable with winedbg and hitting Ctrl-C to break results in a segfault. Doing the same in old WoW64 mode with WINEARCH=win32 works correctly. Seems to affect all 32-bit programs. A working workaround is to send SIGTRAP to the process manually, e.g. `kill -SIGTRAP $(pgrep test.exe)`. Reproducible with: #include <stdio.h> int main(void) { for (;;) { printf("test\n"); } } $ i686-w64-mingw32-gcc test.c -o test.exe $ WINEDEBUG=-all winedbg test.exe WineDbg starting on pid 0134 0x0000007bfa4686 ntdll+0x64686: movl -0x58(%ebp), %eax Wine-dbg>c Ctrl-C: stopping debuggee Unhandled exception: page fault on execute access to 0xfff4109c in wow64 32-bit code (0x000000fff4109c). -- 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 59803] New: Program crash on debugger interrupt in wow64 mode
by WineHQ Bugzilla June 6, 2026

June 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59803 Bug ID: 59803 Summary: Program crash on debugger interrupt in wow64 mode Product: Wine Version: 11.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)list.winehq.org Reporter: wine(a)tomashu.dev Distribution: --- Created attachment 81045 --> http://bugs.winehq.org/attachment.cgi?id=81045 backtrace Distro: CachyOS When debugging a 32-bit program in wow64 mode, trying to interrupt its execution with Ctrl+C causes it to crash. As an example, let's take wine's `notepad.exe` as it has both 64 and 32 bit versions. Steps to reproduce: 1. change directory to <wine_prefix>/drive_c/windows 2. launch 32bit version: `winedbg syswow64/notepad.exe` 3. continue program execution (with `c`) 4. interrupt the program (with `Ctrl+C`) 5. the program crashes. The window still exists, but is not responsive. 6. Exit debugger (with `quit`) Repeating the same steps but with 64 bit version does not result in a crash 2. launch 64bit version: `winedbg system32/notepad.exe` Interestingly, when launching e.g. `syswow64/regedit.exe`, the UI doesn't become unresponsive after the crash and continues to work. Maybe its related to multithreading? -- 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 59821] New: World of Tanks: Certain keys are not registered (Enter, Delete...)
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59821 Bug ID: 59821 Summary: World of Tanks: Certain keys are not registered (Enter, Delete...) Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: public_registrations(a)drax.biz Distribution: --- When typing in chat I can type letters and spaces but pressing Enter or Backspace keys does not work (message is not sent or letters are not getting deleted). Keyboard used to work fine up to version 11.6. Since version 11.7 it is not working correctly (as described). I tested version 11.7, 11.8, 11.9 and 11.10, they are all affected by this bug (reverting to 11.6 is only solution). -- 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 3

[Bug 59811] New: RDR2 (Red Dead Redemption 2) fails to initialize graphics device (Error Code 18) since 11.10
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59811 Bug ID: 59811 Summary: RDR2 (Red Dead Redemption 2) fails to initialize graphics device (Error Code 18) since 11.10 Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: DANIELE.AMODEO(a)OUTLOOK.COM Distribution: --- Red Dead Redemption 2 fails to launch with "Error Code 18: failed to initialize graphics device" since upgrading Wine Staging from 11.9 to 11.10. Downgrading back to Wine Staging 11.9 immediately resolves the issue. System: - OS: Arch Linux - GPU: AMD Radeon RX 6950 XT - Driver: RADV Mesa 26.1.1 - Wine mode: wow64 (64-bit prefix) - DXVK and VKD3D installed via winetricks - Graphics API set to kSettingAPI_DX12 in system.xml Steps to reproduce: 1. Install Wine Staging 11.10 2. Launch Red Dead Redemption 2 via Wine 3. Error Code 18 appears immediately, game does not start Expected: game launches normally (as it did with 11.9) Actual: "Rockstar Games failed to initialize graphics device. Error Code: 18" Suspected cause: dcomp-DCompositionCreateDevice2 patches introduced in 11.10. -- 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 5

[Bug 59817] New: RScript launches with an error screen
by WineHQ Bugzilla June 5, 2026

June 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59817 Bug ID: 59817 Summary: RScript launches with an error screen Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: timoffui(a)gmail.com Distribution: --- Created attachment 81079 --> http://bugs.winehq.org/attachment.cgi?id=81079 a file with detailed information of the specified bug For those who do not know what RScript is, here is a link: https://rangers.fandom.com/ru/wiki/RScript?so=search (The website is in russian, you need to use a translator to be able to read it). The first launch is fine, but after that the wine program error window shows up that states that the program has encountered a serious problem and needs to close. I've attached a backtrace file below. By the way my version of WIne is 11.0(Staging) because i don't know how to specify that. Thank you. -- 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 3