January 2026 - Wine-bugs - list.winehq.org

[Bug 49097] New: Treeview unduly handles WM_SYSKEYDOWN
by WineHQ Bugzilla 14 Jan '26

14 Jan '26

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 54712] New: ntdll:rtl times out on Windows 10 1607
by WineHQ Bugzilla 14 Jan '26

14 Jan '26

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 57816] New: Splinter Cell: Pandora Tomorrow (2004): crashes when changing game resolution when used with DXVK
by WineHQ Bugzilla 14 Jan '26

14 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=57816 Bug ID: 57816 Summary: Splinter Cell: Pandora Tomorrow (2004): crashes when changing game resolution when used with DXVK Product: Wine Version: 10.1 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 78026 --> https://bugs.winehq.org/attachment.cgi?id=78026 output log When I change the game resolution via the options menu, the game crashes. You can also crash when you start the game (right after the introductory video). Just change the game resolution via the SplinterCell2.ini configuration file: WindowedViewportX=1600 WindowedViewportY=1200 and the SplinterCell2.ini configuration file: Resolution=1600x1200 This behavior only happens when used with DXVK. It doesn't happen with WineD3D OpenGL (it's impossible to test with WineD3D Vulkan, as it completely breaks the look of the game). And of course, it doesn't happen with winex11.drv either. - The game was installed via CD-ROM and is up to date with the latest update (v1.31). - I use labwc/wlroots as WM. - Although I'm on Arch Linux, I compile wine manually with these options: ./configure --prefix=/usr --enable-archs=i386,x86_64 --enable-win64. So I'm using the new WoW64 mode, but this behavior also happens in normal wine. -- 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 56684] New: native wayland restart to xorg causes freezes
by WineHQ Bugzilla 14 Jan '26

14 Jan '26

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 14 Jan '26

14 Jan '26

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

[Bug 47659] New: Game crashes when started
by wine-bugs＠winehq.org 14 Jan '26

14 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=47659 Bug ID: 47659 Summary: Game crashes when started Product: Wine Version: 4.14 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: phorcys19(a)gmail.com Created attachment 65102 --> https://bugs.winehq.org/attachment.cgi?id=65102 Bug report Monster Girl Rancher game (https://aryion.com/forum/viewtopic.php?f=79&t=52831) crashes on startup. -- 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 4

[Bug 41930] New: Civilization III Complete shows black terrain ( Wine compiled with OSMesa support)
by wine-bugs＠winehq.org 14 Jan '26

14 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=41930 Bug ID: 41930 Summary: Civilization III Complete shows black terrain (Wine compiled with OSMesa support) Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: michael(a)fds-team.de Regression SHA1: e618ab65ed5b623785c58ea5ece6e39895d43063 Distribution: --- Created attachment 56311 --> https://bugs.winehq.org/attachment.cgi?id=56311 screenshot This is one of the few games that I know of which makes some use of OpenGl in bitmaps. When Wine was compiled with OSMesa support, tiles containing terrain turn black as soon as I launch a game. Reproduced with Nvidia binary drivers 375.20 and nouveau/mesa. I tried Civilization III Complete (both the Steam and the GOG.com versions have this bug). Terminal output: fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 16 err:ole:CoGetClassObject class {5959df60-2911-11d1-b049-0020af30269a} not registered err:ole:CoGetClassObject no class object {5959df60-2911-11d1-b049-0020af30269a} could be created for context 0x1 Reverting the following patch on top of git fixes the problem: commit e618ab65ed5b623785c58ea5ece6e39895d43063 Author: Michael Müller <michael(a)fds-team.de> Date: Tue Feb 3 11:07:38 2015 +0100 gdi32: Fix arguments for OSMesaMakeCurrent when using 16 bit formats. Please let me know if you need debug logs. wine-1.9.24-105-g1d3b944 Fedora 24 x86_64 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 375.20 Installed packages: mesa-libOSMesa.i686 13.1.0-0.12.git95ddb37.fc24 mesa-libOSMesa.x86_64 13.1.0-0.12.git95ddb37.fc24 mesa-libOSMesa-devel.i686 13.1.0-0.12.git95ddb37.fc24 mesa-libOSMesa-devel.x86_64 13.1.0-0.12.git95ddb37.fc24 -- 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 80

