February 2026 - Wine-GitLab

Re: [PATCH v31 0/2] MR9414: shlwapi: Handling of "C:\...xx" in PathCanonicalize[AW].
by Thomas Csovcsity (＠thc13) Feb. 3, 2026

Feb. 3, 2026

Rebased after code freeze. Will leave it untouched for review until i receive other advise. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9414#note_128691

1 0

[PATCH v2 0/1] MR10011: programs/explorer: Follow up c31e65fd3bde7, keep systray visible with taskbar enabled
by Twaik Yont (＠twaik) Feb. 3, 2026

Feb. 3, 2026

This is a follow-up to c31e65fd3bde71234668507a9e15780d567c0a51, which introduced a clear separation between a standalone systray window (show_systray) and the systray area embedded in the taskbar (enable_taskbar). While the standalone systray is correctly disabled when the shell taskbar is enabled, parts of the systray visibility logic still treated show_systray as a global on/off switch. As a result, WM_DISPLAYCHANGE would hide the systray entirely when show_systray was false, even though the taskbar (and its dedicated systray area) was enabled. This caused the systray and its balloons to disappear permanently after a display mode change in desktop=shell configurations. Adjust the visibility conditions so that an enabled taskbar always allows the systray to remain visible, restoring the behavior implied by c31e65fd3bde71234668507a9e15780d567c0a51 and preventing the systray from being hidden on display changes when it is embedded in the taskbar. -- v2: programs/explorer: Follow up c31e65fd3bde7, keep systray visible with taskbar enabled https://gitlab.winehq.org/wine/wine/-/merge_requests/10011

3 3

[PATCH 0/1] MR10011: programs/explorer: Follow up c31e65fd3bde7, keep systray visible with taskbar enabled
by Twaik Yont (＠twaik) Feb. 3, 2026

Feb. 3, 2026

This is a follow-up to c31e65fd3bde71234668507a9e15780d567c0a51, which introduced a clear separation between a standalone systray window (show_systray) and the systray area embedded in the taskbar (enable_taskbar). While the standalone systray is correctly disabled when the shell taskbar is enabled, parts of the systray visibility logic still treated show_systray as a global on/off switch. As a result, WM_DISPLAYCHANGE would hide the systray entirely when show_systray was false, even though the taskbar (and its dedicated systray area) was enabled. This caused the systray and its balloons to disappear permanently after a display mode change in desktop=shell configurations. Adjust the visibility conditions so that an enabled taskbar always allows the systray to remain visible, restoring the behavior implied by c31e65fd3bde71234668507a9e15780d567c0a51 and preventing the systray from being hidden on display changes when it is embedded in the taskbar. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10011

3 7

[PATCH 0/2] MR10004: jscript: Fix DISPATCH_METHOD | DISPATCH_PROPERTYGET in ES5+ modes.
by Gabriel Ivăncescu Feb. 3, 2026

Feb. 3, 2026

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10004

3 4

[PATCH v8 0/3] MR10007: Support enabling/disabling IME on winewayland
by Ziia Shi (＠mkrsym1) Feb. 3, 2026

Feb. 3, 2026

Currently, IME is always enabled for all applications. This can cause some very annoying issues on winewayland. For example, fcitx takes over the character repeat functionality when enabled, and does it via repeatedly sending sequences of keyup/keydown, which leads to applications not being able to track hold duration of a button (can be reproduced on any game which requires holding a letter key). The spec states that the enable request should only be sent when a text edit is focused, and a disable request should be sent when it is unfocused. Windows provides a "similar-ish" mechanism: applications can use ImmAssociateContext/ImmAssociateContextEx to associate an IMC when IME should be enabled, and set associated IMC to null when it should be disabled. From my rather limited testing, it is implemented this way in Chromium/CEF, QT and Unity. Setting it to null internally results in deactivation of the currently associated context. This MR makes the ImeSetActiveContext function of the builtin IME utilize a new driver function to communicate activation status. It does not take into account which specific context was activated, thus semi-stub. This fixes behavior of applications using the above-mentioned components. I only implemented it for winewayland, it probably should also be implemented for winex11 too, but I'm not sure how. ~~Unfortunately this breaks IME input in Wine comctl32/user32 components. I am not sure how it is supposed to behave on Windows or how to test it at the current point, will look into it later. Having IME on by default appears to "fix" it, but that is very likely not the Windows behavior; moreover, at least Unity does not disable IME on start, which causes the above-mentioned issue to occur until a textbox is manually focused and unfocused.~~ Fixed -- v8: winewayland: Implement SetIMEEnabled driver call. imm32: Call SetIMEEnabled in ImeSetActiveContext. win32u: Add SetIMEEnabled driver call. https://gitlab.winehq.org/wine/wine/-/merge_requests/10007

