- Wine-Devel - list.winehq.org

List unsubscribe.
by Philippe Groarke Jan. 13, 2026

Jan. 13, 2026

4 3

11.0 release notes (please review)
by Alexandre Julliard Jan. 12, 2026

Jan. 12, 2026

Folks, Here are the tentative release notes for 11.0. Please review them and let me know if anything is incorrect or missing. Many thanks to Esme, Jacek, Michael, Piotr, Rémi, Vibhav and Zeb for their contributions! I'm planning to release the final 11.0 tomorrow. -- Alexandre Julliard julliard(a)winehq.org

3 3

Wine staging 11.0-rc5 release
by Alistair Leslie-Hughes Jan. 9, 2026

Jan. 9, 2026

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

Handling page faults in syscalls
by tblodt＠icloud.com Dec. 27, 2025

Dec. 27, 2025

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 Dec. 27, 2025

Dec. 27, 2025

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 Dec. 25, 2025

Dec. 25, 2025

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 Dec. 21, 2025

Dec. 21, 2025

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 Dec. 13, 2025

Dec. 13, 2025

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 Dec. 10, 2025

Dec. 10, 2025

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 Dec. 6, 2025

Dec. 6, 2025

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