November 2025 - Wine-gitlab

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

11 Nov '25

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) 11 Nov '25

11 Nov '25

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) 11 Nov '25

11 Nov '25

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

[PATCH 0/1] MR9421: comdlg32/tests: Force console subsystem version 5.2.
by Hans Leidekker (＠hans) 11 Nov '25

11 Nov '25

Fixes a regression from 6a11792e257914e83d1f3a34391aeff7a29ad25a. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9421

2 1

[PATCH 0/1] MR9337: combase: Add stub for CoGetSystemSecurityPermissions.
by Louis Lenders (＠xe) 11 Nov '25

11 Nov '25

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

3 4

[PATCH 0/1] MR9419: kernel32: handle root path in wine_get_dos_file_name
by Jiajin Cui (＠jin-king1) 11 Nov '25

11 Nov '25

Fixed path concatenation issue in wine_get_dos_file_name function when dealing with root paths. The function now checks if the buffer contains a root path using PathIsRootW and adjusts the concatenation offset accordingly. When the path is a root path, it skips the trailing backslash in the NT name to avoid double backslashes in the final path. Signed-off-by: Jiajin Cui <cuijiajin(a)uniontech.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9419

2 1

[PATCH v2 0/3] MR9357: winegstreamer: Add ARGB32 format support and use bottom-up for AVI videos.
by Akihiro Sagawa (＠sgwaki) 10 Nov '25

10 Nov '25

A certain game application requires both. -- v2: winegstreamer: Always use bottom-up for AVI RGB videos. winegstreamer: Add ARGB32 format support for 32 bpp AVI videos. quartz/tests: Add tests for 32 bpp AVI videos. https://gitlab.winehq.org/wine/wine/-/merge_requests/9357

3 4

[PATCH v7 0/5] MR9293: Reparse points, part 1.
by Elizabeth Figura (＠zfigura) 10 Nov '25

10 Nov '25

As prescribed some time ago, this attempts to implement correct reparse behaviour simply without attempting at all to make reparse points resolvable Unix symlinks. A reparse point consists two files. For a file whose NT name is "foobar", the contents of the file or directory (and note that a reparse point *can* have arbitrary contents) is stored in a file or directory "foobar?". The contents of the reparse point are stored in a file "foobar*". Both * and ? are valid in POSIX filenames but not NT, so no collision should be possible. The actual file "foobar" does not exist in this case. This is to allow the case where there are no reparse points (which is most common) to work as it currently does, without any extra overhead to check for a reparse point. [Simply guarding this behind FILE_OPEN_REPARSE_POINT does not seem good enough to me; that flag is used for example by many builtin functions like MoveFile().] When failing to locate a path segment "foobar", we check for "foobar*" and attempt to parse and resolve that reparse point. Issues: (1) Since we are manipulating two files, are there any race conditions? I believe there are no meaningful races. Read/write races: - When setting a reparse point, we move the contents file out of the way last, so attempts to open the file before that will see a normal file. Attempts to read the reparse point might see a partial file, but we treat that as failure. - When removing a reparse point from a file, we move the contents file back first, so attempts to open or read will see a normal file. - When deleting a reparse point entirely, we delete the contents first, so attempts to open the file will see neither a normal file nor the contents of the symlink, and fail. Attempts to query attributes don't need to open the contents, only the data, which will either be present or not. Write/write races: - Races involving file deletion don't matter, because deletion doesn't take effect until all handles to an inode are closed. - If we try to simultaneously set the reparse point from two different threads, one will fail with no effect since we create the reparse data file with O_EXCL. - If we try to remove the reparse point while setting it, the contents won't be in the right place and we'll fail. - If we try to remove the reparse point from two different threads, one will fail to move the contents back or delete them. (2) How does this interact with hard links? Creating a hard link to an existing reparse point is not too hard to do; we can just hard link both the data file and the contents file. However, turning an existing hardlinked file into a reparse point cannot work. This is also a limitation of other approaches that have been proposed. For this reason I've elected to forbid hard link interaction for now. One alternative approach that would allow turning hardlinked files into reparse points would be to store the reparse data in xattr. This would be less portable though. -- v7: ntdll: Resolve IO_REPARSE_TAG_MOUNT_POINT during path lookup. ntdll: Pass attr and nt_name down to lookup_unix_name(). server: Implement FSCTL_GET_REPARSE_POINT. https://gitlab.winehq.org/wine/wine/-/merge_requests/9293

2 6

Re: [PATCH v5 0/5] MR9355: windows.perception.stub: Implement IHolographicSpace_get_PrimaryAdapterId(). - approved
by Alexandre Julliard (＠julliard) 10 Nov '25

10 Nov '25

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

1 0

Re: [PATCH v4 0/6] MR9403: vccorlib140: Implement stringification functions. - approved
by Alexandre Julliard (＠julliard) 10 Nov '25

10 Nov '25

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

1 0