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

[Bug 21158] New: Hitman: Contracts ignores mouse press events
by wine-bugs＠winehq.org Feb. 8, 2026

Feb. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=21158 Summary: Hitman: Contracts ignores mouse press events Product: Wine Version: 1.1.35 Platform: x86 URL: http://www.gamershell.com/download_5663.shtml OS/Version: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: arethusa26(a)gmail.com CC: vitaliy(a)kievinfo.com With wine-1.1.35-180-g20a50f3, after launching Hitman: Contracts, mouse press events at the main menu are ignored by the game. Since a user reported that the game worked normally in wine-1.1.9, a regression test was performed, which indicated: 3743a1a7ca170c765cd779c61b9e362c5b1c5203 is first bad commit commit 3743a1a7ca170c765cd779c61b9e362c5b1c5203 Author: Vitaliy Margolen <wine-patches(a)kievinfo.com> Date: Sun Feb 1 13:11:46 2009 -0700 dinput: Consume mouse & keyboard events in exclusive mode. :040000 040000 6ae6b43b3c100af38ed4f27384470dc4d2595bc1 700b35b9bc8fd27239ee8faaed8ca1c10cfc31d4 M dlls Wine built prior to the indicated commit allows mouse input to work normally. Interestingly, doing graphical mode changes (via keyboard input) makes mouse input work again. The AppDB also suggests adding the strings: UseDirectInputMouse UseDirectInputKeyboard to the HitmanContracts.ini configuration file to have mouse input work. The only visible output under wine-1.1.35-180-g20a50f3 is: fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(1280,1024) fixme:win:EnumDisplayDevicesW ((null),0,0x32eb58,0x00000000), stub! fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x253b060,0x253afa8): stub fixme:dsound:DllCanUnloadNow (void): stub fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x253b060,0x253afa8): stub (Z:\code\hitman2\gui\MainMenu.cpp:554)Hitman Contracts build 171 (Apr 26 2004 14:42:27) fixme:dsound:DllCanUnloadNow (void): stub -- 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 18

[Bug 58961] New: SynthFont2 crashes when attempting to launch it
by WineHQ Bugzilla Feb. 8, 2026

Feb. 8, 2026

http://bugs.winehq.org/show_bug.cgi?id=58961 Bug ID: 58961 Summary: SynthFont2 crashes when attempting to launch it Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: unwed-cola-zesty(a)duck.com Distribution: --- Created attachment 79662 --> http://bugs.winehq.org/attachment.cgi?id=79662 Backtrace of the described bug. The latest version of SynthFont2 (2.9.1.1) crashes with an access violation in SynthFont2x64.exe when opening, once the 30-day trial dialog is closed. To reproduce: 0. Download and install the program from the following link: https://www.synthfont.com/SynthFont2x64Setup.exe 1. Launch SynthFont2 (the main executable is "SynthFont2x64.exe", present at "C:\Program Files\SynthFont2"). 2. Dismiss the 30-day trial window ("You are on day X of the 30 day trial period. Have fun!"). 3. The app notifies of an access violation in "SynthFont2x64.exe". Expected behaviour: The app doesn't crash on startup. The issue occurs on SynthFont2 v2.9.1.1 when running on Linux Mint 22.2 with the latest wine-devel (10.18). The issue does NOT occur on the same SynthFont version (v2.9.1.1) running on latest Windows 10. Additional information: SynthFont is a MIDI player and editor for Windows. v1 is the original free version (with less features), v2 is the newer paid version (described in this bug report). Only v1 is listed in the AppDB, and even then it hasn't been updated since v1.322 (released in 2009), with the latest version being 1.815. Backtrace is attached. Not sure where to find Wine logs, so they aren't included. -- 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 2

[Bug 58264] New: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93"
by WineHQ Bugzilla Feb. 7, 2026

Feb. 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=58264 Bug ID: 58264 Summary: regression in multiple apps in Wine >=10.7, error: "Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevu lkan/loader_thunks.c, line 93" Product: Wine Version: 10.7 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com Created attachment 78605 --> http://bugs.winehq.org/attachment.cgi?id=78605 macOS Terminal log, wine-devel 10.8 running cpuz_x64.exe On macOS, there is a regression in multiple Windows programs since Wine-devel 10.7 (including 10.8) releases by Gcenx, with the final lines of the terminal output reading: > -[MTLHeapDescriptorInternal validateWithDevice:]:327: failed assertion `Heap Descriptor Validation > Placement heap type is not supported. > ' > 01a0:err:msvcrt:_wassert (L"!status && \"vkAllocateMemory\"",L"/Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c",93) > Assertion failed: !status && "vkAllocateMemory", file /Users/gcenx/Documents/GitHub/wine-private/dlls/winevulkan/loader_thunks.c, line 93 These programs work fine in Wine-devel 10.6 and lower tested with Wine-devel 10.7 and 10.8 binary releases from Gcenx (https://github.com/Gcenx/macOS_Wine_builds/releases) on macOS 11.7.10 tested with CPU-Z 2.15 (portable) (cpuz_x64.exe) download: https://download.cpuid.com/cpu-z/cpu-z_2.15-en.zip sha256: c8461d995d77a8fe1e8c5823403e88b04b733165cc151083b26379f1fe4b9501 -- 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 46

