March 2025 - Wine-Bugs - list.winehq.org

[Bug 45483] New: Installation of the DirectX 8.1 SDK fails due to msi custom action failure
by wine-bugs＠winehq.org Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=45483 Bug ID: 45483 Summary: Installation of the DirectX 8.1 SDK fails due to msi custom action failure Product: Wine Version: 3.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: mstefani(a)winehq.org Distribution: --- Created attachment 61838 --> https://bugs.winehq.org/attachment.cgi?id=61838 +msi,+msiexec,+pid debug output The DirectX 8.1 SDK fails to install due msi custom action errors: 006b:006c:err:msiexec:custom_action_server Failed to create custom action server pipe: 231 setup.exe shows "Error: -1603 Fatal error during installation." Steps to reproduce: DX81b_SDK.exe with SHA1: 221c60334da54e8e670741e7090e51255ad0284c MD5: 0ef4637b05b77ae8f75d58e17f0e7d6d DX81b_SDK.exe is a self extracting zip file. cd to the extracted directory and run: wine DXF/setup.exe (Changing to the DXF directory and then wine setup.exe makes no difference). Go through the steps and during the install at 0% a message box with the above error pops up. I'm attaching the +msi,+msiexec,+pid output -- 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.

4 10

[Bug 54626] New: Saving files in Microsoft Word/Excel 2010 creates useless shortcut files
by WineHQ Bugzilla Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=54626 Bug ID: 54626 Summary: Saving files in Microsoft Word/Excel 2010 creates useless shortcut files Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Here follows a new bug report regarding the problem observed in old bug report 15480. It was told me that I should open a new bug report. ;-) Okay, the issue regarding the creation of useless shortcut files is back in Wine 8.0 (stable). When I open a *.xlsx file at the desktop and save it (with the same name) to an *.ods file then Excel 2010 will create two files. One is a *.lnk (which points to the original xlsx) and the other is a shortcut regarding the ods file but also with *.ods ending. As mentioned, both of them are non-functional. -- 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 54425] New: user32:clibpoard - test_string_data_process() fails on Windows in mixed locales
by WineHQ Bugzilla Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=54425 Bug ID: 54425 Summary: user32:clibpoard - test_string_data_process() fails on Windows in mixed locales Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:clibpoard - test_string_data_process() fails on Windows in mixed locales: clipboard.c:2351: Test failed: 7: wrong size 2 / 3 clipboard.c:2352: Test failed: 7: wrong data "a\x00", expected "\x83\xbf\x00" 1020:clipboard: 7 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped. clipboard.c:231: 2 failures in child process clipboard.c:2351: Test failed: 8: wrong size 3 / 5 clipboard.c:2352: Test failed: 8: wrong data "a\xdf\x00", expected "\x83\xbf\x83\xc0\x00" 2024:clipboard: 7 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped. clipboard.c:231: 2 failures in child process clipboard.c:2351: Test failed: 9: wrong size 3 / 5 clipboard.c:2352: Test failed: 9: wrong data "a\xdf\x00", expected "\x83\xbf\x83\xc0\x00" 1a7c:clipboard: 7 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped. clipboard.c:231: 2 failures in child process clipboard.c:2351: Test failed: 10: wrong size 4 / 7 clipboard.c:2352: Test failed: 10: wrong data "a\xdf?\x00", expected "\x83\xbf\x83\xc0\x83\xc1\x00" 1538:clipboard: 7 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped. clipboard.c:231: 2 failures in child process clipboard.c:2351: Test failed: 11: wrong size 4 / 7 clipboard.c:2352: Test failed: 11: wrong data "a\xdf?\x00", expected "\x83\xbf\x83\xc0\x83\xc1\x00" 05bc:clipboard: 7 tests executed (0 marked as todo, 0 as flaky, 2 failures), 0 skipped. clipboard.c:231: 2 failures in child process See https://test.winehq.org/data/patterns.html#user32:clipboard The failures happen in the w10pro64-mx-MX test configuration. What's special about it is that it uses a mix of locales: SystemDefaultLCID 0411 UserDefaultLCID 040c ThreadLocale 0411 SystemPreferredUILanguages 0412,0409 UserDefaultUILanguage 0412 ThreadUILanguage 0412 Country 231 ACP 932 The failures started happening with the commit below: commit 605ecafa67a4e034328b69396581e2f9b60d7af3 Author: Francois Gouget <fgouget(a)codeweavers.com> Date: Wed Dec 21 18:48:29 2022 +0100 user32: Fix a SetClipboardData() buffer overflow. Wine would append a correctly aligned NUL Unicode character to terminate the string but overflow the buffer by one byte for odd-sized strings. Windows instead overwrites the last two buffer bytes with a NUL Unicode character which ends up being misaligned for odd-sized strings. The clipboard data has a size field anyway so match the Windows behavior. Tweak the tests to show that SetClipboardData() can overwrite half of the Unicode string's last character. -- 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 46033] New: Execution of commands that contain special symbols will be truncated.
by wine-bugs＠winehq.org Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=46033 Bug ID: 46033 Summary: Execution of commands that contain special symbols will be truncated. Product: Wine Version: 3.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: yanjie875077968(a)gmail.com Distribution: --- when i use the wine cmd, i find same command can't be run, but it can be run in winxp cmd. ➜ temp wine cmd Wine CMD Version 5.1.2600 (1.6.2) Z:\tmp\temp>dir_ny Volume in drive Z has no label. Volume Serial Number is 0000-0000 Directory of Z:\tmp\temp File not found. Z:\tmp\temp>./dir_ny Z:\tmp\temp>dir . Volume in drive Z has no label. Volume Serial Number is 0000-0000 Directory of Z:\tmp\temp 10/22/2018 4:50 PM <DIR> . 10/22/2018 4:50 PM <DIR> .. 10/22/2018 4:50 PM 471,040 cmd1.exe 10/22/2018 4:50 PM 7 dir_ny.bat 2 files 471,047 bytes 2 directories 9,204,056,064 bytes free Z:\tmp\temp>exit ➜ temp wine cmd1 Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. Z:\tmp\temp>dir_ny fixme:process:CmdBatNotification 1 Z:\tmp\temp>dir . Volume in drive Z has no label. Volume Serial Number is 0000-0000 Directory of Z:\tmp\temp 10/22/2018 04:50 PM <DIR> . 10/22/2018 04:50 PM <DIR> .. 10/22/2018 04:50 PM 471,040 cmd1.exe 10/22/2018 04:50 PM 7 dir_ny.bat 2 File(s) 471,047 bytes 2 Dir(s) 9,204,056,064 bytes free fixme:process:CmdBatNotification 0 i review the cmd code in version 3.18. there is a bug in line 1318. while (IsCharAlphaNumericW(whichcmd[count])) { the IsCharAlphaNumericW function not include "_", so when a command include a "_" will be truncated. -- 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 4

