August 2025 - Wine-bugs - list.winehq.org

[Bug 50182] New: Hotline Miami 2 GOG version not launch after install.
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=50182 Bug ID: 50182 Summary: Hotline Miami 2 GOG version not launch after install. Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: pamungkassendy(a)gmail.com Distribution: --- Created attachment 68700 --> https://bugs.winehq.org/attachment.cgi?id=68700 Hotline Miami 2 GOG Version Game Didn't launch and instead give a crasth report -- 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 47251] New: add support for ConPTY API (pseudo console)
by wine-bugs＠winehq.org 14 Nov '25

14 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=47251 Bug ID: 47251 Summary: add support for ConPTY API (pseudo console) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: programmerjake(a)gmail.com Distribution: --- as in title. API reference: https://docs.microsoft.com/en-us/windows/console/creating-a-pseudoconsole-s… -- 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 52128] New: Hog4PC 3.17 installer VBScript custom action wants scrrun:filesys_MoveFolder implementation
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=52128 Bug ID: 52128 Summary: Hog4PC 3.17 installer VBScript custom action wants scrrun:filesys_MoveFolder implementation Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. --- snip --- $ wine msiexec -i Hog_4_PC_3.17.0.3327.msi ... 0184:trace:scrrun:filesys_FolderExists 0362A084 L"C:\\users\\focht\\AppData\\Roaming" 02F0F970 ... 0184:fixme:scrrun:filesys_MoveFolder 0362A084 L"C:\\users\\focht\\AppData\\Roaming" L"C:\\users\\focht\\AppData\\Roaming" ... 0184:err:msi:MsiActiveScriptSite_OnScriptError script error: L"Object doesn't support this action" ... 0184:trace:msi:ScriptThread custom action (184) returned 1603 --- snip --- VBScript custom action scriptlet: --- snip --- Function renamePersistentDir() Dim appDataEnv appDataEnv = shell.expandEnvironmentStrings("%APPDATA%") Dim roamingDir roamingDir = appDataEnv + "\Flying Pig Systems" If ( fso.FolderExists(roamingDir) ) Then fso.MoveFolder roamingDir, appDataEnv + "\High End Systems" fso.MoveFolder appDataEnv + "\High End Systems\Hog 4PC", appDataEnv + "\High End Systems\Hog 4 PC" End If End Function --- snip --- Wine source: https://source.winehq.org/git/wine.git/blob/f03933fbb73152c7a54383fba411a61… --- snip --- 3616 static HRESULT WINAPI filesys_MoveFolder(IFileSystem3 *iface,BSTR Source, 3617 BSTR Destination) 3618 { 3619 FIXME("%p %s %s\n", iface, debugstr_w(Source), debugstr_w(Destination)); 3620 3621 return E_NOTIMPL; 3622 } --- snip --- Stable download link via Internet Archive: https://web.archive.org/web/20211128125004/https://cdn.etcconnect.com/Hog_4… $ sha1sum Hog_4_PC_3.17.0.3327.msi.zip f98421bbbb0590df0e65ac18903471dd5fb61b6a Hog_4_PC_3.17.0.3327.msi.zip $ du -sh Hog_4_PC_3.17.0.3327.msi.zip 361M Hog_4_PC_3.17.0.3327.msi.zip $ sha1sum Hog_4_PC_3.17.0.3327.msi 0d22bf13c5a9bb682820ee6f690a866c1b320d9b Hog_4_PC_3.17.0.3327.msi $ wine --version wine-6.22-204-gf03933fbb73 Regards -- 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 57241] New: Managed COM components fail to load outside of application directory
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57241 Bug ID: 57241 Summary: Managed COM components fail to load outside of application directory Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: bob(a)paradoxlost.com Distribution: --- Managed assemblies are not loaded outside of the "current" directory due to a failure to open the file using the CodeBase path. https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/mscoree/corruntimeho… Here, the incorrect variable is passed to CreateFileW. It should be filename instead of path. -- 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 6

