December 2025 - Wine-GitLab

[PATCH v13 0/3] MR7539: combase : clsid_from_string_reg() add read of CurVer key value.
by Maotong Zhang (＠xiaotong) Jan. 21, 2026

Jan. 21, 2026

If the read ProgID only has a CurVer key and no CLSID key, it will directly return CO_E_CCLASSSTRING, causing the program to fail to continue running. Add the key value for finding CurVer. -- v13: combase:clsid_from_string_reg() add read of CurVer key value. ole32:Do not zero out when not a CLSID ole32/tests:Remove now succeeding todo_wine https://gitlab.winehq.org/wine/wine/-/merge_requests/7539

4 6

[PATCH v7 0/5] MR9572: opengl32: Implement GL_EXT_memory_object_win32 for base handle types.
by Derek Lesho (＠dlesho) Jan. 20, 2026

Jan. 20, 2026

Not sure about the extension replacement mechanism. Also, should tests be failing when extensions aren't supported? -- v7: opengl32: Expose GL_EXT_memory_object_win32. win32u/opengl: Implement glImportMemoryWin32(Handle/Name)EXT for opaque handle types. opengl32, win32u: Move gl_error to wgl_context. https://gitlab.winehq.org/wine/wine/-/merge_requests/9572

3 6

[PATCH v3 0/6] MR9616: Draft: opengl32: Implement GL_EXT_semaphore_win32 for base handle types.
by Derek Lesho (＠dlesho) Jan. 20, 2026

Jan. 20, 2026

Depends on !9574 and !9572 . -- v3: opengl32: Expose GL_EXT_memory_object_win32 and GL_EXT_semaphore_win32. win32u/opengl: Implement glImportSemaphoreWin32(Handle/Name)EXT for opaque handle types. win32u/opengl: Implement glImportMemoryWin32(Handle/Name)EXT for opaque handle types. opengl32, win32u: Move gl_error to wgl_context. win32u/opengl: Implement GL_DEVICE_LUID_EXT and GL_DEVICE_NODE_MASK_EXT. opengl32: Cleanup glGet* and fix typo in glGetDoublev. https://gitlab.winehq.org/wine/wine/-/merge_requests/9616

4 10

[PATCH v3 0/5] MR9651: dmsynth: More robust sink write and render scheduling
by Anton Baskanov (＠baskanov) Jan. 19, 2026

Jan. 19, 2026

-- v3: dmsynth: Clear the buffer notifications before closing the event handle. dmsynth: Estimate a continuously-advancing buffer position for a more precise timing. dmsynth: Call GetCurrentPosition from a separate thread. dmsynth: Simplify synth_sink_wait_play_end by making it similar to the main rendering loop. dmsynth: Try to maintain a fixed write latency by varying the wait time. https://gitlab.winehq.org/wine/wine/-/merge_requests/9651

3 8

[PATCH 0/1] MR9629: configure: Add option for building with split debug info.
by Yuxuan Shui (＠yshui) Jan. 15, 2026

Jan. 15, 2026

* * * all the machinery for split debug info is there, and the only thing needed is just exposing a flag from `configure`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9629

4 5

[PATCH v3 0/1] MR9764: msi/tests: Fix some typos (Coverity).
by Sven Baars (＠sbaars) Jan. 15, 2026

Jan. 15, 2026

-- v3: msi/tests: Fix some typos (Coverity). https://gitlab.winehq.org/wine/wine/-/merge_requests/9764

3 2

[PATCH v2 0/1] MR9742: mf: Prevent invalid topologies from being started.
by Bernhard Kölbl Jan. 14, 2026

Jan. 14, 2026

Signed-off-by: Bernhard Kölbl <bkoelbl(a)codeweavers.com> -- v2: mf: Prevent invalid topologies from being started. https://gitlab.winehq.org/wine/wine/-/merge_requests/9742

2 3

