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

[Bug 43775] New: Heroes of the Storm crash on start with d3d11
by wine-bugs＠winehq.org Dec. 3, 2025

Dec. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=43775 Bug ID: 43775 Summary: Heroes of the Storm crash on start with d3d11 Product: Wine Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maxi.cass11(a)gmail.com Distribution: --- Created attachment 59282 --> https://bugs.winehq.org/attachment.cgi?id=59282 terminal Output 2.17-staging with dx11 I don't know if the bug is in the non-staging version because Battlenet crash in non-staging. My game crash on my laptop with d3d11, I need to set the -dx9 argument to correct this. -- 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 48

[Bug 55986] New: Gunner3 has flickering in fullscreen
by WineHQ Bugzilla Dec. 3, 2025

Dec. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=55986 Bug ID: 55986 Summary: Gunner3 has flickering in fullscreen Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Since wine-6.1 there is flickering when running Gunner3 in fullscreen mode. Also, from time to time old frame data is shown for a few moments making the game It works with winecfg virtual desktop mode, and making screenshots in fullscreen is hard. It looks similar to the glitches in bug 45168 (but it is unrelated). Don't try to click on a level without having the fix from bug 41977 though, it might crash. The menu is enough to reproduce the issue. -- 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 52244] New: starcraft2 crashes while loading arcade game e_gfxErrorShaderCompileFailed
by WineHQ Bugzilla Dec. 3, 2025

Dec. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=52244 Bug ID: 52244 Summary: starcraft2 crashes while loading arcade game e_gfxErrorShaderCompileFailed Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 71352 --> https://bugs.winehq.org/attachment.cgi?id=71352 console messages [cedric(a)cedric ~]$ wine --version wine-6.23 [cedric(a)cedric ~]$ uname -a Linux cedric 5.15.8-arch1-1 #1 SMP PREEMPT Tue, 14 Dec 2021 12:28:02 +0000 x86_64 GNU/Linux [cedric(a)cedric ~]$ rm -rf ~/.wine [cedric(a)cedric ~]$ wineboot [cedric(a)cedric ~]$ wine ~/.wine-sc2-ok/drive_c/Program\ Files\ $x86$/StarCraft\ II/StarCraft\ II.exe Install battle.net (it finds starcraft2), close click Play choose custom -> arcade. Type in "coop" into the search field, and click on "Wings of liberty coop 1. Liberation day", and click create lobby, and then click "start game". After the countdown, the loading screen shows up, and the progress bar goes about to half full. Then this error dialog shows up: "Starcraft II e_gfxErrorShaderCompileFailed To help us identify the problem, please describe what you were doing when the error occurred. Please use the Report ID below when communicating with Blizzard about the issue. DF97FB56-8356-44A6-A960-5BEA033C44DA [X] Send to Blizzard [Reopen] [Close]" -- 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 8

[Bug 58012] New: DOOM + DOOM II: rsaenh regression
by WineHQ Bugzilla Dec. 3, 2025

Dec. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=58012 Bug ID: 58012 Summary: DOOM + DOOM II: rsaenh regression Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rsaenh Assignee: wine-bugs(a)winehq.org Reporter: joelh(a)disroot.org Distribution: --- Created attachment 78271 --> https://bugs.winehq.org/attachment.cgi?id=78271 backtrace of doom_gog.exe DOOM + DOOM II by Nightdive Studios released in 2024. I am using the GOG.com version. The game will get past the opening screens, then crash on the main menu. It worked okay in Wine 10.2. I have tracked down the problematic commit to: fd539487b7860ff0a53474aa6fbcbe229f3f42c1 rsaenh: Use the bundled tomcrypt to replace the local copy. -- 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 23015] New: PL\SQL Developer: shows standard message boxes behind main window
by wine-bugs＠winehq.org Dec. 3, 2025

Dec. 3, 2025

