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

[Bug 59472] New: FreeArc hangs on startup in new wow64 mode
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59472 Bug ID: 59472 Summary: FreeArc hangs on startup in new wow64 mode Product: Wine Version: 11.3 Hardware: x86-64 URL: https://archive.org/details/FreeArc-0.666-win32bin-Sou rces OS: Linux Status: NEW Keywords: download, testcase, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: arethusa26(a)gmail.com Distribution: --- Created attachment 80459 --> http://bugs.winehq.org/attachment.cgi?id=80459 Largest memory block loop test case executable When running the FreeArc archiver tool on the command line to add a file to an archive with a new wow64 build of Wine, the tool hangs indefinitely with only a banner output string: $ wine freearc/bin/Arc.exe a test.arc empty_file 0124:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 With a old wow64 build of Wine, the tool runs and completes successfully: $ wine freearc/bin/Arc.exe a test.arc empty_file 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION FreeArc 0.666 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... creating archive: test.arc Compressing 1 file, 1,024 bytes. Processed 0% 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 0024:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 0024:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 ... Compressed 1 file, 1,024 => 44 bytes. Ratio 4.2% Compression time: cpu 0.62 secs, real 0.31 secs. Speed 3 kB/s All OK To reproduce the issue with FreeArc, download "FreeArc-portable-0.666-win32.zip" from the URL link and extract the contents of the ZIP file to a directory named "freearc". The Arc.exe binary can be run with the provided command line. When FreeArc is run with new wow64 Wine, there appears to be a thread that is stuck repeatedly calling VirtualAlloc with 0 size: 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 0124:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 0124:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 The code involved in the hang appears to be the LargestMemoryBlock::LargestMemoryBlock() constructor in Environment.cpp from the FreeArc sources. It's a (buggy) loop that attempts a binary search for the largest size it can successfully pass to VirtualAlloc. I have extracted the logic to create a standalone test case, which is built with: i686-w64-mingw32-gcc -O2 -Wall -Wl,--large-address-aware -o largest_memory_block.exe largest_memory_block.c On Windows 10, the largest_memory_block.exe test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 7fffffff a = 0 b = 7fffffff Freeing pointer 00000000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 01970000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 7f98ffff b = 7f990001 Freeing pointer 00000000 with VirtualFree Allocating 7f990000 bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7f990000 On new wow64 Wine, the test case shows the following output: a = 0 b = ffffffff Freeing pointer 00000000 with VirtualFree Allocating 7fffffff bytes with VirtualAlloc VirtualAlloc returned 7fff0000 VirtualAlloc succeeded, updating a to 7fffffff a = 7fffffff b = ffffffff Freeing pointer 7fff0000 with VirtualFree Allocating 3fffffff bytes with VirtualAlloc VirtualAlloc returned 00900000 VirtualAlloc succeeded, updating a to 3fffffff ... a = 1 b = ffffffff Freeing pointer 003f0000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 a = 1 b = 0 Freeing pointer 00000000 with VirtualFree Allocating 0 bytes with VirtualAlloc VirtualAlloc returned 00000000 VirtualAlloc failed, updating b to 0 ... The midpoint computation "c = (a + b) / 2" in the loop overflows when the initial allocation succeeds on Wine and leads to incorrect execution, whereas the initial allocation doesn't appear to succeed on Windows. -- 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