[Bug 58450] New: Total Annihilation (GOG, demo) – Wayland black screen on startup.
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58450 Bug ID: 58450 Summary: Total Annihilation (GOG, demo) – Wayland black screen on startup. Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: karol23145(a)gmail.com Distribution: --- Created attachment 78901 --> http://bugs.winehq.org/attachment.cgi?id=78901 WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`. ### Summary Total Annihilation (GOG version and demo) shows a black screen on native Wayland (Mutter 48.3). On X11 it works perfectly, and on XWayland the game has a minor fullscreen issue (see Bug 57482). ### Steps to reproduce 1. Download the Total Annihilation demo (or use the GOG version). GAME DEMO CAN BE DOWNLOADED FROM: https://archive.org/details/TotalAnnihilation_201405 2. Launch the game executable (`TotalA.exe`) under Wine on a native Wayland session (No XWayland). ### Current behavior The game process starts, sound can be heard, and keyboard input works (buttons can be pressed), but the entire game window is black. The window is also not fullscreen. ### Expected behavior The game's intro videos should play, followed by the main menu, which should be visible and interactive. ### Relevant logs, screenshots, screencasts etc. *Attached are the following files:* 1. `TA.log`: Full Wine debug log captured with `WINEDEBUG=+waylanddrv,+ddraw,+wined3d,+opengl,+seh`. 2. `system_info.txt`: Output of `inxi -Fxxxza`. ### System Details - **Wine Version:** Custom build from source (also tested with Wine development branch, same result) - **Windowing System:** Mutter 48.3 (Wayland session) - **Distribution:** Fedora 42 - **Graphics Driver:** Mesa 25.0.7 - **Kernel version:** 6.15.4 -- 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 6

[Bug 57001] New: Compute shader change causes Affinity Photo 2 to crash on start up
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=57001 Bug ID: 57001 Summary: Compute shader change causes Affinity Photo 2 to crash on start up Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: topgamer7(a)gmail.com CC: gmascellani(a)codeweavers.com Regression SHA1: c319b874669450cc17ebe9a7f459a17b86cdcddb Distribution: ArchLinux Created attachment 76840 --> https://bugs.winehq.org/attachment.cgi?id=76840 The two patches cat'd together commit c319b874669450cc17ebe9a7f459a17b86cdcddb (HEAD) Author: Giovanni Mascellani <...> Date: Tue Mar 19 12:25:28 2024 +0100 wined3d: Compile the clear compute shaders at runtime. Affinity Photo 2 can no longer start after the above commit was made. I narrowed this down by bisecting and rebuilding wine. The application no longer starts. It has a splash screen, and was not even getting to that point. System details: OS: Manjaro Linux x86_64 CPU: AMD Ryzen 9 6900HS with Radeon Graphics (16) @ 4.935GHz GPU: AMD ATI Radeon 680M GPU: AMD ATI Radeon RX 6650 XT / 6700S / 6800S Window manager: Sway, however the application is run using xwayland. Extra configure flags: ../configure \ --prefix='/usr' \ --libdir='/usr/lib' \ --with-x \ --enable-win64 \ --with-wayland \ -C Running affinity photo requires 1. winetricks dotnet48 corefonts 2. You do not need a license to reproduce. 3. some off mainline commits: commit a3c1e73023aa98c6665383096df34dfd86f33108 Author: James McDonnell <> Date: Sun Feb 26 12:56:24 2023 -0800 shell32/iconcache: Call LoadIconW commit 07dd01d8346cba084528ddf6e375641337f876f0 Author: James McDonnell <> Date: Mon Nov 21 21:26:19 2022 -0800 wintypes: Hack in some calls to RoResolveNamespace -- 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 4