http://bugs.winehq.org/show_bug.cgi?id=23015 Summary: PL\SQL Developer: shows standard message boxes behind main window Product: Wine Version: 1.2-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: comdlg32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: chaostya(a)gmail.com When I write a query in PL\SQL Developer window, then issue it against DB and then want to close the window I click [x] and it looks like nothing happens, but if I move main window down I would see a standard "question" message dialog box asking me if I want to save my changes. I'm on 1.2-rc2 and it's a regression from 1.2-rc1 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 49

[Bug 45039] New: Mono: System.UnauthorizedAccessException when trying to read from stdin when both stdout and stderr are redirected
by wine-bugs＠winehq.org Dec. 3, 2025

Dec. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=45039 Bug ID: 45039 Summary: Mono: System.UnauthorizedAccessException when trying to read from stdin when both stdout and stderr are redirected Product: Wine Version: 3.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mk+winehq1803(a)pimpmybyte.de Distribution: --- I wrote a simple C# program that reads a line from stdin and prints it in uppercase (01_shout.cs in [1]). The exe (compiled on Ubuntu with "mcs") is available for download at http://l.proggr.de/?1839m7ier It accepts interactive input when run in cmd.exe on windows 7, even with both stdout and stderr redirected (02_log_win7.txt in [1]). In Ubuntu, it crashes when trying to read the line while stdin is a TTY and both stdout and stderr are redirected (03_log_wine.txt in [1]). Ubuntu 14.04.5 LTS trusty, wine-3.6, Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1.1) Kernel 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:14:37 UTC 2018 i686 i686 i686 GNU/Linux [1] https://gist.github.com/mk-pmb/adae211e875ff11274d9b81248d033a3 -- 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

[Bug 44840] New: Icewind Dale unusably glitchy starting with Wine Version 3.2
by wine-bugs＠winehq.org Dec. 3, 2025

Dec. 3, 2025

https://bugs.winehq.org/show_bug.cgi?id=44840 Bug ID: 44840 Summary: Icewind Dale unusably glitchy starting with Wine Version 3.2 Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wodencafe(a)gmail.com Distribution: --- Starting with Wine 3.2 and on, Icewind Dale (2.0.0.11 (GOG)) is having very strange input / glitchy rendering issues. I have attached a video comparison with 3.1 where it works fine. Tested with 3.2, 3.3, and 3.4, and all have the strange input and glitchy problem. There are no additional wine modifications. Please see the video for example of problem, and comparison of when it was working with 3.1 -- 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 21

[Bug 57588] New: Guardant USB key drivers: grdkey.sys crashes
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