[Bug 58492] New: Prism Cross Team Matches Lag and Flash Screen
by WineHQ Bugzilla Feb. 7, 2026

Feb. 7, 2026

http://bugs.winehq.org/show_bug.cgi?id=58492 Bug ID: 58492 Summary: Prism Cross Team Matches Lag and Flash Screen Product: Wine Version: 10.11 Hardware: x86-64 URL: https://drive.google.com/file/d/1B8c2Gp3NhoafUUEEQD-cP co-6j7-Sgms/view?usp=drive_link OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jenngra505(a)roadrunner.com Distribution: Mint When playing a team match in the Smash Bros fangame Prism Cross, the background will frequently flash colors matching the team outline when attacks are used. Lagging the game in the process. The game was developed in Game Maker and relies on DirectX 9 for its character graphics. A video showcasing the bug is linked below. https://youtu.be/FIBkb6wyDBA -- 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 18

[Bug 51139] New: Application T@X 2021 freezes when trying to transmit data to Elster (German Tax Application)
by WineHQ Bugzilla Feb. 6, 2026

Feb. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=51139 Bug ID: 51139 Summary: Application T(a)X 2021 freezes when trying to transmit data to Elster (German Tax Application) Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dieter.jurzitza(a)harman.com Distribution: --- T(a)X20XX can be used with wine since years. This year it apparently worked as usual, with one frustrating exception: when trying to transfer the entire documetation to the finance office at the end the application freezes and does noting any more. Unfortunately no error shows in the logs when starting wine with a corresponding debug option (WINEDEBUG=+relay, I hope this is ok ...). I have 32 GByte of logging code what is meaningless to upload - but no "real" error message inside. "top" shows 100% CPU - load by the wine process stman.exe. Messages show like: 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000024) ret=089a10d6 01b8:Ret ntdll.RtlAllocateHeap() retval=3ec3bbe0 ret=089a10d6 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000024) ret=089a10d6 01b8:Ret ntdll.RtlAllocateHeap() retval=2f24da98 ret=089a10d6 01b8:Call KERNEL32.HeapFree(00220000,00000000,2f24da98) ret=0899e7eb 01b8:Ret KERNEL32.HeapFree() retval=00000001 ret=0899e7eb 01b8:Call KERNEL32.HeapFree(00220000,00000000,3ec3bbe0) ret=0899e7eb 01b8:Ret KERNEL32.HeapFree() retval=00000001 ret=0899e7eb in fast sequence and this: 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000014) ret=6be509ba 01b8:Ret ntdll.RtlAllocateHeap() retval=31991020 ret=6be509ba 0238:Call ntdll._strnicmp(17f9c7cc "Inter-| Receive | Transmit\n",17f9ca0c "eth1",00000004) ret=7eceaa21 01b8:Call ntdll.RtlAllocateHeap(00220000,00000008,00000014) ret=6be7960b 0238:Ret ntdll._strnicmp() retval=00000001 ret=7eceaa21 01b8:Ret ntdll.RtlAllocateHeap() retval=31983590 ret=6be7960b 0238:Call ntdll._strnicmp(17f9c7cd "face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed\n",17f9ca0c "eth1",00000004) ret=7eceaa21 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,00000020) ret=6be798c1 0238:Ret ntdll._strnicmp() retval=00000001 ret=7eceaa21 01b8:Ret ntdll.RtlAllocateHeap() retval=31992478 ret=6be798c1 0238:Call ntdll._strnicmp(17f9c7d0 "lo: 376975 3786 0 0 0 0 0 0 376975 3786 0 0 0 0 0 0\n",17f9ca0c "eth1",00000004) ret=7eceaa21 0238:Ret ntdll._strnicmp() retval=00000001 ret=7eceaa21 01b8:Call ntdll.RtlAllocateHeap(00220000,00000000,0000000c) ret=6be7974e 0238:Call ntdll._strnicmp(17f9c7ce "eth1: 727671935 574392 0 0 0 0 0 2870 31275660 279019 0 0 0 0 0 0\n",17f9ca0c "eth1",00000004) ret=7eceaa21 01b8:Ret ntdll.RtlAllocateHeap() retval=31991978 ret=6be7974e 0238:Ret ntdll._strnicmp() retval=00000000 ret=7eceaa21 cycling through eth0, eth1, wlan0 etc ... Finally I see once this at the begin (when the trouble starts ...): 01b8:Ret ntdll.RtlAllocateHeap() retval=3ecc7cc8 ret=089a10d6 01b8:Call KERNEL32.OutputDebugStringW(3ecc7cd8 L"void __thiscall BTS::FormViewerPage::enablePrevNext(void) -1 21\n") ret=67020427 01b8:Call ntdll.RtlInitUnicodeString(0021d000,3ecc7cd8 L"void __thiscall BTS::FormViewerPage::enablePrevNext(void) -1 21\n") ret=7b0125fa 01b8:Ret ntdll.RtlInitUnicodeString() retval=00000082 ret=7b0125fa with the "void __thiscall entries - but no clue on my behalf. Any support is very much appreciated, most specifically what could I do and how could I better debug the process without flooding my harddisk with trillions (ok, maybe less :-)) of messages. Thank you very much, take care Dieter Jurzitza -- 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 68

