October 2024 - Wine-Bugs - list.winehq.org

[Bug 57320] New: Zenless zone zero after losing focus is no longer responsive to gamepad input
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=57320 Bug ID: 57320 Summary: Zenless zone zero after losing focus is no longer responsive to gamepad input Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: francisco278herrera(a)gmail.com Distribution: --- Zenless zone zero after losing focus is no longer responsive to gamepad input. To reproduce install the game from the official website https://zenless.hoyoverse.com/en-us/ once the game is downloaded and installed, connect a gamepad with xinput support via USB and start the game. You will need to create an account for the game, this has its own bugs in wine but they belong in another bug report. You will also need to install dxvk using winetricks. Once in game, if the game has not lost focus so far, i.e. you haven't switched apps with alt tab on KDE or gnome, then the gamepad should work well with the game. But as soon as you switch apps using alt tab and then return to the game, the gamepad stops working with the game. -- 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 56077] New: [9.0_rc regression] C&C Generals Zero Hour fails to startup with: err:module:DelayLoadFailureHook failed to delay load ole32.dll.CLSIDFromString
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=56077 Bug ID: 56077 Summary: [9.0_rc regression] C&C Generals Zero Hour fails to startup with: err:module:DelayLoadFailureHook failed to delay load ole32.dll.CLSIDFromString Product: Wine Version: 9.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: herrtimson(a)yahoo.de Distribution: --- hey everyone, I've got a wine prefix for C&C Generals which works just fine with wine-8.0.2. Now that I upgraded to wine-9.0_rc3 for testing, it is pretty broken: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 1 (X_CreateWindow) Resource id in failed request: 0x4000004 Serial number of failed request: 184 Current serial number in output stream: 204 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 1 (X_CreateWindow) Resource id in failed request: 0x4000004 Serial number of failed request: 48 Current serial number in output stream: 52 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 1 (X_CreateWindow) Resource id in failed request: 0x4000004 Serial number of failed request: 48 Current serial number in output stream: 52 0024:err:xrandr:xrandr_get_screen_resources Failed to get screen resources. 0024:err:xrandr:xrandr14_get_gpus Failed to get gpus 0024:fixme:exec:SHELL_execute flags ignored: 0x00000100 0024:err:module:import_dll Library coml2.dll (which is needed by L"C:\\windows\\system32\\ole32.dll") not found 0024:err:module:DelayLoadFailureHook failed to delay load ole32.dll.CLSIDFromString wine: Call from 7BC42CDC to unimplemented function ole32.dll.CLSIDFromString, aborting wine: Unimplemented function ole32.dll.CLSIDFromString called at address 7BC42CDC (thread 0024), starting debugger... 013c:err:xrandr:xrandr_get_screen_resources Failed to get screen resources. 013c:err:xrandr:xrandr14_get_gpus Failed to get gpus X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 1 (X_CreateWindow) Resource id in failed request: 0x4000004 Serial number of failed request: 48 Current serial number in output stream: 52 user(a)tuxbox ~ $ 014c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x7eb4e655 wine client error:14c: -- 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 6

[Bug 56817] New: Wuthering Waves launcher doesn't know what browser to use
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=56817 Bug ID: 56817 Summary: Wuthering Waves launcher doesn't know what browser to use Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: francisco278herrera(a)gmail.com Distribution: --- The links for events and social media sometimes open on Chrome and other times on Firefox even though only chrome is the default browser, i downloaded the same installer several times and this behavior changes depending on which one is used to install the launcher, even though they all have the same version number, once installed the launcher only opens links in firefox or in chrome, or doesn't work but tries to use firefox. once the launcher is installed this behavior doesn't change, this happens even when winetricks is not installed Steps to reproduce: on kubuntu 24.04, Download the wuthering waves installer from the official website: https://wutheringwaves.kurogames.com/en/ then create a new wine prefix using winetricks, but don't change or download anything in it then using the winetricks menu run the installer, when the installer closes the launcher for wuthering waves opens then wait until the links in the launcher appear which can take up to around 10 minutes even on windows and then click on them and see which browser they open on then close the launcher, open the start menu on kde, search uninstall wuthering waves then click on it and uninstall wuthering waves then repeat these steps several times around 5 and see which browsers the links open on, sometimes they open on chrome and other times they open on firefox, on windows they always open on the default browser which i have set to chrome -- 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 11

[Bug 44901] New: DS4Windows crashes DS4 Driver
by wine-bugs＠winehq.org Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=44901 Bug ID: 44901 Summary: DS4Windows crashes DS4 Driver Product: Wine Version: 3.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: romulasry(a)gmail.com Distribution: --- Created attachment 60984 --> https://bugs.winehq.org/attachment.cgi?id=60984 backtrace Crashes on the latest Version 1.4.52 of the application. -- 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 8

