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

[Bug 34143] New: Window'ed Milkdrop 2 visual plug in doesn't work in WinAMP
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=34143 Bug #: 34143 Summary: Window'ed Milkdrop 2 visual plug in doesn't work in WinAMP Product: Wine Version: 1.6 Platform: x86 URL: http://download.nullsoft.com/winamp/client/winamp564_f ull_emusic-7plus_all.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: t.artem(a)mailcity.com Classification: Unclassified Created attachment 45409 --> http://bugs.winehq.org/attachment.cgi?id=45409 Windowed Milkdrop/Wine 1.6 Steps to reproduce - install Wine, run Milkdrop visualization. Its window will be empty. Native d3dx9_36.dll is required, otherwise it won't start. Console messages: fixme:win:EnumDisplayDevicesW ((null),0,0x24db8c8,0x00000000), stub! fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. -- 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 49

[Bug 59380] New: Nioh: The Complete Edition fails to reach the main menu
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59380 Bug ID: 59380 Summary: Nioh: The Complete Edition fails to reach the main menu Product: vkd3d Version: 1.18 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: vkd3d-shader Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com CC: fcasas(a)codeweavers.com Regression SHA1: 0dabfdee6393eb777dd025ff3d37968fb385f026 Distribution: --- Movie folder should be renamed due to bug 54682. vkd3d:08d4:err:vsir_dst_operand_io_normalise ../vkd3d/libs/vkd3d-shader/ir.c:4693: Unreachable code reached. vkd3d-1.18-295-gc121e9b1 -- 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 58517] New: Comments are broken
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=58517 Bug ID: 58517 Summary: Comments are broken Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php?sClass=vers ion&iId=252 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 Blocks: 43702, 58287 Distribution: --- >From https://appdb.winehq.org/objectManager.php?sClass=version&iId=252 : Error Message: Uncaught Error: Call to a member function objectMakeUrl() on null in /home/winehq/opt/appdb/include/comment.php:286 Stack trace: #0 /home/winehq/opt/appdb/include/comment.php(246): Comment->output_comment() #1 /home/winehq/opt/appdb/include/comment.php(478): Comment::view_app_comment() #2 /home/winehq/opt/appdb/include/comment.php(492): Comment::do_display_comments_nested() #3 /home/winehq/opt/appdb/include/comment.php(760): Comment::display_comments_nested() #4 /home/winehq/opt/appdb/include/version.php(1199): Comment::view_app_comments() #5 /home/winehq/opt/appdb/include/objectManager.php(1340): version->display() #6 /home/winehq/opt/appdb/objectManager.php(157): ObjectManager->view() #7 {main} thrown File: comment.php:286 -- 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 57686] New: Thief (2014) requires 'GroupMemoryBarrierWithGroupSync' support
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=57686 Bug ID: 57686 Summary: Thief (2014) requires 'GroupMemoryBarrierWithGroupSync' support Product: vkd3d Version: 1.14 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: --- 09b4:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 09b4:err:d3dcompiler:D3DCompile2 Shader log: 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:35:51: E5000: Invalid subscript "Length". 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:35:5: E5002: Can't implicitly convert from <error type> to int. 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:42:83: E5000: Invalid subscript "Length". 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:43:83: E5000: Invalid subscript "Length". 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:44:83: E5000: Invalid subscript "Length". 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:45:83: E5000: Invalid subscript "Length". 09b4:err:d3dcompiler:D3DCompile2 ..\..\Engine\\Shaders\Compute\DoFBlurBGCS.hlsl:46:1: E5005: Function "GroupMemoryBarrierWithGroupSync" is not defined. 09b4:err:d3dcompiler:D3DCompile2 1.14-278-ga082daeb -- 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 55080] New: Rayman Origins needs support for instruction type HLSL_IR_IF
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=55080 Bug ID: 55080 Summary: Rayman Origins needs support for instruction type HLSL_IR_IF 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: gijsvrm(a)gmail.com Distribution: --- 0024:err:d3dcompiler:D3DCompile2 <anonymous>:51:1: E5017: Aborting due to not yet implemented feature: Instruction type HLSL_IR_IF. -- 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 50298] New: w1064v1909 shows the "create a Windows account" fullscreen dialog
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=50298 Bug ID: 50298 Summary: w1064v1909 shows the "create a Windows account" fullscreen dialog Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 68868 --> https://bugs.winehq.org/attachment.cgi?id=68868 w1064v1909 "Let's finish setting up your device" dialog w1064v1909 corresponds to the 1909-live snapshot of the w1064 VM. That snapshot is created automatically by the TestBot. Currently this snapshot opens on the "create a Windows account" fullscreen dialog, the one with the following title: Let's finish setting up your device It seems this dialog 'pops up' automatically on boot if one does not provide a Microsoft account when installing Windows. When that happens is hard to predict, Windows seems to wait a few days or reboots before doing. Furthermore something WineTest does seems to make this dialog go away because it's not visible in the final WineTest screenshot. However it is visible if one runs a single test such as ntdll:exception. It's not entirely clear if this dialog is interfering with some tests but its presence is definitely unwanted. -- 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 60131] New: Changing a distribution when reviewing test results, accepts the new distribution anyway
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60131 Bug ID: 60131 Summary: Changing a distribution when reviewing test results, accepts the new distribution anyway Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 URL: https://appdb.winehq.org/objectManager.php?bIsQueue=fa lse&bIsRejected=false&sClass=distribution&iId=2085&sAc tion=view&sTitle=View+Distribution OS: Linux Status: NEW Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)list.winehq.org Reporter: imwellcushtymelike(a)gmail.com Target Milestone: --- Distribution: --- For reasons unknown, people love to submit distributions that are already listed. When reviewing test results, you can remove the details of the "new" distro from the fields, and select the existing distro. After accepting the test result, the "new" distro is created anyway. This new distro now claims to have a test result, though there are none. I assume this is because the accept/reject of this distro is linked directly to the test result. This is obviously not ideal. The counter of 1 for an empty distro may be an additional issue. There may be a number of empty distros like this, but the list isn't currently sortable by number of test results. -- 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 60130] New: GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60130 Bug ID: 60130 Summary: GetProcAddress() crashes with a stack overflow when a DLL export forwards to its own module name Product: Wine Version: 11.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)list.winehq.org Reporter: realmaitreal(a)deadmail.lat Target Milestone: --- Created attachment 81711 --> http://bugs.winehq.org/attachment.cgi?id=81711 sources + both binaries, sha1 b5346d4acdd636eae5fd13a8a986a030f805b48e A DLL that forwards an export to its own module name makes GetProcAddress() recurse until the thread stack is exhausted, killing the process. Attached is a minimal testcase (source included, ~20 lines): selffwd.dll - one export, "test_func", a forwarder to "SELFFWD.test_func", i.e. to the DLL's own base name fwdloop.exe - LoadLibraryA("selffwd.dll") then GetProcAddress(mod, "test_func") Steps to reproduce: 1. put selffwd.dll and fwdloop.exe in the same directory 2. wine fwdloop.exe Expected (Windows 10 x64, see windows-output.txt): GetProcAddress returns NULL, GetLastError() is 193 (ERROR_BAD_EXE_FORMAT), the program exits normally. Actual (wine-11.14, clean prefix, no DLL overrides, see wine-output.txt): err:virtual:virtual_setup_exception stack overflow ... and the process dies before GetProcAddress returns. find_forwarded_export() in dlls/ntdll/loader.c resolves the forwarder's module by base name, which finds the forwarding module itself, and recurses on the same export with unchanged arguments. Nothing bounds the chain. This is not specific to the testcase. It affects the common "proxy DLL" pattern, where a stub in an application's directory forwards its exports on to the system copy of the same name. I hit it originally with a third-party plugin DLL for the Steam client. -- 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 60129] New: strftime missing support for %O modifier (breaks Python 3.15 calendar module)
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60129 Bug ID: 60129 Summary: strftime missing support for %O modifier (breaks Python 3.15 calendar module) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)list.winehq.org Reporter: te5212329(a)gmail.com Target Milestone: --- Distribution: --- ================================================================================ WINE BUG REPORT DRAFT ================================================================================ Title: strftime missing support for %O modifier (breaks Python 3.15 calendar module) Product: Wine Component: msvcrt Version: 11.14 (also affects 9.0, 10.0) Summary: -------- Wine's strftime implementation does not support the %O modifier for alternative date/time representations. This causes Python 3.15+ to crash when importing the calendar module. Steps to Reproduce: ------------------- 1. Install Python 3.15.0b4 Windows embeddable package in Wine 2. Run: wine python.exe -c "import calendar" Expected Result: ---------------- calendar module imports successfully Actual Result: -------------- Traceback (most recent call last): File "<string>", line 1, in <module> File "calendar.py", line 156, in <module> File "calendar.py", line 110, in __getitem__ ValueError: Invalid format string Technical Details: ------------------ Python 3.15 (commit 438cbd857a875efc105b4215b1ae131e67af37e1, July 31, 2025) added support for standalone month names using the %OB and %Ob format specifiers in the calendar module. These specifiers are part of the POSIX strftime extension for alternative representations and are supported by Windows via GetLocaleInfoEx with LOCALE_SMONTHNAME* variants. The %O modifier is used for: - %OB: Standalone full month name (nominative case for Slavic/Baltic/Greek languages) - %Ob: Standalone abbreviated month name Wine's dlls/msvcrt/time.c strftime implementation lacks handling for the %O modifier, causing it to return an error instead of the month name. Affected Software: ------------------ - Python 3.15.0b4 and newer - Any Windows application using %O format specifiers in strftime Tested Wine Versions: --------------------- - Wine 9.0 (Ubuntu 24.04): FAILS - Wine 10.0 (Debian trixie): FAILS - Wine 11.14 (WineHQ devel): FAILS References: ----------- - Python commit: https://github.com/python/cpython/commit/438cbd857a875efc105b4215b1ae131e67… - Python issue: https://github.com/python/cpython/issues/131146 - POSIX strftime %O modifier: https://pubs.opengroup.org/onlinepubs/9699919799/functions/strftime.html ================================================================================ EOF ================================================================================ WINE BUG REPORT DRAFT ================================================================================ Title: strftime missing support for %O modifier (breaks Python 3.15 calendar module) Product: Wine Component: msvcrt Version: 11.14 (also affects 9.0, 10.0) Summary: -------- Wine's strftime implementation does not support the %O modifier for alternative date/time representations. This causes Python 3.15+ to crash when importing the calendar module. Steps to Reproduce: ------------------- 1. Install Python 3.15.0b4 Windows embeddable package in Wine 2. Run: wine python.exe -c "import calendar" Expected Result: ---------------- calendar module imports successfully Actual Result: -------------- Traceback (most recent call last): File "<string>", line 1, in <module> File "calendar.py", line 156, in <module> File "calendar.py", line 110, in __getitem__ ValueError: Invalid format string Technical Details: ------------------ Python 3.15 (commit 438cbd857a875efc105b4215b1ae131e67af37e1, July 31, 2025) added support for standalone month names using the %OB and %Ob format specifiers in the calendar module. These specifiers are part of the POSIX strftime extension for alternative representations and are supported by Windows via GetLocaleInfoEx with LOCALE_SMONTHNAME* variants. The %O modifier is used for: - %OB: Standalone full month name (nominative case for Slavic/Baltic/Greek languages) - %Ob: Standalone abbreviated month name Wine's dlls/msvcrt/time.c strftime implementation lacks handling for the %O modifier, causing it to return an error instead of the month name. Affected Software: ------------------ - Python 3.15.0b4 and newer - Any Windows application using %O format specifiers in strftime Tested Wine Versions: --------------------- - Wine 9.0 (Ubuntu 24.04): FAILS - Wine 10.0 (Debian trixie): FAILS - Wine 11.14 (WineHQ devel): FAILS References: ----------- - Python commit: https://github.com/python/cpython/commit/438cbd857a875efc105b4215b1ae131e67… - Python issue: https://github.com/python/cpython/issues/131146 - POSIX strftime %O modifier: https://pubs.opengroup.org/onlinepubs/9699919799/functions/strftime.html ================================================================================ -- 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 60127] New: Wrong colors in Forestia
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=60127 Bug ID: 60127 Summary: Wrong colors in Forestia Product: Wine Version: 1.5.13 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: alexhenrie24(a)gmail.com Target Milestone: --- Distribution: --- Forestia is one of many old games that refuse to start if the graphics card is set to display more than 256 colors. To work around that problem, do the following: 1. Run `wine 'D:\SETUP.EXE'` to install the game. 2. In one terminal, run `Xephyr :1 -ac -screen 1024x768x8` to start a 256-color nested X server. 3. In another terminal, run `DISPLAY=:1 openbox` to start a window manager that supports colormaps. 4. In another terminal, run `DISPLAY=:1 wine 'C:\Program Files (x86)\Forestia\FORESTIA.EXE'` to start the game. 5. The game shows an error dialog that says 'Problème à l'ouverture de "C:\users\alex\Temp".' Just close it and the game will continue. Forestia's main menu has three buttons on the bottom: Exit should be red, Menu should be green, and Help should be orange. As far as I can tell, Wine 1.5.12 was the last version where the colors were close to correct: In Wine 1.5.12, Exit is brown, Menu is green, and Help is orange. After Wine 1.5.12, the colors are scrambled in one way or another. `git bisect` landed on the same commit as Bug 48088, but the fix for that bug in Wine 5.0 did not completely resolve the issue, and Bug 57584 broke it worse in Wine 9.11. Interestingly, https://gitlab.winehq.org/wine/wine/-/merge_requests/9619 does not help with Forestia. $ sha256sum Forestia-English.iso dff0b757f8cbe8784dda2da6c1ab8f0bca15f3a763148eaa0c200473919368d5 -- 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