February 2026 - Wine-bugs - list.winehq.org

[Bug 51139] New: Application T@X 2021 freezes when trying to transmit data to Elster (German Tax Application)
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

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 59201] New: Naviextras Toolbox crashes when launched with wow64 related unhandled exception: page fault on read access
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=59201 Bug ID: 59201 Summary: Naviextras Toolbox crashes when launched with wow64 related unhandled exception: page fault on read access Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: lced2-wine(a)yahoo.com Distribution: --- Created attachment 80076 --> http://bugs.winehq.org/attachment.cgi?id=80076 Backtrace of the crash Steps to reproduce: - Install the software - download link https://winmo.naviextras.com/shop/portal/downloads - Launch the soft Actual result: the window of the tool shows up quickly then instantly crashes. Backtrace attached. -- 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 58575] New: Low performance in an old Directx8 Sonic fangame in wined3d
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

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 46197] New: user32: Implement CascadeWindows and TileWindows
by wine-bugs＠winehq.org 06 Feb '26

06 Feb '26

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 58919] New: osu!stable freezes when running on winewayland
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

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 59290] New: Serial baud rates above 115200 not supported due to bug in serial.c
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=59290 Bug ID: 59290 Summary: Serial baud rates above 115200 not supported due to bug in serial.c Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: serial Assignee: wine-bugs(a)list.winehq.org Reporter: winehq.x4aeq(a)simplelogin.com Distribution: --- Hi, I have been attempting to move my simulator from Windows to Linux and have had great success with the exception of certain USB-over-serial devices. I found some references to this bug in the past, but it seems it was never opened formally and bad advice was given: https://forum.winehq.org/viewtopic.php?p=139497#p139497 This bug will affect all applications that interact with devices that run at bauds >115200 (specifically, in my case, 250000), 3d printers, GPS receivers, OBD interfaces, etc. Through much troubleshooting and fact-finding I narrowed it down to these two lines in `serial.c`: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/unix/serial.c#… https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/ntdll/unix/serial.c#… An application that is affected: https://github.com/tronicgr/AMC-AASD15A-Firmware/blob/master/Thanos-utility… sha1: 0ded8cf5b1595a984144b5d5c8dcdaced0020b1e AMC_Config.exe Another application affected: https://www.simhubdash.com/ The applications (AMC_Config.exe is an example of one, SimHub is another) are non-functional when trying to access these USB devices, as they use the API `SerialPort.Open()` which in turn calls `GetCommProperties()` which calls this `IOCTL_SERIAL_GET_PROPERTIES` function, we see these items in the debug log: ```sh 0a48:trace:comm:serial_DeviceIoControl 0x3cc IOCTL_SERIAL_GET_PROPERTIES (nil) 0 0x6acf6b0 64 0x7ffffe7ff4f0 0a48:trace:comm:serial_DeviceIoControl 0x3cc IOCTL_SERIAL_GET_MODEMSTATUS (nil) 0 0x6acf768 4 0x7ffffe7ff4f0 0a48:trace:comm:get_modem_status 0006 -> ``` They applications are expecting to be presented back the actual maximum baud rate - but are erroring out with: "Max baud supported by device 131072" - this correlates to `BAUD_115200` hex value of `0x00020000`. I created a patch as below, instead using the actual max baud supported by Microsoft which is `BAUD_USER` / `0x10000000`, I also added the other supported baud `BAUD_128K` as a SettableBaud for those devices. https://learn.microsoft.com/en-us/windows/win32/api/winbase/ns-winbase-comm… Patch: ``` diff --git a/dlls/ntdll/unix/serial.c b/dlls/ntdll/unix/serial.c index 7a79dd0ac6a..a8585bbced9 100644 --- a/dlls/ntdll/unix/serial.c +++ b/dlls/ntdll/unix/serial.c @@ -376,14 +376,14 @@ static NTSTATUS get_properties(int fd, SERIAL_COMMPROP *prop) prop->ServiceMask = SP_SERIALCOMM; prop->MaxTxQueue = 4096; prop->MaxRxQueue = 4096; - prop->MaxBaud = BAUD_115200; + prop->MaxBaud = BAUD_USER; prop->ProvSubType = PST_RS232; prop->ProvCapabilities = PCF_DTRDSR | PCF_PARITY_CHECK | PCF_RTSCTS | PCF_TOTALTIMEOUTS | PCF_INTTIMEOUTS; prop->SettableParams = SP_BAUD | SP_DATABITS | SP_HANDSHAKING | SP_PARITY | SP_PARITY_CHECK | SP_STOPBITS ; prop->SettableBaud = BAUD_075 | BAUD_110 | BAUD_134_5 | BAUD_150 | BAUD_300 | BAUD_600 | BAUD_1200 | BAUD_1800 | BAUD_2400 | BAUD_4800 | - BAUD_9600 | BAUD_19200 | BAUD_38400 | BAUD_57600 | BAUD_115200 ; + BAUD_9600 | BAUD_19200 | BAUD_38400 | BAUD_57600 | BAUD_115200 | BAUD_128K | BAUD_USER ; prop->SettableData = DATABITS_5 | DATABITS_6 | DATABITS_7 | DATABITS_8 ; prop->SettableStopParity = STOPBITS_10 | STOPBITS_15 | STOPBITS_20 | PARITY_NONE | PARITY_ODD |PARITY_EVEN | PARITY_MARK | PARITY_SPACE; ``` I am unsure how to go about contributing such a small change - I have read the contributor documentation and have the code to fix it, but I am more than a little intimidated. Appreciate any eyes on this, Myles -- 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 50501] New: Default wrapping mode DWRITE_WORD_WRAPPING_WRAP is not handled correctly
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

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

[Bug 59181] New: GTA: San andreas/Vice city - Intro videos aren't properly rendered, showing only a white screen
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=59181 Bug ID: 59181 Summary: GTA: San andreas/Vice city - Intro videos aren't properly rendered, showing only a white screen Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)list.winehq.org Reporter: ziadelsayed1797(a)tutamail.com Distribution: --- Intro videos are not shown properly in either sa and or vc, it instead greets you with a white screen, audio only. This only happens on winewayland, and not winex11. -- 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 52592] New: MilkyTracker does not work: no valid waveout devices.
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

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 58167] New: Pegasus Mail immediately restores window
by WineHQ Bugzilla 06 Feb '26

06 Feb '26

http://bugs.winehq.org/show_bug.cgi?id=58167 Bug ID: 58167 Summary: Pegasus Mail immediately restores window Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jonass.user.lysator.liu.se Distribution: --- After upgrading from 10.5 to 10.6 I can't minimize Pegasus Mail. When I click minimize the window only flashes, seems like it minimizes but immediately restores to open window with the same size as before. No error messages in console. git bisect suggests it may be related to commit 6b04bdf25796c9c76815588bf7bdc36ff44b9e13 OS: XUbuntu 24.04.2 LTS NVIDIA Driver Version: 535.183.01 Using X11 (not Wayland) -- 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 38