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

[PATCH 0/5] MR11065: taskschd: Implement several methods in IActionCollection, ITriggerCollection and IPrincipal
by Oleg Nikulin (＠owl2) June 4, 2026

June 4, 2026

I have an app that crashes in Wine because it requires some task scheduler features that are not implemented yet -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11065

2 5

Re: [PATCH v3 0/2] MR10804: unicode: optimize memicmp_strW by doing case-sensitive comparision first
by Alfred Agrell (＠Alcaro) June 4, 2026

June 4, 2026

On Thu Jun 4 11:18:52 2026 +0000, Stephan Seitz wrote: > @Alcaro I would like to dig a bit deeper into this. How do you think we > should progress with this MR? > - have standalone MRs for the memicmp_strW optimization and the > optimization of loading of sorted data. Should I collect more data for > the both optimizations for both realistic registry sizes and huge ones? > - try to profile a bit more to improve registry loading as a whole IMO the most important question here is what made your registry so chonky. "Wineserver startup takes 20 seconds after installing Contoso System Discombobulator 2028" is more a convincing usecase than "Wineserver startup takes 20 seconds if your registry is half a gigabyte". I'd also check server startup times for unpatched, case patch only, sort patch only, and both. If the latter two are almost the same, the case patch is probably not worth keeping; if noticably different, we now know it is worth keeping. But I'm not the wineserver maintainer, so my opinion isn't the important one. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10804#note_142183

1 0

Re: [PATCH v3 0/2] MR10804: unicode: optimize memicmp_strW by doing case-sensitive comparision first
by Stephan Seitz (＠theHamsta) June 4, 2026

June 4, 2026

@Alcaro I would like to dig a bit deeper into this. How do you think we should progress with this MR? - have standalone MRs for the memicmp_strW optimization and the optimization of loading of sorted data. Should I collect more data for the both optimizations for both realistic registry sizes and huge ones? - try to profile a bit more to improve registry loading as a whole -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10804#note_142180

1 0

[PATCH v7 0/5] MR10963: winex11: Keyboard layouts rework, part 3
by Matteo Bruni (＠Mystral) June 4, 2026

June 4, 2026

-- v7: user32/tests: Add more key map tests. user32/tests: Add more key names tests. user32/tests: Add a SendInput VK_PAUSE test. winex11: Support fixed X11 keycode to scancode conversion. winex11: Use scancode high bit to set KEYEVENTF_EXTENDEDKEY flag. https://gitlab.winehq.org/wine/wine/-/merge_requests/10963

4 8

[PATCH v4 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. -- v4: configure: Add -msse2 to default i386_EXTRACFLAGS. https://gitlab.winehq.org/wine/wine/-/merge_requests/10953

2 1

[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

Re: [PATCH v3 0/3] MR11054: ole32: Implement IStorage::MoveElementTo(). - 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/11054

1 0

Re: [PATCH v2 0/1] MR11059: dssenh: Use SymCrypt. - 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/11059

1 0

Re: [PATCH v2 0/1] MR11057: winexinput.sys: Fix handling of non-32-bit axis - 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/11057

1 0

Re: [PATCH v5 0/1] MR11055: loader: Add default SQMClient registry key - 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/11055

1 0

[PATCH v2 0/1] MR10953: Draft: Update default i386_CFLAGS
by Matteo Bruni (＠Mystral) June 3, 2026

June 3, 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. -- v2: configure: Add x86-64 CPU features to default i386_EXTRACFLAGS. https://gitlab.winehq.org/wine/wine/-/merge_requests/10953

3 2

[PATCH v3 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 -- v3: 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

2 3

Re: [PATCH v2 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Alexandre Julliard (＠julliard) June 3, 2026

June 3, 2026

On Wed Jun 3 18:43:03 2026 +0000, Rose Hellsing wrote: > Is the loop actually necessary? From how I understand it it keeps > re-rolling the cookie until it's no longer the same as the default > sentinel, but the chance for that to happen should be pretty low. Sure, but low is not zero. Some apps crash when the cookie is not set. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11001#note_142125

1 0

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

June 3, 2026

On Wed Jun 3 18:42:40 2026 +0000, Alexandre Julliard wrote: > I don't think you should be removing the loop. Is the loop actually necessary? From how I understand it it keeps re-rolling the cookie until it's no longer the same as the default sentinel, but the chance for that to happen should be pretty low. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11001#note_142124

1 0

[PATCH 0/1] MR11061: hnetcfg: Report 0 returned elements from IEnumVARIANT::Next.
by Tim Clem (＠tclem) June 3, 2026

June 3, 2026

A regression from !10957. MSDN documents that the final argument should be set to the number of returned elements, even if the function returns S_FALSE. steamservice.exe crashes on launch without this; it passes an uninitialized variable as pCeltFetched, so it proceeds to loop over some arbitrary number of (nonexistent) variants. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11061

3 2

Re: [PATCH v2 0/3] MR11001: ntdll, ntoskrnl.exe: account for read-only cookie in loader
by Alexandre Julliard (＠julliard) June 3, 2026

June 3, 2026

I don't think you should be removing the loop. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11001#note_142122

1 0