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

[Bug 59008] New: Red dead redemption hangs
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59008 Bug ID: 59008 Summary: Red dead redemption hangs Product: vkd3d Version: 1.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)list.winehq.org Reporter: levanchelidze(a)gmail.com Distribution: --- Created attachment 79745 --> http://bugs.winehq.org/attachment.cgi?id=79745 terminal output On uhd 620 graphics after in game some time passes the game hangs Using wine 10.19 and installed vkd3d from winetricks BufferCount = 3. 10029.717:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sync_objects: Ensure maximum latency of 3 frames with KHR_present_wait. 10029.728:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_waiter_thread: Enabling present wait path for frame latency. 10029.728:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_init_sleep_state: Timer interval is 1.0 ms. warn: DXGI: MakeWindowAssociation: Ignoring flags 10029.751:0020:01f8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images. 10029.923:0020:01f8:info:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Got 3 swapchain images. 10030.179:0020:01f0:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Flushing disk cache (wakeup counter since last flush = 1791). It seems like application has stopped creating new PSOs for the time being. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 10063.639:0020:0024:info:vkd3d-proton:dxgi_vk_swap_chain_ChangeProperties: Reallocating swapchain (1280 x 720), BufferCount = 3. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 01d8:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 10109.104:0020:01f4:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. ^C0264:fixme:console:default_ctrl_handler Terminating process 20 on event 0 -- 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 59067] New: some Unreal Engine games don't render correctly with opengl renderer
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59067 Bug ID: 59067 Summary: some Unreal Engine games don't render correctly with opengl renderer Product: Wine Version: 10.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 79840 --> http://bugs.winehq.org/attachment.cgi?id=79840 console output for vulkan To start off, this seems to be an engine problem as I've seem this in at least 2 UE games. So, I'll be attaching two short logs from one of the games - one for opengl renderer, where the problem can be seen and one for vulkan, where it seems to display correctly. The problem is that the scene is rendered dark with opengl - not sure if it's missing textures, bad lightning or something else. Another one of those games is 'Last Hope' by Poolside Games - just start a new game, the bug is - let's say 'difficult to miss' within first 15 sec. of gameplay. It's on steam, but there were free releases of that one too. PS: unrelated problem - both of the games I'm testing this problem with also turn off my secondary screen at termination...for no apparent reason, as I'm running them windowed anyway. -- 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 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 59065] New: 32-bit foobar2000 crashes when you play files
by WineHQ Bugzilla Dec. 1, 2025

Dec. 1, 2025

http://bugs.winehq.org/show_bug.cgi?id=59065 Bug ID: 59065 Summary: 32-bit foobar2000 crashes when you play files Product: Wine-staging Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: just4steam778(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 79838 --> http://bugs.winehq.org/attachment.cgi?id=79838 Log 32-bit foobar2000 crashes when you try to play files. 64-bit foobar2000 works fine. OS: Arch Linux -- 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 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