- Wine-GitLab - list.winehq.org

Re: [PATCH v2 0/1] MR10615: po: update Polish translation - approved
by Alexandre Julliard (＠julliard) April 9, 2026

April 9, 2026

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10615

1 0

Re: [PATCH v2 0/1] MR10614: po: Update Lithuanian translation. - approved
by Alexandre Julliard (＠julliard) April 9, 2026

April 9, 2026

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10614

1 0

Re: [PATCH v2 0/2] MR10605: wmvcore: Initialize COM in async_reader_callback_thread(). - approved
by Alexandre Julliard (＠julliard) April 9, 2026

April 9, 2026

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10605

1 0

[PATCH 0/5] MR10550: winex11: Keyboard layouts rework, part 1
by Matteo Bruni (＠Mystral) April 9, 2026

April 9, 2026

The idea is to improve the detection of the available keyboard layouts, normally via Xkb group names + xkbregistry, and then propagate the current layout to win32u and the PE / win32 side state. Along the way also start using `KBDTABLES` and the related newer win32u machinery that was introduced for winewayland. I'm taking a lot of inspiration (and also actual patches, or pieces of code) from the winewayland driver and Rémi's draft MR !2122. The main difference from that attempt is that I'm going to keep around `X11DRV_KEYBOARD_DetectLayout()` and use it as a fallback detection mechanism (e.g. for vncserver), but still move winex11 to `KBDTABLES` and such. You can find the current (still WIP, especially for later patches) branch at https://gitlab.winehq.org/Mystral/wine/-/commits/hl-kbl?ref_type=heads This first MR does very little, just testing the waters... -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10550

3 29

[PATCH v2 0/1] MR10490: vbscript: Return specific error codes for integer constant and Property declarations.
by Francis De Brabandere (＠francisdb) April 9, 2026

April 9, 2026

Add error productions in the bison grammar for two cases: - Expected integer constant in Dim array bounds (error 1026) e.g. Dim x("a") where a numeric value is required. - Expected Let, Set, or Get after Property keyword (error 1049) e.g. Property x without specifying the accessor type. Previously these fell through to the generic E_FAIL path in parser_error(). Now each sets the correct VBSE_EXPECTED_* error code via MAKE_VBSERROR before aborting the parse. -- v2: vbscript: Return specific error codes for integer constant and Property declarations. https://gitlab.winehq.org/wine/wine/-/merge_requests/10490

2 1

[PATCH 0/1] MR10615: po: update Polish translation
by Adam Markowski (＠AMark) April 9, 2026

April 9, 2026

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

2 1

[PATCH v3 0/4] MR10104: user32/edit: set bCaptureState flag after SetCapture()
by Ivan Ivlev (＠iviv) April 9, 2026

April 9, 2026

Edit control does not release mouse capture after WM_LBUTTONDOWN has been processed two times in a row. This MR fixes this issue by releasing capture and setting it again on WM_LBUTTONDOWN if window was already captured. I have stumbled upon the app in which edit control process WM_LBUTTONDOWN twice on one mouse click. While in windows it causes no problem, wine edit does not release capture, so other buttons inside this app become unclickable. It happens because when WM_LBUTTONDOWN is processed twice, WM_CAPTURECHANGED is sent and bCaptureState is set to FALSE, then EDIT_WM_LButtonUp does not release capture because bCaptureState is already FALSE. Thing about tests: I have added test case for this problem to be visible. I also had to use todo_wine because SendMessageA for WM_LBUTTONDOWN and WM_LBUTTONUP returns 0 in wine and 1 in windows (which is not the case for combobox test, where SendMessageА for WM_LBUTTONDOWN also returns 1 in wine). -- v3: comctl32_v6/edit: set bCaptureState flag after SetCapture() user32/edit: set bCaptureState flag after SetCapture() comctl32/tests/edit.c: Test WM_LBUTTONDOWN processing user32/tests/edit.c: Test WM_LBUTTONDOWN processing https://gitlab.winehq.org/wine/wine/-/merge_requests/10104

2 5

[PATCH v2 0/4] MR10611: LPC: Implement proper LPC system
by Rose Hellsing (＠axtlos) April 9, 2026

April 9, 2026

Until now, LPC was just a stub, any application that relied on LPC for communication would fail. This change implements parts of LPC, to allow for IPC between programs. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=30069 - fully fixed, sqlservr is able to run as expected Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=59494 - partially fixed, starmoney doesn't flat out crash anymore, but it doesn't start fully, possibly because it uses the ALPC system which was introduced in Windows Vista, the version Starmoney 10 was advertised for -- v2: ntdll/tests: Remove todo_wine from LPC port tests. server: Implement LPC message passing (NtRequestPort, NtRequestWaitReplyPort, NtReplyPort, NtReplyWaitReceivePort) and Thread termination. server: Implement LPC connection flow (NtConnectPort, NtListenPort, NtAcceptConnectPort, NtCompleteConnectPort). server: Add LPC port object infrastructure and NtCreatePort/NtCreateWaitablePort. https://gitlab.winehq.org/wine/wine/-/merge_requests/10611

2 5

[PATCH 0/1] MR10613: winemac: Handle reset parameter in ClipCursor.
by Feifan He (＠Feifan) April 9, 2026

April 9, 2026

At the moment, `ClipCursor()` sent to winemac with parameter `reset`=1 is ignored. This doesn't seem to match other drivers' behavior (e.g. winex11 does unclip if `reset`=1, and winewayland simply doesn't care about the value). It causes problem in following steps: - App (typically a game) enters fullscreen, with a display mode change. - Display mode changes, triggering cursor clipping for fullscreen. - App then leaves fullscreen, supposed to have cursor clipping reset, _but nothing happened_. - UNEXPECTED BEHAVIOR 1: Cursor remains confined in windowed mode. - App enters fullscreen again, with a display mode change identical to previous one. - UNEXPECTED BEHAVIOR 2: Clip rect shrinks to previous size of windowed mode, instead of fullscreen size. The second unexpected behavior is actually a side effect of the first one. Currently `[NSWindow setMouseConfinementRect]` is used to implement cursor clipping, and it doesn't handle window resizing "properly": the clip rect always becomes the minimum of size before and after resizing. Interestingly when app enter fullscreen again, a second `ClipCursor()` will be sent to winemac and overwrite clip rect (unclip and clip again), but it can still be skipped if the clip rect is identical to the previous one. Anyway these won't happen if `reset` is properly handled in the first place. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10613

4 3

[PATCH v3 0/1] MR10424: services: Cancel overlapped IO after timeout.
by Yuxuan Shui (＠yshui) April 9, 2026

April 9, 2026

Though WaitForSingleObject timed out, the IO operation is still running in the background. After the function process_send_command returns, the OVERLAPPED object referenced by this IO operation becomes invalid. Later, when this IO finally completes, server_select will use invalid stack memory. -- v3: services: Cancel overlapped IO after timeout. https://gitlab.winehq.org/wine/wine/-/merge_requests/10424

2 2