[Bug 56932] New: Null pointer dereference in MiniDumpWriteDump
by WineHQ Bugzilla Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=56932 Bug ID: 56932 Summary: Null pointer dereference in MiniDumpWriteDump Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: madebr(a)gmail.com Distribution: --- Created attachment 76754 --> https://bugs.winehq.org/attachment.cgi?id=76754 Program Error details When using sdlprocdump [1] to get a minidump and stackframe of a crashing program, wine segfaults inside DbgHelp.MiniDumpWriteDump. I've attached the error when running the following crashing programming under sdlprocdump.exe. ``` int main(int argc, char *argv[]) { return argc / (argc - 1); } ``` sdlprocdump usage: ``` wine sdlprocdump.exe a.exe ``` [1] https://github.com/libsdl-org/SDL/blob/main/test/win32/sdlprocdump.c -- 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 57570] New: Syntax Error in CMD Batch Parsing
by WineHQ Bugzilla Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=57570 Bug ID: 57570 Summary: Syntax Error in CMD Batch Parsing Product: Wine-staging Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juan3(a)yandex.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 77673 --> https://bugs.winehq.org/attachment.cgi?id=77673 running wine cmd When attempting to run the `msys2_shell.cmd` script from MSYS2, Wine fails with a syntax error: `Syntax error: unexpected IN`. This issue occurs during the batch file parsing phase. 1. Download the MSYS2 base archive from the following link: ``` https://github.com/msys2/msys2-installer/releases/download/2024-12-08/msys2… ``` 2. Extract the archive to a directory, e.g., `Z:\msys2\msys64`. 3. Navigate to the extracted directory: ``` Z:\msys2\msys64> ``` 4. Run the `msys2_shell.cmd` script with the following arguments: ``` msys2_shell.cmd -here -defterm -no-start ``` 5. Observe the error: ``` Syntaxfehler Syntax error: unexpected IN ``` The `msys2_shell.cmd` script should execute without errors and launch the MSYS2 shell environment. Wine fails with a syntax error: `Syntax error: unexpected IN`. -- 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 7