[Bug 56791] New: Resident Evil - Operation Raccoonn City only work on the 6.x API
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=56791 Bug ID: 56791 Summary: Resident Evil - Operation Raccoonn City only work on the 6.x API Product: Wine Version: 9.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ribbon_45(a)proton.me Distribution: --- This crash bug is a regression that make these games only work on 6.x versions of Wine. I tested on 5.x versions and 7.x versions and newer. These games don't work on 9.0 and 9.10 versions. My guess: the bug seems to be related to video decoding. The crash log says: "wine: Unhandled page fault on write access to 09DA8140 at address 016CB76C (thread 017c), starting debugger..." (Sorry for the lack of additional information, this bug is boring) -- 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 6

[Bug 48081] New: Oregon Trail II will not start in 16-bit mode
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=48081 Bug ID: 48081 Summary: Oregon Trail II will not start in 16-bit mode Product: Wine Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sebastian(a)stillion.com Distribution: --- Created attachment 65632 --> https://bugs.winehq.org/attachment.cgi?id=65632 Detailed report of the bug The 16-bit version of Oregon Trail II will not run. It will crash if you try to run it. Will run on 32-bit and 16-bit versions of Windows. -- 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 54712] New: ntdll:rtl times out on Windows 10 1607
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=54712 Bug ID: 54712 Summary: ntdll:rtl times out on Windows 10 1607 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:rtl times out on Windows 10 1607: [...] rtl.c:2790: Running test 23 (compressed_size=5, uncompressed_size=0, status=0xc0000242) ntdll:rtl:00a4 done (258) in 120s 2231B See https://test.winehq.org/data/patterns.html#ntdll:rtl The timeouts started on 2022-09-06 and have been systematic since. However when run on its own the test does not time out and usually runs in under 1s. The timeout always happens after the "test 23" trace which is also the last test of test_RtlDecompressBuffer(). Given that the test usually runs pretty fast it is probable that one of the tests that follows causes a freeze on Windows 10 1607. -- 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 49097] New: Treeview unduly handles WM_SYSKEYDOWN
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=49097 Bug ID: 49097 Summary: Treeview unduly handles WM_SYSKEYDOWN Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: contact(a)kcsoftwares.com Distribution: --- Treeview unduly handles WM_SYSKEYDOWN Refer to treeview.c case WM_KEYDOWN: case WM_SYSKEYDOWN: return TREEVIEW_KeyDown(infoPtr, wParam); No such processing on Listview : case WM_KEYDOWN: return LISTVIEW_KeyDown(infoPtr, (INT)wParam, (LONG)lParam); As a consequence, WM_SYSKEYDOWN not correctly passed to parent Wnd if focus is on a Treeview control. Proof of concept : Use ReactOS. Open Regedit or Event Viewer. Put focus on treeview. Alt+F4 does nothing (WM_SYSKEYDOWN "stuck" at Treeview component level) Suggested patch : change case WM_KEYDOWN: case WM_SYSKEYDOWN: return TREEVIEW_KeyDown(infoPtr, wParam); into case WM_KEYDOWN: return TREEVIEW_KeyDown(infoPtr, wParam); as no reason to handle WM_SYSKEYDOWN at component level. -- 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 12

[Bug 56684] New: native wayland restart to xorg causes freezes
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=56684 Bug ID: 56684 Summary: native wayland restart to xorg causes freezes Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- from memory (maybe missed something, did something extra) - start wayland - run a game with native wine (star wars kotor) - regedit and change back to `x11,wine` - exit wayland (wine server is still running) - start xorg - run a game... bad times ensue. freezes, have to kill everything in tty, kill wine probably low priority as ppl shouldn't do this once their environment is set up and working. idk the behavior of wine and restarting itself. -- 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 6

[Bug 56387] New: Buttons in Laragon not responding to mouse clicks
by WineHQ Bugzilla Jan. 14, 2026

Jan. 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=56387 Bug ID: 56387 Summary: Buttons in Laragon not responding to mouse clicks Product: Wine Version: 9.3 Hardware: x86-64 URL: https://github.com/leokhoa/laragon/releases/download/6 .0.0/laragon-wamp.exe OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tobbi.bugs(a)googlemail.com % wine --version wine-9.3 % openssl sha256 laragon-wamp.exe SHA2-256(laragon-wamp.exe)= 333a8eaa06b0d4078027deec2e04fb59c8bbdc06c03398c9253e637aeb2c00d8 When I open Laragon, none of the buttons on the main screen respond to mouse clicks. Steps to reproduce: 1. Download and install laragon. 2. Open Laragon from C:/laragon/laragon.exe -- 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