June 2026 - Wine-Devel - list.winehq.org

wine staging 11.12 release
by Alistair Leslie-Hughes June 29, 2026

June 29, 2026

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.12 (289 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * tiptsf: Add dll * tiptsf: Add ITextInputPanel interface stub * rtscom: New dll * rtscom: Add RealTimeStylus stubbed interface. Removed (No longer required). * winex11-ime-check-thread-data Added: * [55138] ntdll: Add read and write to new guard pages. Updated: * vkd3d-latest * comctl32_animate_avi (warning fixes) * windowscodecs-TIFF_Support (warning fixes) * mmsystem.dll16-MIDIHDR_Refcount (warning fixes) Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Clean-Room guidelines + some general questions
by Hudson Finn June 26, 2026

June 26, 2026

Hi guys, I just started looking around the codebase, and reading the wiki. This is my first time working with "Windows", as I've been daily-driving Linux for a long time. I have a few questions: - Do you guys have general recommendations for looking at Windows documentation/finding information about various Windows components and such? What's the deal with MSDN beyond it being sometimes wrong? Are there other things here to know about? - When debugging a problem with the Wayland driver, will running wine normally work? I use XWayland for a few apps that I use. Are there flags I should pass to ensure that I'm on native Wayland? Thanks guys! I'm looking forward to being able to contribute in the future!

1 0

Project creation permission request
by павел June 22, 2026

June 22, 2026

Hello,I recently created an account on gitlab.winehq.org (my username is PavelCheloveckov)and would like to contribute a patch. However, I cannot fork thewine repository due to the project creation limit on new accounts.Could you please grant my account permission to create projects so I cansubmit a merge request?Thank you,Pavel

1 0

[RFC] server: report a stream socket writable while its send buffer has room
by wine-devel＠forryan.co.uk June 20, 2026

June 20, 2026

Hi all, Before I open a merge request, I’d like feedback on the approach, as it has a portability angle I’m unsure about. Question up front: the fix relies on TIOCOUTQ to query the amount of unsent data in a socket’s send buffer. That is Linux-specific. Is gating it on #ifdef TIOCOUTQ (leaving current behaviour unchanged elsewhere) acceptable, or would you prefer a different mechanism, or a different layer than poll_socket()? I’d rather hear that now than in review. On Windows, select() reports a connected stream socket writable whenever a send() would still accept data into the send buffer. Wine derives writability from the host poll(); on Linux POLLOUT is only set once the send queue has drained below roughly 2/3 of SO_SNDBUF. So while the buffer is between ~2/3 full and full, Windows says “writable” but Wine says “not writable” even though send() still succeeds. The common application pattern is a non-blocking select() writability check before waiting on an FD_WRITE event. libcurl’s multi loop does exactly this. Under Wine, an app-limited sender (sends keep succeeding, never hitting WSAEWOULDBLOCK) sees “not writable” while it still has room, and since FD_WRITE is edge-triggered and not re-recorded until a send fails, it waits out its full poll timeout (typically 1s) between bursts. Single-stream uploads end up throttled to ~140 KB/s. I found this with a libcurl-based backup client whose uploads could not finish within their timeout under Wine. Proposed fix: In poll_socket(), when the immediate poll() does not report POLLOUT for a connected stream socket that still has send-buffer room (TIOCOUTQ < SO_SNDBUF), report it writable. One small block, #ifdef TIOCOUTQ. Conformance: I have a ws2_32:sock test (the invariant: select() reports writable exactly while send() accepts data). On the same test binary: * real Windows pass (0 violations) * Wine, unpatched fail (~230 of ~660 sends report not-writable yet send ok) * Wine, patched pass (0 violations) I’ll submit the test as a todo_wine commit ahead of the fix. One thing I tried and dropped: I first also changed FD_WRITE to re-arm on every send. A conformance test on real Windows showed Windows does NOT re-arm FD_WRITE after a successful send (only after WSAEWOULDBLOCK, matching MSDN), so that change would have diverged from Windows. The writability fix alone is sufficient and is the Windows-conforming part. For background, curl’s issue #6146 (https://github.com/curl/curl/issues/6146) documents this same select/FD_WRITE behaviour on Windows; curl’s workaround is the select()-before-wait pre-check in commit a69d1a4 (PR #5634, “multi: implement wait using winsock events”). That pre-check is exactly the path this fix unblocks under Wine. Bug: https://bugs.winehq.org/show_bug.cgi?id=59893 Happy to adjust the mechanism based on what you’d prefer here. Thanks, Martyn Forryan

2 2

Wine staging 11.11 release
by Alistair Leslie-Hughes June 13, 2026

June 13, 2026

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.11 (289 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * None Updated: * vkd3d-latest * dcomp-DCompositionCreateDevice2 Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Multiple test failures in Gitlab's CI
by Barath Rk June 9, 2026

June 9, 2026

I recently created this MR in Gitlab: https://gitlab.winehq.org/wine/wine/-/merge_requests/11079 which had 52 test failures in the CI. However, some other merged requests appear to similarly have many failures. My question is, should I attribute these test failures to a flaky CI and just wait for review, or try to resolve it on my end? Thanks in advance.

2 3

Spout2PW, Wine 11, and on GPU Shared Handles
by madalee＠ohlmeyers.com June 3, 2026

June 3, 2026

Hello All, I'm trying to adapt Lina's Spout2Pw to the new restrictions in Wine 11 and constantly failing. Am I right in understanding that there is no current method to pass a handle to GPU shared memory between the Wine/Linux barrier? I've proven out that I can do this with CPU accessible RAM, but every method I've tried with VRAM fails. I saw mention of KMT being supported in DXVK and maybe in Wine 11. I've tried using it, but, at least as of Proton 11, I think KMT doesn't work for sharing memory handles yet. Is there any method of doing this that anyone can suggest, for Wine 11, or any versions of Wine 11 that this should work with? Thanks, -Madalee

1 0