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

[Bug 53619] New: World of Warcraft Shadowlands randomly crashes
by WineHQ Bugzilla Jan. 31, 2026

Jan. 31, 2026

https://bugs.winehq.org/show_bug.cgi?id=53619 Bug ID: 53619 Summary: World of Warcraft Shadowlands randomly crashes Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cianuro2036(a)protonmail.com Distribution: --- This is something that has happened on multiple hardware, platforms and OS distros. This is also something that has been happening for a while, I just decided to report it because It can affect some parts of the game, such as rated PVP. The particular error logs as follows: 05f4:err:seh:dispatch_exception unknown exception (code=c0000420) raised wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart. How to reproduce: This feels 'random' but makes me _think_ it could be a memory leak issue. If you're in highly populated areas _or_ highly demanding zones, it can trigger itself. Two recent scenarios I can recall - First, doing multiple arena matches and waiting for the queue in Oribos. The crash happened specifically during arena. - Second, doing the Ashran Brawl Battleground. This battleground is very, very long and has a lot of people around. In both scenarios there is a slowdown in FPS in both areas. -- 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 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 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 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 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

[Bug 35613] New: Foxit Reader unable to validate digital signatures
by wine-bugs＠winehq.org Jan. 30, 2026

Jan. 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=35613 Bug ID: 35613 Summary: Foxit Reader unable to validate digital signatures Product: Wine Version: 1.7.12 Hardware: x86 URL: http://www.foxitsoftware.com/downloads/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Classification: Unclassified Created attachment 47561 --> http://bugs.winehq.org/attachment.cgi?id=47561 Log from opening sample PDF and clicking on signature Tested with FoxitReader612.12241_enu_Setup.exe and sample signed PDF downloaded from http://blogs.adobe.com/security/SampleSignedPDFDocument.pdf. To reproduce: 1. Install Foxit Reader. 2. Open sample signed PDF from Adobe. 3. Click on the signature in the document. 4. A Signature Validation Status window pops up that says: Signature is INVALID. - The document has been altered or corrupted since the Signature was applied. - The signer's identity has not yet been verified. 5. Clicking on the Signature Properties button brings up the Signature Properties window, but the Show Certificate button is greyed out. In Windows (tested XP & 7 in a VM), the first time you try to validate the signature the message in the Signature Validation Status window is: Signature validity is UNKNOWN. - The document has not been modified since the signature was applied. - The signer's identity is unknown because it has not been included in your list of trusted identities and none of its parent certificates are trusted. - The certificate has exceeded the time of validity. However, in Windows the Show Certificate button on the Signature Properties window works and takes you to a dialog that allows you to import the certificate. Once that is done, the message from clicking on the signature is: Signature is VALID, signed by John B Harris ,jbharris(a)adobe.com> - The document has not been modified since this signature was applied. - The signer's identity is valid. - The certificate has exceeded the time of validity. I'm attaching a log from opening the sample PDF and clicking on the signature in a clean wineprefix. Copying mfc42u.dll and msasn1.dll to the wineprefix's system32 directory gets rid of the console error messages about them, but does not change the app's behavior. -- 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 11

[Bug 59056] New: Kontakt 8: fails to install: "FALSE"
by WineHQ Bugzilla Jan. 30, 2026

Jan. 30, 2026

http://bugs.winehq.org/show_bug.cgi?id=59056 Bug ID: 59056 Summary: Kontakt 8: fails to install: "FALSE" Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)list.winehq.org Reporter: mail+winehq(a)astr.cc Distribution: --- Created attachment 79824 --> http://bugs.winehq.org/attachment.cgi?id=79824 install traces for both kontakt 7 and 8 When trying to install Native Instruments' Kontakt 8 (both full and Player), the installer fails with the error "The Native Instruments Kontakt 8 Setup has failed: "FALSE". Please check your settings and try again". Kontakt 7 (Player), which uses a nearly identical installer setup (InstallAware Wizard-based), installs just fine. The Player version is free, but requires going through the Native Access download manager (which itself is annoying to get working on Wine, see AppDB): https://www.native-instruments.com/en/products/komplete/samplers/kontakt-8-… I'm working with these binaries: 73632dc3fa6ac54365ca9c3f892083598fd42c72 Kontakt 7 7.10.9 Setup PC.exe c71edf4f829dc3cbf34a92d152cccbb6092c5666 Kontakt 8 8.7.2 Setup PC.exe I've attached install logs on a fresh prefix with WINEDEBUG=+msi,+msidb,+warn for both 7 and 8 so you can look at the differences. Notably, it seems like the .msi file by Kontakt 8 extracted to C:\Windows\Installer is malformed in some way - trying to open it with msitools yields "Table size is invalid 148/3" when loading _Tables (and this is in the Wine logs as well), and real Windows agrees with this. The string pool seems to have a lot of empty(?) entries at the end (see string_totalsize traces), which for 8 is enough to push it past the 2^16 threshold in msi_save_string_table (https://gitlab.winehq.org/wine/wine/-/blob/4dfbf077cf708e4bbffa8e086d78d665…) This then makes the _Tables table fail to load. If I run the installer in a windows VM, the dropped .msi file won't have the blank entries at the end, and will install correctly (with a string pool size of ~50k rather than ~80k). I'm not sure what's causing the extra entries and whether *that's* the bug, or if it just needs to be saved differently? -- 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