[PATCH v3 0/3] MR7429: winex11: Support absolute rawinput events and use window-relative coordinates.
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51357 Now that we're tracking window position changes as they arrive, they should always be consistent with the received mouse input events. Absolute rawinput is useful for tablets, touchpad or touchscreen when they are exposed as absolute mouse devices. -- v3: winex11: Use window-relative coordinates for mouse input. winex11: Add support for absolute position in RawMotion events. winex11: Clear the MOUSEEVENTF_MOVE flag when accumulating motion. https://gitlab.winehq.org/wine/wine/-/merge_requests/7429

3 6

[PATCH 0/1] MR8452: Draft: gitlab: Set WINEPREFIX to a job workspace sub-directory.
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Although I have trouble reproducing it I still experience weird test failures whenever I create or updated separate MRs in a short amount of time. These failures are usually coming from unexpected display settings, although each job is running within docker in an isolated environment. I don't have any explanation for this, and I have confirmed that separate X server are spawned. However, the prefix used for the tests is initialized to /home/gitlab/.wine and I suspect this could perhaps be mounted and shared across containers? It could also explain the failures, if, for instance wineserver starts while another instance (invisible as isolated in a separate container) is running and has updated the registry on disk with different display settings while the tests are being executed. This is hypothetical but nonetheless I think it's better to keep the prefix in a job workspace sub-directory. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8452

3 6

[PATCH v2 0/4] MR9510: Draft: win32u: Implement timeline semaphore rewinding.
by Rémi Bernon Jan. 14, 2026

Jan. 14, 2026

Pretty much the same kind of thing Proton does, this is only for non-shared semaphores for now. This creates timeline events backed by host timeline semaphores, for every wait and signal operation on a client timeline semaphore. Events are host timeline semaphores with monotonically increasing values. One event is a `(host semaphore, value)` unique tuple, and their value is incremented every time they get signaled. They can be reused right away as a different event, with the new value. Signaled events are queued to a per-device event list for reuse, as we cannot safely destroy them [^1] and as creating them might be costly. A thread is spawned for every device that uses timeline semaphores, monitoring the events and semaphore value changes. The semaphore wrapper keeps the current client semaphore value, which is read directly by `vkGetSemaphoreCounterValue`. CPU and GPU waits on the client semaphore are swapped with a wait on a timeline event, and GPU signals with a signal on a timeline event. CPU signals simply update the client semaphore value on the wrapper, signaling the timeline thread to check and notify any waiter. The timeline thread waits on signal events, coming from the GPU, and on a per-device semaphore for CPU notifications (wait/signal list updates, CPU-side signal). It will then signal any pending wait for a client semaphore value that has been reached, and removes timed out waits. --- For shared semaphores my idea is to use the client timeline semaphore host handle itself as a signal to notify other device threads of semaphore value changes, as the host semaphore is what is exported and imported in other devices. The timeline threads would wait on that semaphore too in addition to the signal events and thread notification semaphore. The main issue with shared semaphores actually comes from sharing the client semaphore values, so that they can be read from each device timeline threads as well as from other processes. There's two scenarios to support, one that is for in-process sharing which could perhaps keep the information locally, but we also need to support cross-process sharing so I think there's no other way than to involve wineserver. My idea then is to move shared semaphore client value to wineserver, which will cost a request on every signal and wait (and reading the value for waits could later be moved to a shared memory object). This will also allow us to implement `D3DKMTWaitForSynchronizationObjectFromCpu` which might be useful for D3D12 fence implementation as it'll allow us to translate a timeline semaphore wait to an asynchronous NT event signal. [^1]: Vulkan spec indicates that semaphores may only be destroyed *after* every operation that uses them has fully executed, and it's unclear whether signaling or waiting a semaphore is enough as an indicator for full execution or whether we would need to wait on a submit fence. -- v2: win32u: Implement timeline semaphore rewinding support. win32u: Make a copy of the timeline semaphore value arrays. win32u: Spawn a device thread for timeline semaphores. win32u: Hook more vulkan timeline semaphore functions. https://gitlab.winehq.org/wine/wine/-/merge_requests/9510

3 9