[Bug 52373] New: White Band on Screen in Call of Cthuhlu
by WineHQ Bugzilla Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=52373 Bug ID: 52373 Summary: White Band on Screen in Call of Cthuhlu Product: Wine Version: 7.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matthewcboyd(a)tutanota.com Distribution: --- Created attachment 71571 --> https://bugs.winehq.org/attachment.cgi?id=71571 Picture of Band Call of Cthulhu launches to a black screen with a white band on it. -- 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 57927] New: Sony Vegas 13 no longer starts
by WineHQ Bugzilla Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=57927 Bug ID: 57927 Summary: Sony Vegas 13 no longer starts Product: Wine Version: 10.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- Starting from 9e9e894a76582063119f4a9004e8f3a346ad97e8 in 10.0-rc1, Sony Vegas 13 freezes the moment the splash screen appears and doesn't show any loading progress. Additionally, although this is an issue that I couldn't manage to bisect due to how inconsistent it is, is that ever since Wine 9.22, the moment it hits the stage of "Initializing external monitoring..." during loading, Vegas may freeze Wine, causing me to have to SIGKILL every process manually. It may provide an assertion of the following: "Fatal glibc error: pthread_mutex_lock.c:460 (__pthread_mutex_lock_full): assertion failed: robust || (oldval & FUTEX_OWNER_DIED) == 0" Unfortunately, I don't think I can provide good reproduction instructions as Sony Vegas 13 is paid software, although I think the installer may have a trial. -- 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 57839] New: Black rects appear briefly during window drawing
by WineHQ Bugzilla Dec. 16, 2025

Dec. 16, 2025

https://bugs.winehq.org/show_bug.cgi?id=57839 Bug ID: 57839 Summary: Black rects appear briefly during window drawing Product: Wine Version: 10.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: msuhoruki(a)gmail.com Distribution: --- I've noticed Wine 9.x started producing a visual artifact when opening dialogs, navigating menus, bringing windows to the foreground. The effect appears like a black area, displayed very briefly just before the actual content is drawn. I think this has started somewhere with 9.x and I don't see this black flash effect in Wine 8.0. It seems every time there is some activity on the window area the affected region is "blanked" out momentarily before the GUI is drawn. Using Wine 10.1 on Xorg with amdgpu and Trinity desktop. Xfce 4.12 shows same problem. Is there some redraw frequency I can tweak to fix this? The effect sounds minor but gets really jarring fast. -- 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 1

[Bug 57954] New: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device
by WineHQ Bugzilla Dec. 15, 2025

Dec. 15, 2025

https://bugs.winehq.org/show_bug.cgi?id=57954 Bug ID: 57954 Summary: Watch_Dogs black splash screen 10.3 rawinput:add_device Failed to open device Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- Created attachment 78201 --> https://bugs.winehq.org/attachment.cgi?id=78201 wd-winedbg 10.2 seems to work fine, 10.3 gives an error about rawinput and the splash screen that should have the main character and game title is a black box and hangs using wow64 build, other 32bit games seem to work fine. running with WINEDBEUG ends in multiple varying lines of `0158:warn:rawinput:add_device Failed to open device file L"\\??\\HID#some-device-name#{hex-hash-id}", status 0xc0000034.` -- 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 17