[Bug 59289] New: GOG-Game "Asterix and Obelix XXXL: The Ram From Hibernia" crashes on start
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59289 Bug ID: 59289 Summary: GOG-Game "Asterix and Obelix XXXL: The Ram From Hibernia" crashes on start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: jmb_tux(a)gmx.net Distribution: --- Created attachment 80222 --> http://bugs.winehq.org/attachment.cgi?id=80222 Screen Dump from Crash Report by AOA.exe I am now using WineHQ Repos - both stable and devel, but currently these are the same. Why is there no 11.0 as devel-version to select? Especially as both, stable and devel, are 11.0 ? But in this case, versions are quite unimportant, as it is the same on 10.0 or 9.0 ... The former 3 "Asterix&Obelix XXL" titles work without problem (Wine 9 like Wine 10), but now the new title no longer used their own engine, but OSome Studio / Microids use with the latest Release on 27.10.2022 Epic's Unreal Engine 5, but it looks this is severely broken. As I am not using Windows, I can not say that it works / don't work on Windows. Unfotunately, GOG is not willing give the slightest support when using Wine. Thus instead of getting info - I can only ask for Refund. Then after some time buy it again, test it, and ask for refund if its is still broken ... When starting it with Wine via "wine AOA.exe" (in 'GOG\ Games' binary path, I directly hear a sound and when it ends, the crash message appears: ~~~ "The UE4-AOA [File:Unknown] [Line: 339]" Direct3DDevice->CreateTexture2D(TextureDesc,SubResourceData,OutTexture2D) failed at D:/P41660/UE427Custom/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Texture.cpp:534 with error E-INVALIDARG, Size)1920x1080x1 PF=67 Format=(9x99999967), NumMips=1, Flags=D2D11_BIND_SHADER_RESOURCE, Usage:0x0, CPUFlags: 0x0, MiscFlags:0x0, SampleCount:0x1, SampleQuality:0x0, SubresPtr:0x0000000000000000m SubpresPitch:0,SupresSlicePitch:0 [OK] ~~~ (I hope I have no typo - but I have added a screen dump as attatchment.) The same error message shows on an o AMD system Zen 4: Ryzen 9 7900 & RDNA 3: Radeon RX 7800 XT as well as in an o Intel Skylake with Nvidi graphics. So it is not HW relevant ... but while gamers report about many bugs, I have not read about direct crashes on start as happening under Wine. It is the 1st game using 4 Players in locCoop for that series ... and it would be a pity, if this can not be played under Wine at all ... If I am able to reach for Devs/Publisher, I will hint them to this bug report ... and will add any information I might get - especially about changes following WineHQ-Devel. Maybe Wine Devs could hint to the current problem. -- 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

[Bug 59480] New: Hoyle Word Games (1999) crashes on startup in Wine 11.0
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59480 Bug ID: 59480 Summary: Hoyle Word Games (1999) crashes on startup in Wine 11.0 Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: DSKJConserver(a)gmail.com Distribution: --- Created attachment 80475 --> http://bugs.winehq.org/attachment.cgi?id=80475 The bug report is attached. Hoyle Word Games (1999) crashes in Wine 11.0 Steps to reproduce: 1. Install Hoyle Word Games (1999) 2. Run using: wine wordgame.exe 3. Crash occurs System: Wine build: wine-11.0 Platform: x86_64 (guest: i386) Version: Windows 98 Host system: Linux Host version: 6.8.0-101-generic Terminal log attached. Note: Even when executed properly, this game fails to operate as intended. Furthermore, it does not provide any method to close the blank windows, leaving me unable to proceed unless I discover a way to terminate the program or perform a forced restart of the computer. -- 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 59470] New: MetaEditor 5 generates a lot of error messages in ~/.xsession-errors
by WineHQ Bugzilla March 6, 2026

March 6, 2026

http://bugs.winehq.org/show_bug.cgi?id=59470 Bug ID: 59470 Summary: MetaEditor 5 generates a lot of error messages in ~/.xsession-errors Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: luke2135(a)gmail.com Distribution: --- If I start MetaEditor 5 the ~/.xsession-errors file starts to fill up with messages: 0120:fixme:file:GetLongPathNameW UNC pathname L"\\\\?\\C:\\Program Files\\MetaTrader 5\\MQL5" Not sure exactly how many messages are generated but it is somewhere in the range of 10-100 per second. The file quickly reaches MiB in size. -- 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

[Bug 59489] New: Dr.Explain 7.0: no background for selected text in a custom edit control
by WineHQ Bugzilla March 5, 2026

March 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59489 Bug ID: 59489 Summary: Dr.Explain 7.0: no background for selected text in a custom edit control Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)list.winehq.org Reporter: vladislav.kochemaev(a)vd42.net Distribution: --- Created attachment 80487 --> http://bugs.winehq.org/attachment.cgi?id=80487 Complete terminal output Install and launch Dr.Explain > wait for the Continue using a free restricted license button to appear and click it > open the Settings menu and select Application settings... > in the application settings dialog, click on the path to the right of the Autosave folder label (for example, C:\users\vd42\AppData\Roaming\DrExplain\Autosave) > press Ctrl+A to select all text. The selected text has no background. -- 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

