December 2025 - Wine-devel - list.winehq.org

Submitting patches to staging
by light gray 26 Feb '26

26 Feb '26

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.

5 6

Handling page faults in syscalls
by tblodt＠icloud.com 27 Dec '25

27 Dec '25

I just had a bit of a frustrating moment debugging why winecfg was crashing in my freshly built tree, and discovered something that many of you probably already know but is new to me: Wine swallows page faults that happen inside a syscall and just unwinds the stack to the caller returning an error, with only a trace level log. This seems surprising - normally page faults indicate a bug and need to be reported. And also scary - the code behind the syscall boundary can be anything, not necessarily part of the wine project, possibly even platform libc, and therefore not safe to unwind. My guess is these are caught instead of killing the process because that's the expected behavior of an NT syscall when you pass a bad pointer to it - that a bad dereference of a userspace pointer would be handled and turned into returning an fault error code. Is this right? But then what would actually make sense is to write separate functions for safely dereferencing user pointers, like Linux has. What should ideally be happening here? ~Theodore

2 3

Wine staging 11.0-rc4 release
by Alistair Leslie-Hughes 27 Dec '25

27 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-rc4 (252 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: * None 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

Question about AI-generated code policy
by mcm＠etersoft.ru 25 Dec '25

25 Dec '25

Hello everyone, I would like to raise a question about Wine's policy on code generated by Large Language Models (LLMs). Several large open-source projects, including NetBSD, QEMU, and Gentoo, have already stated their strict position about contributing such code [1] [2] [3], but I found no results related to this topic in either the Wine Developer's Guide [4] or wine-devel archives [5]. Would it make sense to formalize a clear code policy regarding code generated by LLM and add it to the Developer's Guide? This would be relevant for both the main Wine tree and the tests subsystem. Best regards, Y. Osipov [1]: https://www.netbsd.org/developers/commit-guidelines.html#tainted [2]: https://www.qemu.org/docs/master/devel/code-provenance.html#use-of-ai-gener… [3]: https://wiki.gentoo.org/wiki/Project:Council/AI_policy [4]: https://gitlab.winehq.org/wine/wine/-/wikis/Wine-Developer%27s-Guide [5]: https://list.winehq.org/archives/search?mlist=wine-devel%2540list.winehq.org

1 1

Wine staging 11.0-rc3 release
by Alistair Leslie-Hughes 21 Dec '25

21 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-rc3 (252 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: * None 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 11.0-rc2 release
by Alistair Leslie-Hughes 13 Dec '25

13 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-rc2 (252 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

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

10 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 4

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

06 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