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

[Bug 59672] New: winhttp: DOAXVV fails with error 9003 at title screen
by WineHQ Bugzilla May 1, 2026

May 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59672 Bug ID: 59672 Summary: winhttp: DOAXVV fails with error 9003 at title screen Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)list.winehq.org Reporter: axis6404(a)proton.me Distribution: --- Description: Since the commit 355cdaf9c964078bea018e654d253d23536f2e51, DEAD OR ALIVE Xtreme Venus Vacation (DOAXVV) fails to proceed past the title screen with Error Code 9003. Environment: -OS: Debian 13 (trixie) -Desktop: KDE Plasma (X11) -Regression: Yes (identified by git bisect) Steps to reproduce: 1.Launch DOAXVV. 2.Wait for the title screen. 3."Error Code: 9003" appears and the game stops. Additional Info: The issue is resolved by reverting the aforementioned winhttp commit. -- 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 12

[Bug 59692] New: WoW MoP PTR unable to launch because it fails to load function IPHLPAPI.dll
by WineHQ Bugzilla May 1, 2026

May 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59692 Bug ID: 59692 Summary: WoW MoP PTR unable to launch because it fails to load function IPHLPAPI.dll Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)list.winehq.org Reporter: macieklin16(a)gmail.com Distribution: --- Created attachment 80802 --> http://bugs.winehq.org/attachment.cgi?id=80802 PROTON_LOG I'm having annoying issue with MoP PTR in particular (all other versions run just fine, including other PTR). The client straight up crashes with said error. I've been said on CachyOs discord server that that funcion is stub, But i'm not that tech savvy so it would point me in any direction. My specs: 9800x3d paired with rtx 5080 Environmental variables: WINE_SIMULATE_WRITECOPY=1 PROTON_USE_NTSYNC=1 MANGOHUD=1 Things I've tried so far: - switching to various proton versions (GE,CachyOs,provided by steam, basically all of them) - gemini pointed me towards changing version of windows in Winecfg but that didn't help at all - adding an override to IPHLPAPI.dll - running directly through terminal using "wine start" command All of these steps didn't even change the error output that I get, while other versions where running fine despite changes. -- 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 59712] New: `TextRenderer.MeasureText()` ignores trailing spaces
by WineHQ Bugzilla May 1, 2026

May 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59712 Bug ID: 59712 Summary: `TextRenderer.MeasureText()` ignores trailing spaces Product: Framework Mono Version: 6.12.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: System.Windows.Forms Assignee: wine-bugs(a)list.winehq.org Reporter: matthias.klaey(a)gmx.ch CC: madewokherd(a)gmail.com Distribution: --- Created attachment 80848 --> http://bugs.winehq.org/attachment.cgi?id=80848 [Windows 11 = equal width measured], [Mono Debian WSL = trailing spaces ignored] As visible in the attached screenshots, `TextRenderer.MeasureText()` ignores trailing spaces. Here's the repro code snipped: ``` var text = listBox_OwnerDraw.Items[e.Index].ToString(); TextRenderer.DrawText(e.Graphics, text, e.Font, e.Bounds, e.ForeColor, e.BackColor, TextFormat); var width = TextRenderer.MeasureText(e.Graphics, text, e.Font, e.Bounds.Size, TextFormat).Width; listBox_Width.Items[e.Index] = $"Width = {width}"; ``` Origin: https://sourceforge.net/p/y-a-terminal/code/HEAD/tree/trunk/YAT/YATLib/YAT.… -- 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 57852] New: Call from 7BD748A5 to unimplemented function imagehlp.dll.ReBaseImage64, aborting
by WineHQ Bugzilla May 1, 2026

May 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=57852 Bug ID: 57852 Summary: Call from 7BD748A5 to unimplemented function imagehlp.dll.ReBaseImage64, aborting Product: Wine Version: 10.2 Hardware: x86-64 OS: FreeBSD Status: NEW Keywords: download Severity: normal Priority: P2 Component: imagehlp Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com I got the Win32 version of OpenOffice (Apache OpenOffice, "AOO") to successfully build on FreeBSD with Wine + Cygwin + Windows SDK, and this was one of the Wine bugs I had to work around during the build. The problem is in the main/postprocess/rebase directory, where it tries to rebase binaries, ultimately calling C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\rebase (from the Windows SDK), which tries to call the unimplemented function imagehlp.dll.ReBaseImage64, which causes a crash during the build. Since rebasing is just done for better performance, it's not critical and can be worked around by commenting out the relevant makefile command. Still, Wine should ideally support this API, and it's good to document applications that need it. For further details please see the email where I described my experiences, and other Wine bugs I found: https://lists.apache.org/thread/x3p7mv0py2s5hw3cvrm1d3krxgb7cq9k Also if you want to reproduce, you can try compiling OpenOffice on Wine, but it's a very complicated build environment and takes many hours to run, and this bug only happens near the end. See the build guide on https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_s… and the extra instructions in the email above. And it is remarkable that Wine works so well, when building a project with ~70000 C++ files, 12 million lines of code, 37 external libraries, code generation during the build, calls to many Cygwin tools and Perl scripts, Java and Ant, .NET tools, and lots more. Only 6 Wine bugs were found, of which 3 are already fixed in Wine 10.2, and the other 3 have workarounds. -- 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