https://bugs.winehq.org/show_bug.cgi?id=57588 Bug ID: 57588 Summary: Guardant USB key drivers: grdkey.sys crashes Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: amorozov(a)etersoft.ru Distribution: --- Created attachment 77697 --> https://bugs.winehq.org/attachment.cgi?id=77697 Log with WINEDEBUG=+ntoskrnl,+plugplay and winedbg output I installed Guardant USB key drivers 7.0.224 from here: https://www.guardant.com/support/users/download/2238/ with WoW64 Wine build. $ md5sum GrdDrivers.exe 731d388d2ee4c1a4f45d655e4b8c9163 GrdDrivers.exe After installation windows/system32/drivers/grdkey.sys appears. And it crashes at Wine start: wine: Unhandled page fault on read access to 0000000000000008 at address 00006FFFFC8A295B (thread 00f0), starting debugger... In AddDevice handler grdkey.sys calls IoOpenDeviceRegistryKey. This results in calling get_device_instance_id -> get_device_id and sending IRP_MJ_PNP/IRP_MN_QUERY_ID with BusQueryDeviceID to the driver which calls IofCallDriver(NULL, ....) and crashes. The crash can be avoided with commenting out this line: device = IoGetAttachedDevice( device ); in get_device_id function in dlls/ntoskrnl.exe/pnp.c But I assume that the correct fix should be in avoiding to send IRPs from IoOpenDeviceRegistryKey. MSDN says that IRP_MN_QUERY_ID is sent before loading driver and calling AddDevice: https://learn.microsoft.com/en-us/windows-hardware/drivers/kernel/adding-a-… -- 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 30853] New: Wine doesn’t always handle "right alt" properly
by wine-bugs＠winehq.org Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=30853 Bug #: 30853 Summary: Wine doesn’t always handle "right alt" properly Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 40410 --> http://bugs.winehq.org/attachment.cgi?id=40410 workaround/quick and dirty fix I’m trying to get World of Warcraft working under Wine. However, I have huge trouble with key bindings (I use unusual key bindings : I use the right half of my keyboard, whereas most players use the left half). After investigation, I found 3 bugs (different behaviors between Wine and my Windows installation). The first one is the management of the right "Alt" key (labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with Spy++, I get the followings events : <03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:0 fUp:0 <03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:0 fUp:0 <03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1 Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb lp 760001 [note: wp = VK_OEM_PA2] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp c0260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp c0760001 [note: wp = VK_OEM_PA2] With xev, I get : KeyPress event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425), state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425), state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I get this under Wine : trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp a5 lp 21380001 [wp = VK_RMENU] trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp 4c lp 20260001 [wp = 'L'] trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c lp 20260001 [wp = 'l'] trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c lp e0260001 [wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp c1380001 [wp = VK_RMENU] (yes, I have a KEYUP without KEYDOWN) Wich is still not the same as Windows. So I think there is two problems here : - ISO_Level3_Shift is not properly recognized by Wine - "AltGr" doesn't have the same behavior under Wine and Windows FYI, attached patch is a workaround to have the same behavior than Windows. With it, I get this under Wine : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2 lp 1d0001 [note: wp = VK_LCONTROL] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4 lp 20380001 [note: wp = VK_LMENU] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c lp 20260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp e0260001 trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2 lp e01d0001 trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp c0380001 Which is still not the same as Windows : - Windows uses (right) control + menu (with fExtended flag for menu) whereas Wine uses left control + left menu. Not investigated if this is related to TranslateMessage. - AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message, wheras Wine send nothing. Note that I had to disable the XFilterEvent test in event.c to have those messages, otherwise nothing is sent to the program (but that’s another story for another bug report) But it suffice for my use case (WoW key bindings with right alt) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 57925] New: winewayland.drv: Games are not filled to my monitor's resolution
by WineHQ Bugzilla Nov. 30, 2025

Nov. 30, 2025

https://bugs.winehq.org/show_bug.cgi?id=57925 Bug ID: 57925 Summary: winewayland.drv: Games are not filled to my monitor's resolution Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: daniel.penalized(a)proton.me Distribution: ArchLinux Created attachment 78178 --> https://bugs.winehq.org/attachment.cgi?id=78178 SWAT 4 output log (in this log I opened the settings and tried to set the maximum resolution that the game supports) Old games (specifically Ghost Recon, Splinter Cell 1, Splinter Cell 2 and SWAT 4) won't fill to my monitor's resolution, even if I switch to a higher resolution in the game settings. This MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/6804) was supposed to work with winewayland.drv and fix this issue, but it doesn't work or fix it. However, this MR (https://gitlab.winehq.org/wine/wine/-/merge_requests/5057) does work and fixes that issue. There is a workaround (at least for SWAT 4): which is to take the game window out of fullscreen, then toggle the maximization state of the game window and put the game window back into fullscreen (In labwc/openbox terms: ToggleFullscreen > ToggleMaximize > ToggleFullscreen). I think it also works for Ghost Recon. Splinter Cell 1 even supports 16:9 resolutions, but only in game (in the menus, loadings and cut-scenes are still not filled in for my monitor's resolution) and Splinter Cell 2 is worse, there's no support for 16:9 resolutions or even a workaround. - I use labwc/wlroots as WM. - I'm using the new WoW64 mode. I did some tests with normal wine, but it's been a few weeks or months, so I'm not sure if the new WoW64 mode has any impact here, but I don't think so. (Sorry if the paraphrases seem disconnected from each other, if I'm not very clear or if I'm giving too little information. I've been doing a lot of testing over the last few hours and my mind isn't in a good place to come up with a good text here :/) -- 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 8