December 2024 - Wine-bugs - list.winehq.org

[Bug 53751] New: RollerCoaster Tycoon 1-2: rename dialog is hidden behind game screen
by WineHQ Bugzilla 20 Dec '25

20 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=53751 Bug ID: 53751 Summary: RollerCoaster Tycoon 1-2: rename dialog is hidden behind game screen Product: Wine Version: 6.1 Hardware: x86-64 URL: https://archive.org/download/RollerCoasterTycoon2Demos /RCT2_Demo.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 4ce1d7f93a35322d149cbde29d619e2580159a80 Distribution: --- Created attachment 73216 --> https://bugs.winehq.org/attachment.cgi?id=73216 What it looked like the last time it worked When you click on an attraction or person in RollerCoaster Tycoon 1 & 2 you can rename the object. A standard windows text-box should open in the upper-left corner of the screen letting you input a new name for that object. This text window is hidden behind the game screen when it is opened thus it is inaccessible/not usable. Tried with virtual desktop mode and fullscreen: both have the same issue. Nothing obvious appears in the terminal. Last version when it worked: Wine-6.0. Bisecting revealed commit 4ce1d7f93a35322d149cbde29d619e2580159a80 was the culprit. Can't revert it on current Wine but the rename window appears properly with the previous commit. Steps to reproduce in RCT 2 demo: Start a new game with the left-most icon at the bottom, select either "Crazy Castle" or "Six Flags Belgium" scenario. Left-click on an object to open an information window, select the rename icon (looks like a brownish name-tag). A text-box is opened but it is placed behind the game screen. RCT2_Demo.exe (69M) md5: 2d07a92c72ed5077a933ec9bf395f4d2 Still present in wine-7.18-120-g001665d7354. Xfwm4 version 4.16.1 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03 OpenGL core profile shading language version string: 4.60 NVIDIA -- 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 47624] New: Application crashes in socket communication (Regression)
by wine-bugs＠winehq.org 19 Dec '25

19 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=47624 Bug ID: 47624 Summary: Application crashes in socket communication (Regression) Product: Wine Version: 4.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mnemotron(a)gmail.com Distribution: --- Created attachment 65058 --> https://bugs.winehq.org/attachment.cgi?id=65058 Wine debug log +relay,+ntdll,+winsock For several years we've been using Wine 1.7.18 on Lubuntu 13 (Linux 3.11.10) with a proprietary 32-bit Windows application programmed in Delphi. It is installed on small embedded PCs with AMD Geode LX processors at 500 MHz and 1 GB RAM and we have about 100 of these machines. After upgrading a test machine to newer Linux distributions and Wine 4.x the application crashes in its network functions. When booting the same hard drive via USB on a modern PC everything works, so the bug might be driver related. (But it works on the older kernel!) The basic error is this (Wine 4.13 devel): 340728.035:0008:0009:Ret KERNEL32.GetProcAddress() retval=7db174ac ret=0041615c 340728.035:0008:0009:Call ws2_32.shutdown(000000dc,00000001) ret=0067ba05 340728.035:0008:0009:Call ntdll.wine_server_handle_to_fd(000000dc,00000000,0033fac8,0033fac4) ret=7db246cb 340728.035:0008:0009:Ret ntdll.wine_server_handle_to_fd() retval=00000000 ret=7db246cb 340728.035:0008:0009:trace:winsock:WS_shutdown socket 00dc, how 0x1, options 0x0 340728.035:0008:0009:trace:winsock:WS2_register_async_shutdown socket 00dc type 2 340728.036:0008:0009:Call ntdll.RtlAllocateHeap(00110000,00000000,00000018) ret=7db1a77a 340728.036:0008:0009:Ret ntdll.RtlAllocateHeap() retval=001be6c0 ret=7db1a77a 340728.036:0008:0009:err:seh:setup_exception_record nested exception on signal stack in thread 0009 eip 7bca93b9 esp 7ffdbae0 stack 0x242000-0x340000 Winedbg does not work. When attaching to the Windows process, the application crashes and Winedbg says "Can't attach to process ... Error 5". Running the application in Winedbg directly generates the above error message plus "Process of pid=xxxx has terminated". There is no backtrace, the thread dies completely. I have tried various Linux distributions using 4.x kernels (Bodhi Linux 5, Linux Mint Debian Edition 3, Debian 9.9, Debian 10, Ubuntu 16.04) and also tried Wine 2.0.2, which is the oldest available binary package, and everytime the above error occurs. Building a custom Linux kernel for the machine also didn't change anything. Trying to build Wine 1.7.18 on Debian 10 resulted in several compile time errors that I am not able to fix, so I am stuck with available binary packages. Debugging and changing the Windows application itself managed to move the crash from the first network connect to when the application is shutdown. Only widely available network component libraries for Delphi were used (Indy and ICS), there is no self-developed net code. So, the same Windows executable works with Wine 1.7.13 on Linux 3.11, but it crashes in Wine 4.x (I tried several packages from Ubuntu and Debian from winehq) on modern 4.x Linux kernels on this machine. Any ideas? I'm ready to provide more needed info. Thomas -- 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 45483] New: Installation of the DirectX 8.1 SDK fails due to msi custom action failure
by wine-bugs＠winehq.org 19 Dec '25

19 Dec '25

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 19 Dec '25

19 Dec '25

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 19 Dec '25

19 Dec '25

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 19 Dec '25

19 Dec '25

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 19 Dec '25

19 Dec '25

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 19 Dec '25

19 Dec '25

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 19 Dec '25

19 Dec '25

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 57600] New: Application not showing console output
by WineHQ Bugzilla 15 Dec '25

15 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57600 Bug ID: 57600 Summary: Application not showing console output Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: angel.narvaez(a)civiceye.com Distribution: --- Created attachment 77715 --> https://bugs.winehq.org/attachment.cgi?id=77715 wine8 vs wine9 I'm running into an issue where an application that can be started from explorer.exe or cmd.exe is not showing the console output to the unix console. The "buggy" behavior is present in wine v9, but wine v8 shows the console output just fine. I believe the related change is in this commit: https://gitlab.winehq.org/wine/wine/-/commit/4b63e888945b8ada2ddc043e435b93… In the commit, it is stated that this behavior can be achieved by starting the app with "./wine app | cat", however that does not seem to be working with wine or wineconsole (Please see attachments) When using WINEDEBUG=+console, I can see the application interacting and writing to the windows console, however nothing is shown on the screen. I need guidance on this issue. -- 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