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

[Bug 59100] New: Worms Revolution displays only black screen
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59100 Bug ID: 59100 Summary: Worms Revolution displays only black screen Product: Wine Version: 10.18 Hardware: x86-64 URL: https://store.steampowered.com/app/200170/Worms_Revolu tion/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)list.winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 4aa48c97f419ca53a08d714431ed307bfbaf9d2d Distribution: --- The game is running because sounds from the menu can be heard but the screen remains black after starting the game. Regression from Wine-10.18: commit 4aa48c97f419ca53a08d714431ed307bfbaf9d2d opengl32: Use a buffer map for gl(Draw|Read)Buffer(s). With the previous commit the game works properly. Wine-11.0-rc1 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 580.105.08 X.Org X Server 1.21.1.21 -- 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 1

[Bug 58171] New: Breath of Fire IV, Ys VI crashes on the opening video
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58171 Bug ID: 58171 Summary: Breath of Fire IV, Ys VI crashes on the opening video Product: Wine Version: 10.6 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: smazza(a)codeweavers.com Regression SHA1: 277c8924c1ecd8626b26e19206908f648cc86e2c Distribution: ArchLinux Created attachment 78459 --> http://bugs.winehq.org/attachment.cgi?id=78459 terminal output The GOG version of Breath of Fire IV and YS VI: The Ark of Naphistim crash when the first opening video is about to play. No demo versions exist. Reverting commit 277c8924c1ecd8626b26e19206908f648cc86e2c [amstream: Implement dynamic formats in ddraw stream.] fixes the crash for me. wine-10.6-71-gf7503d0a996 -- 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 7

[Bug 58811] New: Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive.
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=58811 Bug ID: 58811 Summary: Steam: Unable to display the intended GUI windows due to steamwebhelper being unresponsive. Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 2a2cc34db71a86899b69bf3ee1da52793c342019 Distribution: Gentoo Created attachment 79466 --> http://bugs.winehq.org/attachment.cgi?id=79466 terminal After 2a2cc34db71 [1], Steam appears to launch, showing its notification area icon, but no window will appear. After a while from clicking said icon, the "Steamwebhelper is not responding" window [2] will appear, with a few different options to restart things with, of which none do any better. I believe the src\vgui2\vgui_surfacelib\Win32Font.cpp (963) : Couldn't get string length line shows up only when this problem can be seen, which could be a sort of a hint at least. Building before the mentioned commit, or reverting it, and efce37afd70 due to conflicts, on current 'git master' will make it work again. Hacking on it a bit, removing the 'wcsupr(refkey->name);' line also makes it work, though maybe that is obvious in this case, and might more or less nullify the point of the uppercasing intended. (Did not try a fresh prefix and clean install of Steam yet due to the cumbersome log-in process, but hopefully that is not necessary here.) Last tested at 'wine-10.17'. Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/2a2cc34db71a86899b69bf3ee1da52… 2. https://help.steampowered.com/en/faqs/view/6C3E-9504-CC20-AF49 -- 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 25

[Bug 57770] New: Hearts of Iron IV requires 'WorldMatrix' identifier
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57770 Bug ID: 57770 Summary: Hearts of Iron IV requires 'WorldMatrix' identifier Product: vkd3d Version: 1.14 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Using DX9 (legacy) 0384:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0384:err:d3dcompiler:D3DCompile2 Shader log: 0384:err:d3dcompiler:D3DCompile2 memory:433:47: E5005: Identifier "WorldMatrix" is not declared. 1.14-345-gf1412e42 -- 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 4

