- Wine-GitLab - list.winehq.org

[PATCH v3 0/1] MR10953: Update default i386 CFLAGS
by Matteo Bruni (＠Mystral) June 4, 2026

June 4, 2026

The immediate reason for this is !10716, but I suspect it might come in handy in other places as well. FWIW I've been building Wine with similar CFLAGS for many, many years. -- v3: configure: Add x86-64 CPU features to default i386_EXTRACFLAGS. https://gitlab.winehq.org/wine/wine/-/merge_requests/10953

2 2

[PATCH v24 0/7] MR10659: combase: Implement restricted WinRT error handling APIs.
by Anna R Békefi (＠annareginabekefi) June 4, 2026

June 4, 2026

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=58900 Bug 58900 This series implements restricted WinRT error handling in combase and\ adds conformance tests for the new behavior. Implemented APIs include restricted error creation / retrieval,\ error context capture, transform, matching, and unhandled error reporting\ paths. Tests were added under dlls/combase/tests and pass locally.\ The existing combase tests also continue to pass. -- v24: combase: Implement SetRestrictedErrorInfo. combase: Add semi-stub for RoOriginateLanguageException. combase: Implement RoOriginateError(W) and GetRestrictedErrorInfo. combase: Implement Ro{Get,Set}ErrorReportingFlags. combase/tests: Add tests for GetRestrictedErrorInfo. combase/tests: Add tests for RoOriginateError(W) and RoOriginateLanguageException. combase/tests: Add tests for Ro{Get,Set}ErrorReportingFlags. https://gitlab.winehq.org/wine/wine/-/merge_requests/10659

3 7

[PATCH v3 0/4] MR10535: mfreadwrite: Rescale video frames based on aspect ratio when processing is enabled.
by Yuxuan Shui (＠yshui) June 4, 2026

June 4, 2026

-- v3: mfreadwrite: Ensure output has a 1:1 pixel aspect ratio if processing is enabled. mfreadwrite/tests: Test how aspect ratios are handled by the reader. mfreadwrite: Don't modify the `type` parameter in src_reader_SetCurrentMediaType. mfplat/tests: Test how the MPEG4 media source handles aspect ratio info. https://gitlab.winehq.org/wine/wine/-/merge_requests/10535

3 7

[PATCH v9 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Rose Hellsing (＠axtlos) June 3, 2026

June 3, 2026

Until now wine tried to write the cookie even if the cookie was located in a read-only section, causing some applications to crash. With this change the loader temporarily marks the memory section as read-write to update the cookie. The same fix was applied to the ntdll and ntoskrnl.exe loader, as they had pretty much the same set_security_cookie() function. A test to check for correctness with read-only cookies was also added. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51928 -- v9: kernel32: Add test for read-only cookie in loader ntoskrnl.exe: account for read-only cookies https://gitlab.winehq.org/wine/wine/-/merge_requests/11001

2 4

[PATCH v8 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Rose Hellsing (＠axtlos) June 3, 2026

June 3, 2026

Until now wine tried to write the cookie even if the cookie was located in a read-only section, causing some applications to crash. With this change the loader temporarily marks the memory section as read-write to update the cookie. The same fix was applied to the ntdll and ntoskrnl.exe loader, as they had pretty much the same set_security_cookie() function. A test to check for correctness with read-only cookies was also added. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51928 -- v8: kernel32: Add test for read-only cookie in loader https://gitlab.winehq.org/wine/wine/-/merge_requests/11001

3 5

[PATCH v7 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Rose Hellsing (＠axtlos) June 3, 2026

June 3, 2026

Until now wine tried to write the cookie even if the cookie was located in a read-only section, causing some applications to crash. With this change the loader temporarily marks the memory section as read-write to update the cookie. The same fix was applied to the ntdll and ntoskrnl.exe loader, as they had pretty much the same set_security_cookie() function. A test to check for correctness with read-only cookies was also added. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51928 -- v7: kernel32: Add test for read-only cookie in loader https://gitlab.winehq.org/wine/wine/-/merge_requests/11001

2 3

[PATCH v6 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Rose Hellsing (＠axtlos) June 3, 2026

June 3, 2026

Until now wine tried to write the cookie even if the cookie was located in a read-only section, causing some applications to crash. With this change the loader temporarily marks the memory section as read-write to update the cookie. The same fix was applied to the ntdll and ntoskrnl.exe loader, as they had pretty much the same set_security_cookie() function. A test to check for correctness with read-only cookies was also added. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51928 -- v6: kernel32: Add test for read-only cookie in loader https://gitlab.winehq.org/wine/wine/-/merge_requests/11001

2 3

[PATCH v5 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Rose Hellsing (＠axtlos) June 3, 2026

June 3, 2026

Until now wine tried to write the cookie even if the cookie was located in a read-only section, causing some applications to crash. With this change the loader temporarily marks the memory section as read-write to update the cookie. The same fix was applied to the ntdll and ntoskrnl.exe loader, as they had pretty much the same set_security_cookie() function. A test to check for correctness with read-only cookies was also added. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51928 -- v5: kernel32: Add test for read-only cookie in loader https://gitlab.winehq.org/wine/wine/-/merge_requests/11001

2 4

[PATCH v4 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Rose Hellsing (＠axtlos) June 3, 2026

June 3, 2026

Until now wine tried to write the cookie even if the cookie was located in a read-only section, causing some applications to crash. With this change the loader temporarily marks the memory section as read-write to update the cookie. The same fix was applied to the ntdll and ntoskrnl.exe loader, as they had pretty much the same set_security_cookie() function. A test to check for correctness with read-only cookies was also added. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51928 -- v4: kernel32: Add test for read-only cookie in loader ntoskernel.exe: account for read-only cookies ntdll: account for read-only cookie in loader https://gitlab.winehq.org/wine/wine/-/merge_requests/11001

3 8

Re: [PATCH v2 0/1] MR11061: hnetcfg: Report 0 returned elements from IEnumVARIANT::Next. - approved
by Alexandre Julliard (＠julliard) June 3, 2026

June 3, 2026

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

1 0