[Bug 58279] New: ME: Andromeda (Steam) will not start without virtual desktop
by WineHQ Bugzilla 14 Jan '26

14 Jan '26

http://bugs.winehq.org/show_bug.cgi?id=58279 Bug ID: 58279 Summary: ME: Andromeda (Steam) will not start without virtual desktop Product: Wine Version: 10.8 Hardware: x86-64 URL: https://store.steampowered.com/app/1238000/Mass_Effect _Andromeda_Deluxe_Edition/ OS: Linux Status: NEW Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 78626 --> http://bugs.winehq.org/attachment.cgi?id=78626 Wine 10.8 console log When launching Mass Effect: Andromeda for Steam, it first launches the EA App, which then launches the game. Steam and the EA App work (with workarounds) but there appears (via htop) to be no attempt to actually load the game. Running in a virtual desktop allows the game to launch. The graphics are terrible but that's another issue. Workarounds: - arial (Bug 32342) [for Steam & EA App - both CEF] $ wine 'c:\program files (x86)\steam\steam.exe' -applaunch 1238000 I couldn't find a demo to test. -- 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 3

[Bug 57202] New: steam client stops working on wine 8.19+ on Slackware 15.0 due to mono 8.10 update
by WineHQ Bugzilla 14 Jan '26

14 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=57202 Bug ID: 57202 Summary: steam client stops working on wine 8.19+ on Slackware 15.0 due to mono 8.10 update Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: steampunque8(a)gmail.com Distribution: --- Created attachment 77100 --> https://bugs.winehq.org/attachment.cgi?id=77100 last step of bisect for steam client launch failure I recently tried to run steam client on upstream wines and found that the client will not start on any wine version 8.19 or above. I bisected the problem to the update to mono 8.1.0. The last stage of bisect is attached. When starting the client a ton of processes get created and then "Maximum number of clients reached" messages get spammed infinitely on the console. OS: Linux 5.15.140 Dist: Slackware 15.0 64 CPU: 9900k GPU: RTX 4070 I found a workaround to the problem to shut off mono as follows: export WINEDLLOVERRIDES="mscoree=" This workaround seems OK since I don't think steam client itself relies on mono but I am not sure some of the apps it launches wont. Any tips or ideas what might be happening here would be appreciated. No issues with the older wine versions up to 8.18 ran steam with mono enabled fine so I am pretty sure some update in mono 8.10 is triggering the problem. There is a good chance this is related to Slackware 15.0 distribution and has nothing to do with wine or mono issue but I don't know where to start looking for the breakage.export WINEDLLOVERRIDES="mscoree=" -- 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 18

[Bug 40167] New: theWord: popup doesn't work correctly after first Shift-MouseOver
by wine-bugs＠winehq.org 14 Jan '26

14 Jan '26

https://bugs.winehq.org/show_bug.cgi?id=40167 Bug ID: 40167 Summary: theWord: popup doesn't work correctly after first Shift-MouseOver Product: Wine Version: unspecified Hardware: x86-64 URL: http://www.theword.net/files/setup/getmulti.php/en-sma ll OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: therapon(a)roadrunner.com Distribution: Ubuntu bug is present in all versions of wine 1.1.14 through 1.9.3 MouseOver a hyperlink (cross-reference, commentary, etc.) displays a popup up with the content of whatever is linked. Instruction at bottom of popup says: Press SHIFT key and move mouse over popup to keep visible. Works properly the first time only. The only way to keep subsequent popups visible is to press SHIFT before MouseOver. To reproduce: 1. MouseOver a hyperlink. Popup displays with standard background until the mouse is moved off the link, then it disappears. 2. MouseOver a hyperlink, press SHIFT and move the mouse over the popup. Popup displays with blue gradient background until the mouse is moved off the popup. 3. MouseOver a hyperlink. Popup flashes with blue gradient background and disappears unless it has a vertical scrollbar. If it has a scrollbar, the popup displays and functions as if SHIFT had been pressed. Expected behavior: 1. MouseOver a hyperlink. Popup displays with standard background until the mouse is moved off the link, then it disappears. 2. MouseOver a hyperlink, press SHIFT and move the mouse over the popup. Popup displays with blue gradient background until the mouse is moved off the popup. 3. MouseOver a hyperlink. Popup displays with standard background until the mouse is moved off the link, then it disappears. -- 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 5