- Wine-Bugs - list.winehq.org

[Bug 54925] New: World of Warcraft WotLK Classic crashes on receiving inputs very frequently
by WineHQ Bugzilla Jan. 31, 2026

Jan. 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=54925 Bug ID: 54925 Summary: World of Warcraft WotLK Classic crashes on receiving inputs very frequently Product: Wine Version: 8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chagatai(a)bitigchi.xyz Distribution: --- Created attachment 74446 --> https://bugs.winehq.org/attachment.cgi?id=74446 wine debug log After logging in and selecting a character the game seems to run as normal without issues. If I don't do anything and just leave the game as is without inputs it runs for quite a while without issue. But without fail, if I start making inputs the game crashes within a minute or two. Most of the debug log is just this one line: 010c:err:sync:RtlLeaveCriticalSection section 0000000000FD26C0 (null) is not acquired And when the application stops responding it's: 01d4:err:sync:RtlpWaitForCriticalSection section 0000000000FD26F0 (null) wait timed out in thread 01d4, blocked by 0000, retrying (60 sec) At which point the application stops responding and I'm forced to terminate it. -- 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 59343] New: Debian 13 (Trixie): winehq-stable depends on non‑installable wine-stable-i386 despite WOW64 support
by WineHQ Bugzilla Jan. 31, 2026

Jan. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=59343 Bug ID: 59343 Summary: Debian 13 (Trixie): winehq-stable depends on non‑installable wine-stable-i386 despite WOW64 support Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: wine-packages Assignee: wine-bugs(a)list.winehq.org Reporter: w4wgw0okswwksckskgs8k4k0og8k4gos(a)ai.notifier.in CC: dimesio(a)earthlink.net Distribution: --- On Debian 13 (Trixie) amd64, installing winehq-stable from the WineHQ repository fails due to an unsatisfied dependency on wine-stable-i386, which is not installable on this system. The Debian/Ubuntu installation wiki states that with the new WoW64 support you no longer need to enable i386 architecture for Wine 11, but the current wine-stable:amd64 package still has a hard dependency on wine-stable-i386. > Steps to reproduce 1. Install a fresh Debian 13 (Trixie) amd64 system. 2. Add the official WineHQ repository for Trixie and import its key as documented. sudo apt update sudo apt install winehq-stable > Actual result apt fails with: wine-stable : Depends: wine-stable-i386 (= 11.0.0.0~trixie-1) but it is not installable E: Unable to correct problems, you have held broken packages. A detailed solver output (from apt/your frontend) shows: winehq-stable:amd64=11.0.0.0~trixie-1 Depends wine-stable (= 11.0.0.0~trixie-1) wine-stable:amd64=11.0.0.0~trixie-1 Depends wine-stable-i386 (= 11.0.0.0~trixie-1) but no installable candidate exists. > Expected result Either: - wine-stable:amd64 should be installable on a pure amd64 system without requiring wine-stable-i386 (new WoW64 packaging), or - The documentation should clearly state that i386 and multiarch are still required for the current Debian 13 packages, and the repository should provide a working wine-stable-i386 candidate. > Environment - Distribution: Debian 13 “Trixie” amd64 - Wine package: winehq-stable 11.0.0.0~trixie-1 - dpkg --print-architecture: amd64 - dpkg --print-foreign-architectures: Nothing - apt policy wine-stable-i386; wine-stable-i386: Installed: (none) Candidate: (none) Version table: > Comment I am using: # dpkg --list|grep wine ii libwine:amd64 10.0~repack-6 amd64 Windows API implementation - library ii wine 10.0~repack-6 all Windows API implementation - standard suite ii wine64 10.0~repack-6 amd64 Windows API implementation - 64-bit binary loader ii winetricks 20250102-1 all simple tool to work around common problems in Wine from debian APT, and I wanted to use Wine 11 from WineHQ because I heard it support WOW64 (32bit over 64bit), but since it cannot be installed without multiarch, I guess I have to wait for Debian maintainer instead :( -- 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 46416] New: World of Warcraft dx12/vkd3d crashes soon after login
by wine-bugs＠winehq.org Jan. 31, 2026

Jan. 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=46416 Bug ID: 46416 Summary: World of Warcraft dx12/vkd3d crashes soon after login Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: zurohki(a)gmail.com Distribution: --- Created attachment 63183 --> https://bugs.winehq.org/attachment.cgi?id=63183 WINEDEBUG=+seh,+dxgi,+d3d12 VKD3D_DEBUG=trace log After logging in and reaching the character select screen, World of Warcraft quickly crashes with an Error #132 exception. It doesn't matter whether you sit on that screen or choose a character and start loading in to the game world. Slackware64-current Ryzen 2700X Vega 64 wine 4.0rc4 + staging from https://github.com/lutris/wine/commits/tkg Kernel 4.20.0 Mesa master, commit 3453814 LLVM 8.0.0svn, r349003 vkd3d master, commit e13fb13 Vanilla Wine doesn't display any output at all, the screen just freezes. I have to alt-tab to the terminal and ctrl-c to kill Wine, so I can't test with it. -- 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 33

[Bug 58701] New: World of Warcraft: When launching a classic version of wow the windows is not fullscreen
by WineHQ Bugzilla Jan. 31, 2026