[Bug 59488] New: Dr.Explain 7.0: incorrect positioning of the caret when clicking in a custom edit control
by WineHQ Bugzilla March 5, 2026

March 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59488 Bug ID: 59488 Summary: Dr.Explain 7.0: incorrect positioning of the caret when clicking in a custom edit control Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)list.winehq.org Reporter: vladislav.kochemaev(a)vd42.net Distribution: --- Created attachment 80486 --> http://bugs.winehq.org/attachment.cgi?id=80486 Complete terminal output Install and launch Dr.Explain > wait for the Continue using a free restricted license button to appear and click it > open the Settings menu and select Application settings... > in the application settings dialog, click on the path to the right of the Autosave folder label (for example, C:\users\vd42\AppData\Roaming\DrExplain\Autosave). The caret will be placed at the beginning of the text, not where you clicked. -- 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

[Bug 59487] New: Dr.Explain 7.0: crash in a focused custom edit control containing an empty string
by WineHQ Bugzilla March 5, 2026

March 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=59487 Bug ID: 59487 Summary: Dr.Explain 7.0: crash in a focused custom edit control containing an empty string Product: Wine Version: 11.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)list.winehq.org Reporter: vladislav.kochemaev(a)vd42.net Distribution: --- Created attachment 80484 --> http://bugs.winehq.org/attachment.cgi?id=80484 Complete terminal output with WINEDEBUG=+dwrite Launch Dr.Explain > click the Activate Dr.Explain button. The activation dialog opens, and the edit control (which is initially empty) receives focus, and the program crashes. I suspect the issue is in the function dwrite:dwritetextlayout_HitTestTextPosition. -- 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

[Bug 47279] New: TP-Link PowerLineUtility installs but does nothing
by wine-bugs＠winehq.org March 3, 2026

March 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=47279 Bug ID: 47279 Summary: TP-Link PowerLineUtility installs but does nothing Product: Wine Version: 4.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dave(a)davehigton.me.uk Distribution: --- The TP-Link PowerLineUtility.exe installes OK under wine 4.9 (my thanks to the team for fixing the bug I reported recently which prevented installation). Running the installed app offers me "Trust and launch", whereupon I get the "round hourglass" for about 15 seconds, then... nothing. No error window, no nothing. It should be accessing the status and configuration of the power line modems that I have. The Linux box it's on is communicating over them to post this message. The app in question can be downloaded from https://static.tp-link.com/2018/201809/20180904/PowerLineUtility_Win_180816… -- 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 52570] New: d3d:debug_d3dformat Unrecognized 0x34324644 & 0x36314644 WINED3DFORMAT
by WineHQ Bugzilla March 3, 2026

March 3, 2026

