January 2026 - 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

FOSDEM
by Huw Davies 27 Jan '26

27 Jan '26

Hi folks, Once again, many CodeWeavers folks will be in Brussels this weekend attending FOSDEM. If anybody else is around please feel free to either drop me an email or simply turn up to the BrewDog on Saturday evening from 17:00. Many of us will be in Brussels Thursday, Friday and Sunday evenings too, but our exact location is less certain; if you let me know you’re interested, I can try to keep you in the loop. Sorry for the late notice (again)! Huw

2 1

Wine staging 11.1 release
by Alistair Leslie-Hughes 24 Jan '26

24 Jan '26

Binary packages for various distributions will be available from: https://www.winehq.org/download For the complete wine release notes https://gitlab.winehq.org/wine/wine/-/releases/wine-11.0 Summary since last release * Rebased to current wine 11.1 (254 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * [47015] msxml3: Photoshop CC2019 login screen content does not render without native msxml3 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

Unixlib support for non-Wine binaries? (Or: would upstream Wine take a Spout2 to PipeWire bridge?)
by Hoshino Lina 21 Jan '26

21 Jan '26

Hi! I'm working on a tool to bridge Spout2 [1][2] to PipeWire. Spout2 is a windows-only frame-sharing technology widely used for video-streaming and mixing apps. It allows one app to send video to another, much like JACK does for audio on Linux (and now PipeWire for both A/V). For example, the majority of the VTubing/streaming world relies on Spout2 to stream avatars and graphics on screen. To make this work, the bridge needs to use unixlib to do the bridging between the Windows and Linux worlds. I got it to build outside the Wine source tree by using just a few headers outside the public wine headers (unixlib.h, server.h, server_protocol.h). Originally I intended to distribute it as a simple installable that users could throw into their WINEPREFIX, but it turned out that for unixlib to work, the exe needs to be marked as builtin and distributed as a Wine builtin exe in wine/x86_64-windows with the .so file in the companion x86_64-unix directory. - Would it make sense for Wine to change its unixlib loading code to work with non-builtin binaries, such as looking for the .so in the same directory as the .dll/.exe? - Otherwise, would upstream Wine be interested in merging this feature? The main dependencies are PipeWire and libfunnel [3]. The app does rely on some Wine/DXVK internals (unixlib, KeUserDispatchCallback, \??\SharedGpuResource, ProcessWineMakeProcessSystem) but it's not strictly necessary for those to remain stable across all future Wine releases, as making updates to stay compatible is not a major issue. At this time I plan to distribute it as a "patch" that can be applied to Proton installations (which just drops in the exe/so and adds it to wine.ini). Another option is using WINEDLLPATH, which should work for regular Wine (this one is problematic on Proton since the Proton launcher unconditionally clobbers that environment variable). One potential issue is that due to the less than ideal design of Spout2, there is no way to know when apps start using Spout2 other than polling for the existence of a named shared memory segment. So if this is merged unconditionally, the service would have to always run even if not needed, unless some kind of hack is added to `CreateFileMappingA` to watch for the "SpoutSenderNames" mapping and launch the service on demand when it is created. On top of that, once PipeWire -> Spout2 support is added, it would mean the daemon is bridging every possible PipeWire stream to Spout2 as soon as any Spout2 app runs regardless of whether any Spout2 consumer exists for it. The only way I can think of avoiding this (other than manual config) is, again, some kind of Wine hook that only triggers the bridge for a stream when some Spout2 consumer app has the specific stream shared memory and/or mutex opened to a handle... it really isn't a well designed protocol, unfortunately, but it is what is in use on Windows. [1] https://spout.zeal.co/ [2] https://github.com/leadedge/Spout2 [3] https://github.com/hoshinolina/libfunnel ~~ Lina

4 5

How do I unsubscribe from the mailing list?
by Kirill Mosorov 21 Jan '26

21 Jan '26

Hello! How can I unsubscribe from this mailing list? :)

1 0

UnixLib
by imichaelost＠gmail.com 19 Jan '26

19 Jan '26

1 0

Availability of wine-devel/wine-gitlab archives
by Dmitry Timoshkov 18 Jan '26

18 Jan '26

Hi all, recently I tried to lookup some previously discussed things in wine-devel archives and was surprised that neither winehq.org nor archive.org provide something useful, all the links I tried don't work. The things get a bit more complex due to transition from pipermail to hyperkitty and current system. Is it possible to make old archives available again and fix access to current wine-devel/wine-gitlab archives? Thanks. -- Dmitry.

4 7

Upcoming vkd3d 1.19 release
by Henri Verbeet 15 Jan '26

15 Jan '26

Hi all, The planned release date for vkd3d 1.19 is Thursday February 19. That means the public API will become frozen next week on January 22, and features will be frozen two weeks before the release, on February 5. This does not mean that development should slow down or stop, of course; after making sure that we're in good shape to release, this would be the ideal time to make sure that any larger features are ready to get merged at the start of the next development cycle. As usual, if you're an upstream vkd3d developer, please do the following: - Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify that all vkd3d tests pass on your hardware/setup, and please send fixes if they don't. - Review and improve the documentation. - Get any larger features ready to get merged at the start of the next development cycle. If you're a downstream user of vkd3d, please test your applications for any regressions, and file bug reports if you find any. The planned release date for vkd3d 2.0 is Thursday May 21. A tentative release schedule for future releases can be found on the vkd3d wiki[1]. Regards, Henri [1] https://gitlab.winehq.org/wine/vkd3d/-/wikis/release-schedule

1 0

Wine staging 11.0 release
by Alistair Leslie-Hughes 13 Jan '26

13 Jan '26

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

List unsubscribe.
by Philippe Groarke 13 Jan '26

13 Jan '26

4 3