[Bug 58650] New: Mouse cursor becomes invisible and unmovable
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58650 Bug ID: 58650 Summary: Mouse cursor becomes invisible and unmovable Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: agarplayerarlon(a)gmail.com Distribution: --- Created attachment 79226 --> http://bugs.winehq.org/attachment.cgi?id=79226 video of the issue in FL Studio with the wine wayland driver, if I move the mouse cursor to certain elements of the sidebar, that have names that are longer than the width of the sidebar, the mouse cursor becomes invisible and now in wine 10.14 unmovable, if I remember correctly up to wine 10.13 I was able to move the mouse, it would just becomes invisible, but as you can see in the video, it now becomes unmovable and the only way to move it again is to press the meta key and then since it took the focus away I can move it again. of course these issues don't happen when using xwayland with the x11 driver. -- 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 58140] New: ODBC using unixodbc stopped working due to regression merge between 9.0 and 10.0
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58140 Bug ID: 58140 Summary: ODBC using unixodbc stopped working due to regression merge between 9.0 and 10.0 Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: odbc Assignee: wine-bugs(a)winehq.org Reporter: heiko.rabe+winehq(a)peopleware.com Distribution: --- The following fix prevent proper usage of ODBC interface based on unixodbc provided DSN's: https://gitlab.winehq.org/wine/wine/-/commit/85047505f342b6767b9f48cbcdae2b… I'm using an odbc.ini as follows located at `/etc/odbc.ini` ``` [test] Driver=PostgreSQL Unicode Description=PostgreSQL Data Source Servername=xyz.internal.com Port=5432 UserName=xyz Password=xyz_password Database=test SSLMode=prefer Debug=0 CommLog=0 ``` This leads to following wine registry entries in `system.reg` file: ``` [Software\\ODBC\\ODBC.INI\\test] 1744806811 #time=1dbaecbc3836bb4 "Driver"="PostgreSQL Unicode" [Software\\ODBC\\ODBCINST.INI\\ODBC Drivers] 1744806811 #time=1dbaecbc3834d1e "PostgreSQL ANSI"="Installed" "PostgreSQL Unicode"="Installed" ``` Testing it with `isql` tool on linux the connect is successful and i can select data from database: ``` isql test +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------------------------+ SQL> ``` The Windows application using a driverconnect with connect string "DSN=test". Unfortunately the fix linked above searches the driver key now on a complete different registry key and tries only to open it from there. Versions previous to 10.0 are using the registry keys shown above and are working, version 10.0 now tries only: ``` [Software\\ODBC\\ODBC.INI\\ODBC Data Sources] 1744806811 #time=1dbaecbc3836bb4 ``` which is not present, will be created by requesting the driver and fails, cause the driver key can only be found on the above shown reg key, that 9.0 correctly supports. This stops working with ODBC based on unixodbc in version 10.0 and higher now. To me it's not clears, what problem the fix linked above should address. My guess would be, that one of following relates to the problem: - ODBC supports user and system DNS (system DNS seems now not longer be valid) - Wine runtime doesn't create the correct registry entries on 'wineboot' (leads to failing fix) - overlooked to support unixodbc at all and only tested with Microsoft ODBC drivers only. -- 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 21

[Bug 56187] New: windows.ui:uisettings fails on Windows 11
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56187 Bug ID: 56187 Summary: windows.ui:uisettings fails on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.ui:uisettings fails on Windows 11: uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 0 value.G == 120 value.B == 212 (type = 5) uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 0 value.G == 103 value.B == 192 (type = 4) uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 0 value.G == 62 value.B == 146 (type = 3) uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 0 value.G == 26 value.B == 104 (type = 2) uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 0 value.G == 145 value.B == 248 (type = 6) uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 76 value.G == 194 value.B == 255 (type = 7) uisettings.c:141: Test failed: got unexpected value.A == 255 value.R == 153 value.G == 235 value.B == 255 (type = 8) See https://test.winehq.org/data/patterns.html#windows.ui:uisettings The failures are systematic and started on 2023-11-16 and the failing test was introduced by the commit below on the same day: commit 3448a84cac437f66bf7bdd833a6ce5026fddd4cc Author: Myah Caron <qsniyg(a)protonmail.com> Date: Fri Sep 22 20:41:23 2023 +0000 windows.ui: Support accent colors in uisettings3_GetColorValue. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55640 Signed-off-by: Myah Caron <qsniyg(a)protonmail.com> -- 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 58320] New: ok() macro should not evaluate the format arguments if condition is not met.
by WineHQ Bugzilla 14 Nov '25

14 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58320 Bug ID: 58320 Summary: ok() macro should not evaluate the format arguments if condition is not met. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: testcases Assignee: wine-bugs(a)winehq.org Reporter: yshuiv7(a)gmail.com Distribution: --- While running the test suite under ASan I noticed in several instances where the format arguments given to the ok() macro is only safe to evaluate if the test case has failed. One such example is in bcrypt/tests: https://gitlab.winehq.org/wine/wine/-/blob/d9148e48a3257ae80361f02f0bb7a2d6… accessing `buffer[i]` is only safe if the test `i == sizeof(buffer)` has failed, and if the test case passes, we will access `buffer` out-of-bound. -- 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