[Bug 58575] New: Low performance in an old Directx8 Sonic fangame in wined3d
by WineHQ Bugzilla Feb. 6, 2026

Feb. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=58575 Bug ID: 58575 Summary: Low performance in an old Directx8 Sonic fangame in wined3d Product: Wine Version: 10.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- This game has a built-in fps counter. After launching it, I was surprised to find that it ran at only 30 fps in the hub area, while on windows it runs at 60. It is seemingly ok in the gameplay, but fps is often several values short of 60, and there are also rarer drops to 30 for several seconds. There are no warnings in the console other than related to directsound. DXVK works at a locked 60 fps, so that means that it's a problem with wined3d. Here is the link to the game: https://gamejolt.com/games/sonic3d/28626 -- 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 14

[Bug 58919] New: osu!stable freezes when running on winewayland
by WineHQ Bugzilla Feb. 6, 2026

Feb. 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=58919 Bug ID: 58919 Summary: osu!stable freezes when running on winewayland Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: marshnelloosu(a)gmail.com Distribution: --- Playing a map in osu!stable (https://osu.ppy.sh/home/download) on latest winewayland causes the game to freeze (visually, audio still runs in the background). Bisected the breaking commit to be this: https://gitlab.winehq.org/wine/wine/-/commit/871a52cb8b2d9688dbc100284843aa… Reverting it does indeed make the game playable again. Tested on latest KDE Plasma 6.5 To reproduce: - `winetricks -q dotnet48 dotnet20 gdiplus_winxp` - Launch the game with `DISPLAY=` and wait a few seconds (20-30s) in the main menu - Set the game FPS to unlimited in settings - Play a beatmap, freeze should occur as soon as it's launched. If it does not occur on the game's first run, a second run should trigger the 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.

3 7

[Bug 46197] New: user32: Implement CascadeWindows and TileWindows
by wine-bugs＠winehq.org Feb. 6, 2026

Feb. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=46197 Bug ID: 46197 Summary: user32: Implement CascadeWindows and TileWindows Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: katayama.hirofumi.mz(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62857 --> https://bugs.winehq.org/attachment.cgi?id=62857 The patch Wine lacks the implementations of CascadeWindows and TileWindows functions of window arrangement. -- 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 9

[Bug 52592] New: MilkyTracker does not work: no valid waveout devices.
by WineHQ Bugzilla Feb. 6, 2026

Feb. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=52592 Bug ID: 52592 Summary: MilkyTracker does not work: no valid waveout devices. Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: carlo.bramix(a)libero.it Distribution: --- MilkyTracker is an multi-platform music application for creating .MOD and .XM module files. https://github.com/milkytracker/MilkyTracker Unfortunately, it doesn't work on WINE because it cannot open any waveout device. Sources of MilkyTracker do these actions: 1) waveOutOpen(&hwo, WAVE_MAPPER, &format, 0, 0, CALLBACK_NULL); This call is a success and it returns a valid handle. 2) waveOutGetID(hwo,(LPUINT)&waveOutID); This call also returns success and it returns a value of 63 into "waveOutID". BUT THIS IS WRONG. "waveOutID" should be equal to WAVE_MAPPER, which equal to -1, as you can see in point (1). 3) waveOutGetDevCaps((UINT)waveOutID, &waveoutcaps, sizeof(waveoutcaps)); As result, this call to waveOutGetDevCaps() fails with return value of MMSYSERR_BADDEVICEID. Here there is the point where there is the code that I'm talking about: https://github.com/milkytracker/MilkyTracker/blob/4f97b7011b20519890e30368e… The cause of the trouble is the way the function waveOutGetID() is implemented. waveOutGetID() calls WINMM_GetDeviceFromHWAVE(). And WINMM_GetDeviceFromHWAVE() calls WINMM_DecomposeHWAVE() Into WINMM_DecomposeHWAVE(), there are these lines: ULONG32 l = HandleToULong(hwave); *device_index = l & 0xFF; But this is wrong, because *device_index will be never able to return -1 that is the value for WAVE_MAPPER. -- 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 20

[Bug 50501] New: Default wrapping mode DWRITE_WORD_WRAPPING_WRAP is not handled correctly
by WineHQ Bugzilla Feb. 6, 2026

Feb. 6, 2026

https://bugs.winehq.org/show_bug.cgi?id=50501 Bug ID: 50501 Summary: Default wrapping mode DWRITE_WORD_WRAPPING_WRAP is not handled correctly Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- Split from bug 50494, test program attached there could be used to reproduce. Mode DWRITE_WORD_WRAPPING_WRAP is more permissive than current implementation, it not only enables wrapping after clusters with canWrapLineAfter == 1, but also breaks after any cluster if current line had no good wrapping position otherwise. -- 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 2