November 2025 - Wine-GitLab

[PATCH v6 0/2] MR9287: uxtheme: Handle NULL options in DrawThemeTextEx().
by Mohamad Al-Jaf (＠maljaf) Nov. 11, 2025

Nov. 11, 2025

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54927 -- v6: uxtheme/tests: Add some DrawThemeTextEx() tests. uxtheme: Handle NULL options in DrawThemeTextEx(). https://gitlab.winehq.org/wine/wine/-/merge_requests/9287

3 3

[PATCH 0/6] MR9422: comctl32/rebar: Add a helper to draw the gripper.
by Zhiyi Zhang (＠zhiyi) Nov. 11, 2025

Nov. 11, 2025

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

3 7

[PATCH 0/1] MR9417: uxtheme/tests: Verify GetCurrentThemeName() returns Aero\Aero.msstyles on Windows
by nikita pushkarev (＠strudelll) Nov. 11, 2025

Nov. 11, 2025

## WINELINKING environment variable `WINELINKING` is an optional environment variable that controls how Wine installs its built-in (“fake”) DLLs into a Wine prefix.\ Instead of always copying the PE template into the prefix, Wine can: * create a symbolic link to the original PE file, * create a hard link to the original PE file, or * attempt a filesystem-level copy-on-write (reflink) clone. This can significantly reduce disk usage and speed up prefix creation on filesystems that support these features. `WINELINKING` is only consulted when installing built-in DLLs (the fake DLLs generated by `setupapi`). It does **not** affect how applications copy or install their own files inside the prefix. ### Supported values `WINELINKING` recognizes the following values: * `WINELINKING=sym`\ Wine attempts to create a **symbolic link** in the prefix that points to the original built-in PE file in the Wine installation. * `WINELINKING=hard`\ Wine attempts to create a **hard link** to the original built-in PE file, so both paths refer to the same underlying file on disk. * `WINELINKING=cow`\ Wine attempts a **copy-on-write (CoW) / reflink clone** of the original PE file. On filesystems that support extent cloning, this creates a logical copy that shares physical blocks until one of the copies is modified. If `WINELINKING` is not set, or set to any other value, Wine falls back to the traditional behavior: the built-in DLL is copied into the prefix with a normal write. Signed-off-by: Nikita strudelll(a)etersoft.ru -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9417

3 3

Re: [PATCH v2 0/1] MR9414: Draft: shlwapi: Handling of "C:\...xx" in PathCanonicalize[AW].
by Thomas Csovcsity (＠thc13) Nov. 11, 2025

Nov. 11, 2025

## Test results from test bot: - patch and test execution - https://testbot.winehq.org/JobDetails.pl?Key=160728 - 0128:path: 66853 tests executed (9 marked as todo, 0 as flaky, **0 failures**), 0 skipped. - test execution without patch - https://testbot.winehq.org/JobDetails.pl?Key=160713 - 0124:path: 66853 tests executed (9 marked as todo, 0 as flaky, **4 failures**), 0 skipped. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9414#note_121509

1 0

[PATCH 0/1] MR9414: Draft: shlwapi: Handling of "C:\...xx" in PathCanonicalize[AW].
by Thomas Csovcsity (＠thc13) Nov. 11, 2025

Nov. 11, 2025

## Description This is intended to solve https://bugs.winehq.org/show_bug.cgi?id=58129 Add tests for verification, which pass on my locale win10 machine. ##Todo - [] Removed UNC path check which seems okay, but i am not sure why it was introduced. git blame did not help me, therefore any hints or examples to test are welcome. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9414

3 3

[PATCH v3 0/1] MR9423: ntdll: Warn when environment block is too large, instead of removing it
by Martino Fontana (＠tinozzo123) Nov. 11, 2025

Nov. 11, 2025

This partially reverts commit d4920360bffddaa5923a8da0b15f3ad9a2a97e78. Windows does support environment blocks of unlimited sizes, which makes the reverted commit a workaround for (at least) one defective application. And it's a very invasive workaround: there are multiple applications that run on Wine, but expect the user to supply environment variables from the Unix side (e.g. DXVK). The change breaks these configurations on users who may not even use the defective application(s). So, instead of breaking configurations, just warn the user that there may be issues due to the large environment block. -- v3: ntdll: Warn when environment block is too large, instead of removing it https://gitlab.winehq.org/wine/wine/-/merge_requests/9423

2 1

[PATCH 0/1] MR9424: shell32: Support SHARD_PATHW in SHAddToRecentDocs().
by Hans Leidekker (＠hans) Nov. 11, 2025

Nov. 11, 2025

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54626 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9424

2 1

[PATCH v2 0/1] MR9423: ntdll: Warn when environment block is too large, instead of removing it
by Martino Fontana (＠tinozzo123) Nov. 11, 2025

Nov. 11, 2025

This partially reverts commit d4920360bffddaa5923a8da0b15f3ad9a2a97e78. Windows does support environment blocks of unlimited sizes, which makes the reverted commit a workaround for (at least) one defective application. And it's a very invasive workaround: there are multiple applications that run on Wine, but expect the user to supply environment variables from the Unix side (e.g. DXVK). The change breaks these configurations on users who may not even use the defective application(s). So, instead of breaking configurations, just warn the user that there may be issues due to the large environment block. -- v2: ntdll: Warn when environment block is too large, instead of removing it https://gitlab.winehq.org/wine/wine/-/merge_requests/9423

2 1

[PATCH 0/1] MR9423: ntdll: Warn when environment block is too large, instead of removing it
by Martino Fontana (＠tinozzo123) Nov. 11, 2025

Nov. 11, 2025

This partially reverts commit d4920360bffddaa5923a8da0b15f3ad9a2a97e78. Windows does support environment blocks of unlimited sizes, which makes the reverted commit a workaround for (at least) one defective application. And it's a very invasive workaround: there are multiple applications that run on Wine, but expect the user to supply environment variables from the Unix side (e.g. DXVK). The change breaks these configurations on users who may not even use the defective application(s). So, instead of breaking configurations, just warn the user that there may be issues due to the large environment block. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9423

2 1

[PATCH v12 0/5] MR9112: XCOPY and COPY should not attempt to copy a file to itself.
by Joe Souza (＠JoeS209) Nov. 11, 2025

Nov. 11, 2025

Current code attempts to copy a file to itself. File is not actually copied; instead, a file sharing error is received. This result is ugly and differs from native. Behavior now appears to be the same as native with changes in this MR . -- v12: xcopy: Don't attempt to copy a file to itself. xcopy/tests: Add test for XCOPY to self. xcopy: Fix leaked resource in an error case. https://gitlab.winehq.org/wine/wine/-/merge_requests/9112

4 7