[Bug 59103] New: Wine staging error
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59103 Bug ID: 59103 Summary: Wine staging error Product: Wine-staging Version: 11.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: lloydhopesallen6012(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Wine stagging error that I think is also messing with my other programs. This is my first Linux computer and I'm honestly lost on what is happening. I've tried fixing it myself but have had no luck. Started after I had battle.net installed, had it working and then had it not work the next day when I was trying to get diablo IV set up. It's now gotten to a point were I have a battle.net program running that I've tried to uninstall multiple times. The wine unistaller isn't working , and I'm getting this error. I'm also unsure on how to bring up the rest of the error log, so I only pasted what I can get into the attachment. And appreciate the help! -- 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 57332] New: ReadLink (FSCTL_GET_REPARSE_POINT) returns garbage on Wine but works on actual Windows
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=57332 Bug ID: 57332 Summary: ReadLink (FSCTL_GET_REPARSE_POINT) returns garbage on Wine but works on actual Windows Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: joshudson(a)gmail.com Distribution: --- After hammering past the other error; I found this line returns garbage on Wine but something sensible on actual Windows. https://github.com/joshudson/Emet/blob/302fe61d0b8614e2a57930fc75cffa034ba3… Whatever the garbage was, it rendered as ???? on the terminal; while it may actually be ???? it's more likely to be four unprintable characters. This time, the test harness stacktrace blew up on unwind resulting in getting a wine exception handler coming up at top level, so it may have corrupted memory too. Looks like it's a duplicate of https://bugs.winehq.org/show_bug.cgi?id=12401 but isn't. The symptoms are different, probably due to the other one trying to use reparse points (which wouldn't amaze me if they simply didn't work) and this one trying to use symbolic links (which does). -- 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 1

[Bug 1201] Microsoft Golf 99 (Direct3D game) crashes on startup (IDirect3D::EnumDevices() needs to return the RGB device second)
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=1201 --- Comment #52 from Zeb Figura <z.figura12(a)gmail.com> --- Created attachment 79912 --> http://bugs.winehq.org/attachment.cgi?id=79912 ddraw: Enumerate the ramp device. The attached patch fixes the game, and I will submit it after code freeze. Please ping me if I forget... -- 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

[Bug 1201] Microsoft Golf 99 (Direct3D game) crashes on startup (IDirect3D::EnumDevices() needs to return the RGB device second)
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=1201 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com Summary|Microsoft Golf 99 (Direct3D |Microsoft Golf 99 (Direct3D |game) crashes on startup |game) crashes on startup |(IDirect3D::EnumDevices |(IDirect3D::EnumDevices() |needs to return at least |needs to return the RGB |two devices for the |device second) |requested Direct 3D Version | |1) | Status|STAGED |NEW --- Comment #51 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Bernhard Übelacker from comment #50) > So should the Status get changed back to New and the Staged patchset removed? Yes, let's. As described in bug 19153, the wine-staging patch had a lot of extra changes that I was nervous to commit without evidence they were necessary. As it happens, one of them was. Microsoft Golf 99 chooses the GUID for the second device and uses it blindly. That requires there to be two devices, but it *also* requires the second device to be a software device, because the surface it creates the device from is a sysmem surface. The extra change necessary from the wine-staging patch to achieve this is to enumerate the RAMP device first. -- 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

[Bug 56486] New: Battle.net App Crash Cycle on Startup
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

https://bugs.winehq.org/show_bug.cgi?id=56486 Bug ID: 56486 Summary: Battle.net App Crash Cycle on Startup Product: Wine Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wschmrdr(a)gmail.com Distribution: --- Created attachment 76256 --> https://bugs.winehq.org/attachment.cgi?id=76256 Backtrace from the Program Error Starting up Battle.net App. Login screen shows with a loading circle as if it's trying to use a saved password to login. I receive a notice that there's an error and Battle.net has to shut down. I close it, and the error shows up again. This continues in a cycle until I use "wineserver -k" to exit. The backtrace saved from this has been attached. I am able to use the Settings button on the login screen for the Battle.net app, as well as typing in a username/password, but I cannot go any farther than that because there is no submit button and it doesn't seem to want to load. Be aware that I had previously been loading Starcraft II directly using the SC2Switcher.exe executable, but because a new version needs to be downloaded, I'm needing to get into the Battle.net app. Not sure if not using the app is a side effect. For the heck of it, I tried running the setup to update Battle.net, and the same thing occurred. -- 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 19

[Bug 59091] New: UbisoftConnect window completly broken
by WineHQ Bugzilla 08 Dec '25

08 Dec '25

http://bugs.winehq.org/show_bug.cgi?id=59091 Bug ID: 59091 Summary: UbisoftConnect window completly broken Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: iroalexis(a)outlook.fr Regression SHA1: b621117c652280799e209d5bec20106b1f28cb4e Distribution: ArchLinux Created attachment 79881 --> http://bugs.winehq.org/attachment.cgi?id=79881 UbisoftConnect dual window When UbisoftConnect window appaears, a first blank white window display in the middle of the screen, then a second one appears with the main interface, however this one is in the left corner of the desktop. I'm attaching a screenshot to support my description. NB: The desktop manager is Gnome Wayland 49.2 but I use winex11 driver for UbisoftConnect. In this condition, he seems to me that we use xwayland. -- 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 5