https://bugs.winehq.org/show_bug.cgi?id=52570 Bug ID: 52570 Summary: d3d:debug_d3dformat Unrecognized 0x34324644 & 0x36314644 WINED3DFORMAT Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Hi all! It looks like there are present two unimplemented ATI texture features in WineD3D. I can confirm this for the Unigine Sanctuary benchmark. When WineD3D is used, I get on startup an "Unrecognized 0x34324644 (as fourcc: DF24)" and "Unrecognized 0x36314644 (as fourcc: DF16)" error message. Shortly after this the benchmark stops / halts. There is at the CLI the following information avaiable: ---- Render ---- Renderer: ATI R500 256Mb Direct3D9 desc: ATI Radeon X1600 Series Direct3D9 driver: atiumdag.dll Found required D3DPTEXTURECAPS_CUBEMAP Found required D3DPTEXTURECAPS_VOLUMEMAP Found required D3DPTADDRESSCAPS_WRAP Found required D3DPTADDRESSCAPS_CLAMP Found required D3DCAPS2_CANAUTOGENMIPMAP Found optional Vertex shader 3.0 Found optional Pixel shader 3.0 Found optional Vertex texture fetch Found optional HDR blending Found optional HDR filtering Found optional NULL texture Found optional RGB10A2 texture Found optional DXT texture compression Found optional ATI texture compression 1 Found optional ATI texture compression 2 0110:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! 0110:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table. 0110:fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT! 0110:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table. 0110:fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT! 0110:fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table. Found optional NVIDIA hardware shadow Found ATI alpha to coverage Found optional NVIDIA alpha to coverage Maximum texture width: 4096 Maximum texture height: 4096 Maximum render targets: 4 Interestingly this doesn't occur when Gallium Nine is used: ---- Render ---- Renderer: ATI R500 256Mb Direct3D9 desc: ATI Radeon X1600 Series Direct3D9 driver: atiumdag.dll Found required D3DPTEXTURECAPS_CUBEMAP Found required D3DPTEXTURECAPS_VOLUMEMAP Found required D3DPTADDRESSCAPS_WRAP Found required D3DPTADDRESSCAPS_CLAMP Found required D3DCAPS2_CANAUTOGENMIPMAP Found optional Vertex shader 3.0 Found optional Pixel shader 3.0 Found optional Vertex texture fetch Found optional HDR blending Found optional HDR filtering Found optional NULL texture Found optional RGB10A2 texture Found optional DXT texture compression Found optional ATI texture compression 1 Found optional ATI texture compression 2 Found optional ATI texture fetch 4 Found optional ATI hardware shadow Found optional NVIDIA hardware shadow Found ATI alpha to coverage Found optional NVIDIA alpha to coverage Maximum texture width: 4096 Maximum texture height: 4096 Maximum render targets: 4 So it looks that the "ATI texture fetch 4" and "ATI hardware shadow" features are not implemented in WineD3D. ;-) And by the way, the function "Vertex texture fetch" isn't supported by all ATI R500 based hardware so it shouldn't be listed as avaiable. Regarding this there exist a bug report on Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6053 -- 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 59485] New: Everquest Mouse clicks via Gamescope with multiple concurrent instances under wayland/kde
by WineHQ Bugzilla March 3, 2026

March 3, 2026

http://bugs.winehq.org/show_bug.cgi?id=59485 Bug ID: 59485 Summary: Everquest Mouse clicks via Gamescope with multiple concurrent instances under wayland/kde Product: Wine-staging Version: 11.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tlindell(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 80481 --> http://bugs.winehq.org/attachment.cgi?id=80481 Stand alone fix blunt force on directx8 I ran into this issue running EverQuest under Wine 11.1 inside gamescope (multiple concurrent instances on Wayland/KDE Plasma 6). Mouse movement works but clicks are completely dead in-game. Traced it to dlls/dinput/mouse.c — DirectInput8 enables use_raw_input which routes button events through XI2 RawButtonPress. Gamescope's XWayland translates wl_pointer.button into core X11 ButtonPress but doesn't generate XI2 RawButtonPress events (those come from xf86-input which isn't wired to the Wayland pointer protocol). So DirectInput8 sees motion via XI2 RawMotion but never gets button events. Disabling use_raw_input for DirectInput8 forces the WH_MOUSE_LL hook fallback which reads standard WM_LBUTTONDOWN/WM_RBUTTONDOWN from core X11 ButtonPress — those work fine under XWayland. Attaching a patch against Wine 11.1. It's a blunt workaround (unconditionally disables raw input for dinput8 mouse) — a proper fix would probably detect whether XI2 RawButtonPress is actually available at runtime and fall back automatically. To reproduce: # Wine prefix with EverQuest installed at drive_c/EverQuest/ export WINEPREFIX=~/eq-prefix # eqclient.ini must have: Width=1920, Height=1080, Fullscreen=1 # Launch under gamescope with --force-grab-cursor: gamescope -w 1920 -h 1080 -W 1920 -H 1080 --backend sdl --force-grab-cursor -- \ wine eqgame.exe patchme # Mouse movement works, clicks do nothing. # Launch a second instance in another terminal and the issue is consistent. # Without gamescope (plain: wine eqgame.exe patchme) clicks work fine. -- 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 0