Jan. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=58701 Bug ID: 58701 Summary: World of Warcraft: When launching a classic version of wow the windows is not fullscreen Product: Wine-staging Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pally.squatter102(a)passfwd.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79303 --> http://bugs.winehq.org/attachment.cgi?id=79303 How the game launches together with the taskbar When I open up world of warcraft classic the game screen is not in fullscreen mode, it sets the game resolution to a custom to make space for taskbar. If you rightclick on wow task in the taskbar and tick the fullscreen checkbox it works fine, but if you close down the game and open up wow classic again it's back ot the custom game resolution to fit the taskbar into the screen. I have tried several versions of Wine, but since it happens with wine-staging I have a feeling it's somehwere there. Sadly I can't test older version of wine anymore since an update with the Blizzard Update Agent not waking up, which was solved in 10.1. I have seen people report this problem for the retail version of wow as well but works for me there so I can't really report it. There is a lutris thread asking about this issue as well. https://forums.lutris.net/t/world-of-warcraft-doesnt-go-fullscreen-anymore/… -- 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 59287] New: Allow GetTickCount() to return value counted from wineserver start instead of host OS uptime
by WineHQ Bugzilla Jan. 31, 2026

Jan. 31, 2026

http://bugs.winehq.org/show_bug.cgi?id=59287 Bug ID: 59287 Summary: Allow GetTickCount() to return value counted from wineserver start instead of host OS uptime Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)list.winehq.org Reporter: zdenek.koprivik(a)post.cz Distribution: --- In the Windows 95 times it was not very common to have a system uptime higher than 1 day. As a result, there are programs (mostly old games) which stops working when system uptime gets over circa 25 days. The issue is caused by bad programming of the apps and the int32 overflow from GetTickCount() after system uptime reach 2^31 ms (25 days). It is a pain having to reboot the whole system just to play an old game in Wine. There is an old similar feature request here: https://forum.winehq.org/viewtopic.php?t=36058 In my case, the same issue affects Heroes of Might and Magic 2: Gold from GoG. Having a per application toggle to report uptime from the wineserver's start instead of the real OS uptime would be great. It would treat the start of wineserver as a fresh Windows boot and start counting from zero. -- 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 47486] New: GsView draws one menu item with white background
by wine-bugs＠winehq.org Jan. 31, 2026

Jan. 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=47486 Bug ID: 47486 Summary: GsView draws one menu item with white background Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 64866 --> https://bugs.winehq.org/attachment.cgi?id=64866 Screenshot on wine See screenshot. -- 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 10

[Bug 59344] New: Resident Evil Village hangs before entering the main menu
by WineHQ Bugzilla Jan. 30, 2026

Jan. 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=59344 Bug ID: 59344 Summary: Resident Evil Village hangs before entering the main menu Product: Wine Version: 11.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Using proprietary driver 580.119.02 0ba4:fixme:d3d:wined3d_texture_gl_prepare_texture No GL internal format for format WINED3DFMT_NV12_PLANAR. 0ba4:err:d3d:wined3d_debug_callback 00007FA3EB30F610: "GL_INVALID_ENUM error generated. <internalFormat> not valid.". 0ba4:err:d3d:wined3d_debug_callback 00007FA3EB30F610: "GL_INVALID_VALUE error generated. Invalid texture format.". wine-11.1-114-g648e636256a -- 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 58745] New: PeekNamedPipe() unsuccessful on stdin
by WineHQ Bugzilla Jan. 30, 2026

Jan. 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=58745 Bug ID: 58745 Summary: PeekNamedPipe() unsuccessful on stdin Product: Wine Version: 10.10 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: rhaberkorn(a)fmsbw.de Created attachment 79378 --> http://bugs.winehq.org/attachment.cgi?id=79378 Test program for PeekNamedPipe() bug Trying to debug a glib2 problem occurring under Wine, I encountered what is obviously a bug in Wine itself. See the attached test program. This is what I observed on Wine: # wine peeknamedpipe.exe < somefile stat: console=0 fifo=0 ReadFile(stdin): 1 PeekNamedPipe(stdin): 0 # echo TEST | wine peeknamedpipe.exe stat: console=0 fifo=4096 ReadFile(stdin): 1 PeekNamedPipe(stdin): 0 On a real Windows 10 however it behaves differently: >peeknamedpipe.exe < somefile stat: console=0 fifo=0 ReadFile(stdin): 1 PeekNamedPipe(stdin): 0 >echo TEST | peeknamedpipe.exe stat: console=0 fifo=4096 ReadFile(stdin): 1 PeekNamedPipe(stdin): 1 In other words, PeekNamedPipe() returns FALSE on stdin when piping from another process instead of TRUE, which is returned by a real Windows 10. somefile needs to be some non-empty file of course. This was tested both on Wine 10.0 and 10.10 (wine-devel) from the FreeBSD ports tree. I filed this in kernel32 since PeekNamedPipe() is part of Kernel32.dll (at least according to the Microsoft documentation). -- 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 8

[Bug 56058] New: Drawing text background incorrect
by WineHQ Bugzilla Jan. 30, 2026

Jan. 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=56058 Bug ID: 56058 Summary: Drawing text background incorrect Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: ch.panel(a)free.fr Distribution: --- Bug in the TextOut function -when background is OPAQUE -when the "font" used defines an orientation the writing is drawn with the defined orientation but the background is drawn without orientation -- 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 17

[Bug 40365] New: D3DRM error with the game "Fighting Steel"
by wine-bugs＠winehq.org Jan. 30, 2026

Jan. 30, 2026

https://bugs.winehq.org/show_bug.cgi?id=40365 Bug ID: 40365 Summary: D3DRM error with the game "Fighting Steel" Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: e.courtial30(a)gmail.com Distribution: --- Created attachment 54052 --> https://bugs.winehq.org/attachment.cgi?id=54052 back traces Hi When I try to run the game "Fighting Steel", it starts but crashes almost immediately. The hardware checkup done by the game doesn't throw errors. This is a game using the Direct3D Retained Mode. I am running Wine on Ubuntu 15. Back traces are joined to this message. Regards -- 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 25