3 5

[PATCH v2 0/1] MR10017: comctl32 : center icon in LV_VIEW_ICON mode by adjusting icon position calculation.
by Maotong Zhang (＠xiaotong) Feb. 3, 2026

Feb. 3, 2026

Fix icon display issue in "Faststone Image Viewer". -- v2: comctl32 : center icon in LV_VIEW_ICON mode by adjusting icon position calculation. https://gitlab.winehq.org/wine/wine/-/merge_requests/10017

3 4

[PATCH 0/1] MR10016: dbghelp: Rewrite EnumerateLoadedModulesW64 in terms of CreateToolhelp32Snapshot.
by Yuxuan Shui (＠yshui) Feb. 3, 2026

Feb. 3, 2026

Follow up to !9371. Did some quick, unscientific performance tests, EnumerateLoadedModulesW64 is massively faster after this change, so I think everything is working. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10016

3 3

[PATCH 0/1] MR9986: OpenGL32 check if HDC is invalid
by Goran Kovac (＠gorankovacstudio) Feb. 3, 2026

Feb. 3, 2026

Regression from 10.13 - https://bugs.winehq.org/show_bug.cgi?id=58506 When Waves VST tries to load it errors: 0024:warn:win:get_window_pixel_format getting format on win (nil) not supported 0024:warn:opengl:update_context Failed to re-create context for wglShareLists 0024:warn:opengl:wglMakeCurrent wglMakeCurrent returned 0xc0000005 After that it stucks in the loop and main app (DAW) needs to be SIGTERM. Fix checks if the HDC is valid before going further. This makes Waves VST load and work fine. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9986

3 8

[PATCH v7 0/3] MR10007: Support enabling/disabling IME on winewayland
by Ziia Shi (＠mkrsym1) Feb. 3, 2026

Feb. 3, 2026

Currently, IME is always enabled for all applications. This can cause some very annoying issues on winewayland. For example, fcitx takes over the character repeat functionality when enabled, and does it via repeatedly sending sequences of keyup/keydown, which leads to applications not being able to track hold duration of a button (can be reproduced on any game which requires holding a letter key). The spec states that the enable request should only be sent when a text edit is focused, and a disable request should be sent when it is unfocused. Windows provides a "similar-ish" mechanism: applications can use ImmAssociateContext/ImmAssociateContextEx to associate an IMC when IME should be enabled, and set associated IMC to null when it should be disabled. From my rather limited testing, it is implemented this way in Chromium/CEF, QT and Unity. Setting it to null internally results in deactivation of the currently associated context. This MR makes the ImeSetActiveContext function of the builtin IME utilize a new driver function to communicate activation status. It does not take into account which specific context was activated, thus semi-stub. This fixes behavior of applications using the above-mentioned components. I only implemented it for winewayland, it probably should also be implemented for winex11 too, but I'm not sure how. ~~Unfortunately this breaks IME input in Wine comctl32/user32 components. I am not sure how it is supposed to behave on Windows or how to test it at the current point, will look into it later. Having IME on by default appears to "fix" it, but that is very likely not the Windows behavior; moreover, at least Unity does not disable IME on start, which causes the above-mentioned issue to occur until a textbox is manually focused and unfocused.~~ Fixed -- v7: winewayland: Implement SetIMEEnabled driver call. https://gitlab.winehq.org/wine/wine/-/merge_requests/10007

3 7

[PATCH v7 0/4] MR359: mmdevapi: copy ContainerID property from audio driver if available
by Claire (＠ClearlyClaire) Feb. 3, 2026

Feb. 3, 2026

Some games with support for the haptic feedback and speaker features of the Sony DualSense controller select the controller's audio output by filtering on the ContainerId IMMDevice property to find one that matches the controller's HID's. This MR allows this information to be accessible from the IMMDevice's property store when the audio driver provides it (none for now, but I intend to add that feature to `winepulse.drv` and maybe `winealsa.drv`) This is made specific to containerId rather than supporting VT_CLSID on every property because Wine currently stores VT_BLOBs directly in the registry value, which does not allow us to safely disambiguate between VT_CLSID and VT_BLOB values when reading from registry. -- v7: mmdevapi: Invalidate ContainerID of unavailable audio devices. https://gitlab.winehq.org/wine/wine/-/merge_requests/359

6 11