- Wine-devel - list.winehq.org

Wine staging 11.0-rc1 release
by Alistair Leslie-Hughes 05 Dec '25

05 Dec '25

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.0-rc1 (253 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 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

Welcome to code freeze!
by Alexandre Julliard 05 Dec '25

05 Dec '25

Folks, With the release of 11.0-rc1, we are now officially in the code freeze period. Many thanks to everybody for another year of great work! During code freeze, only small, targeted bug fixes will be accepted. When sending fixes, please make sure to mention the bug or the app that is fixed by the change. We are starting code freeze with 200 pending regressions, which is significantly lower than in previous years, where the number was more around 230. It remains to be seen how many regression bugs will be filed against rc1, but I'm hopeful that we can release 11.0 with fewer pending regressions that the previous stable releases. As usual, there will now be weekly -rc releases until the final 11.0, which is expected some time around mid-January. Thank you all for your work! -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Core Infrastructure Maintenance 2025-12-10 18:00 UTC
by David Kahurani 02 Dec '25

02 Dec '25

MITm On Wed, Dec 3, 2025 at 1:19 AM DigitalOcean Support <support(a)digitalocean.com> wrote: > > Start: 2025-12-10 18:00 UTC > End: 2025-12-10 20:00 UTC > > Hello, > > During the above window, our Engineering team will be performing maintenance on principal infrastructure in order to improve reliability of the services. Please note that existing infrastructure will continue running without issue. This maintenance impacts create, read, update, and delete (CRUD) operations in all regions. > > Expected Impact: > > During the maintenance window, users may experience increased latency for the following platform operations: > > Cloud Control Panel and API operations > Event processing > Droplet creates, resizes, rebuilds, and power events > Managed Kubernetes reconciliation and scaling > Load Balancer operations > Container Registry operations > App Platform operations > Managed Database creation and scaling > > We expect to see two periods of 10 second impact, for a total of 20 seconds within the hour window. If unexpected impact occurs or continues for longer than expected, we will provide updates via our public status page. > > If you have any questions related to this issue please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket > > Thank you, > Team DigitalOcean

1 0

Introducing the list.winehq.org domain
by Alexandre Julliard 02 Dec '25

02 Dec '25

Folks, Just a heads up that we are starting the process of moving the various Wine mailing lists to a new 'list.winehq.org' domain. So for instance the wine-devel list is going to be at <wine-devel(a)list.winehq.org>. This is necessary to make it possible to host the lists on a different server in the future. Sending mail to the existing @winehq.org addresses will still work, so the change should be mostly transparent, but you may see the list.winehq.org domain start creeping up in the mail headers, and may need to adjust your filters. Note that the recommended way is to filter on the List-Id: header; that one is not expected to change. Thank you for your understanding, -- Alexandre Julliard julliard(a)winehq.org

3 3

Wine staging 10.20 release
by Alistair Leslie-Hughes 29 Nov '25

29 Nov '25

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.20 (252 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * kernelbase: Add support for moving reparse points with MoveFile*. * x3daudio1_7: Create import library * xactengine3_7/tests: Add Global settings test * kernel32: Implement CreateSymbolicLink[A|W] with ntdll reparse points. * kernel32: Add reparse support to FindNextFile. * user32: Add a workaround for Windows 3.1 apps which call LoadImage(LR_LOADFROMFILE) with a resource id. (v2) Removed (No longer required). * None Added: * None Updated: * vkd3d-latest 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

Wine staging 10.19 release
by Alistair Leslie-Hughes 15 Nov '25

15 Nov '25

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.19 (256 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Add support for creating reparse points. * ntdll: Add support for reading reparse points. * ntdll: Add support for deleting reparse points. * Return correct status value if handle is not a reparse point * ntdll: Always report symbolic links as containing zero bytes. * ntdll: Succeed with no data for NtReadFile on reparse points. * ntdll: Add support for testing for reparse points with GetFileAttributes. * server: Implement FILE_OPEN_REPARSE_POINT option. * ntdll: Add support for FileAttributeTagInformation. * kernelbase: Add support for deleting reparse points with RemoveDirectory. * kernelbase: Add support for deleting reparse points with DeleteFile. * ntdll: Follow reparse points during path resolution. * d3dx11: Implement D3DX11CreateTextureFromMemory() using shared code. Removed (No longer required). * ntdll: Allow reparse points to target the applicable Unix file/directory. * ntdll: Add an intermediary prefix symlink in reparse point metadata. Added: * None Updated: * vkd3d-latest 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

Extended test suite
by Giovanni Mascellani 13 Nov '25

13 Nov '25

Hi, some time ago I was asked by a reviewer to modify a MR I had submitted to remove some of the conformance tests I had added with it. The concern, which I find completely valid, was that since the tests are run on each MR submission we should try to reduce (or, at least, do not increase too much) the run time, otherwise it becomes too much inconvenient for everybody. As I said, that totally makes sense for me, and in that particular occasion I ended up removing some cases, hopefully keeping enough to cover all the common test cases. But corner cases exist too, and they can make a developer waste a lot of time chasing them down. And at least in my experience it's often hard to predict which specific cases are going to be somehow critical in the future. So giving up some tests bears most of the times if not always the risk of having to waste time on something that would have been simpler if only we had kept that specific test case. So I'm curious to know whether anybody else experiences this problem, and possibly brainstorm some ideas about how to work it around. What I'd like to propose is to introduce an extended test suite, which in practice means adding a flag to our current test suite and gating some tests to be executed (at all, or to be executed on a larger number of cases) only if the flag is set. The regular test suite could be run on all MRs, and the extended test suite could be run perhaps once per day or so. The feedback is less immediate, but it still looks better than dropping those tests at all. The terms "pre-merge test" and "post-merge tests" are sometimes used, I think they essentially mean the same thing. Is there any interest for this? Or alternative solutions? Gio.

2 1

64-Bit twain data source manager should be named twaindsm.dll instead of twain_32.dll
by Bernd Herd 10 Nov '25

10 Nov '25

Hello, for 64-Bit, the code in dlls/twain_32 should be compiled into a library installed as twaindsm.dll instead of twain_32.dll, since Windows applications do expect a 64-Bit Data Source Manager to be named twaindsm.dll. How could that be done? Background: wine includes an interface from the TWAIN interface common in Windows to the SANE interface common on Linux. This is dlls/sane.ds, which is in TWAIN speak a "Data Source". This allows to use most scanners supported by SANE from WINE, without caring about any special drivers. Which is a pretty cool thing. 64 Bit TWAIN is somewhat exotic, since Microsoft is pushing towards their WIA interface and does not include a 64-Bit Data Source Manager with Windows. The 32-Bit Data Source Manager shipped with Windows is TWAIN_32.DLL. This DLL is under control of Microsoft and the TWAIN organization cannot update it, so they choose to name their update DSM "twaindsm.dll". I found some more information on that here: https://github.com/twain/twain-dsm/blob/master/TWAIN_DSM/src/readme.doc](ht… This twaindsm.dll is available in 32-Bit and 64-Bit. And so the only 64-Bit DSM that application programs expect is twaindsm.dll. There are hardly any 64-Bit TWAIN drivers available on Windows. Irfanview 64-Bit uses twaindsm.dll if installed and spawns a 32-Bit EXE if not. Older versions of 64-Bit Libreoffice for Windows used twaindsm.dll. New Versions start a 32-Bit process to use 32-Bit TWAIN. The code in the dlls/sane.ds searches for "twain_32", and I know two ways to solve this. What I don't know is how to change wine so that it compiles dlls/twain_32 to twaindsm.dll for 64-Bit Builds only and deploy that dll to the wine prefix. Any suggestion of how to do that? Yours Bernd Herd :-)

3 2

RoResolveNamespace and winmd
by James McDonnell 06 Nov '25

06 Nov '25

Hello, I see the winmd File generation work has landed in wine. In order for affinity to run, it needs to map winrt namespaces to winmd files. These are defined in the idl files afaict. I am looking for guidance of looking up this information in RoResolveNamespace. I see in the widl tool we generate the files. I did not find any parser for winmd files. Is there somewhere I should look? Or is this new ground. Would it be acceptable to have an override in the registry that RoResolveNamespace uses such that wine prefixes can customize if needed? Thank you, James

1 0

Submitting patches to staging
by light gray 06 Nov '25

06 Nov '25

Hi! On the condition that I de-anonymize myself, would it be possible for me to submit my patches over at https://github.com/Weather-OS/WineGDK to wine staging? My repository fully complies with Wine's cleanroom guidelines, and more importantly, I *do not, and under no circumstances,* use AI generated code to implement API functionality. I solely rely on tests written and compiled within a Windows environment and Microsoft's own documentation. Best Regards.

4 5