September 2025 - Wine-Devel

ALSA MIDI is not working under NixOS
by Yuxuan Shui Oct. 1, 2025

Oct. 1, 2025

Hi, I have an interesting bug (maybe?) for you. I don't know what's the best way to explain so I will just retrace how I found out what's happening. I was investigating Bug 58216 (completely unrelated, but this is how I encountered this problem). When I started the game, it just hangs with a black screen. It didn't crash but it didn't start either. Nothing stood out in the logs, so I attached winedbg. It showed a thread stuck in mmdevapi.dll::DriverProc, handling a DRV_FREE. The notify_thread wasn't stopping, clearly the midi_release call isn't causing the midi_notify_wait to return. So I added debug logging to alsamidi.c, and they weren't being hit. Turning on +mmdevapi debug channel shows winealsa.drv was being loaded as the MIDI driver. What is going on? I was perplexed. Single stepping into the unix call to midi_release showed it somehow called into pulse_not_implemented. Turning on +module and I found this: 0024:trace:module:load_native_dll found L"C:\\windows\\system32\\winepulse.drv" for L"\\??\\C:\\windows\\system32\\winealsa.drv" This is bizarre. Reading the code I saw a few server calls for memory mapping stuff, so I turned on +server. And I saw a create_mapping call made with a file handle for winealsa.drv, but a later get_mapping_info call on that mapping returned winepulse.drv. Okay, I was reading wineserver code now. In the create_mapping function we have: mapping->fd = get_fd_object_for_mapping( ... ) And get_fd_object_for_mapping can replace the given fd with another fd of the same underlying inode#. Ah ha! I look at the inode of winealsa.drv and winepulse.drv, and yeah they are identical. * * * But how? I run NixOS. On NixOS all installed software packages come out of the "nix store", and nix store has an "optimise" feature which replaces identical files in the nix store with hardlinks. winealsa.drv and winepulse.drv are empty dlls only there for loading their corresponding .so unixlibs, that's why they are identical, and were replaced by hardlinks. Question: what's the right thing to do here? Considering hardlinked files indistinguishable for mapping purposes seems reasonable, and I won't be surprised if there are testcases testing specifically this. But adding unixlibs to the mix and things change. Now the path from which a module is accessed becomes significant too, because it will be used to find the .so. In this case the result was the wrong unixlib being used. Help? Thanks. -- Regards Yuxuan Shui

7 13

WineConf 2025 Videos
by Jeremy Newman Sept. 29, 2025

Sept. 29, 2025

WineConf 2025 videos now available on our WineHQ YouTube channel: https://www.youtube.com/@wine-hq Keynote - Alexandre Julliard https://youtu.be/zsdukp8xfv4 Framework Mono – Esme Povirk https://youtu.be/l3d68YJtYxY State of crypto support in Wine – Hans Leidekker https://youtu.be/eQOz1nD0VGI Emulation / ARM64 session https://youtu.be/BTraz8LDU8E Minimal Protonification – Arkadiusz Hiler https://youtu.be/U8Xq6jgijos Upholding the LGPL in Wine: Next Steps in Our Journey – Bradley M. Kuhn + Denver Gingerich https://youtu.be/IUE95tVTmO4 Wine on macOS State of the Union – Brendan Shanks https://youtu.be/ftqwLHQveq4 Wine Stable – Michael Stefaniuc https://youtu.be/x6eP56UmxiE llvm-mingw: How to QA a toolchain on a zero budget – Martin Storsjö https://youtu.be/NpxO3DGDxKE The video links along with the slides are also available via our WineConf Wiki page: https://gitlab.winehq.org/wine/wine/-/wikis/WineConf/WineConf-2025 -- CodeWeavers, Inc. 🐉 Jeremy Newman ⛭ Director of IT ────────────────────────────────────────────────────── 📧 jnewman(a)codeweavers.com 🌐 https://www.codeweavers.com/about/people/jnewman

2 1

Release dates
by Alexandre Julliard Sept. 29, 2025

Sept. 29, 2025

Folks, It was great to see many of you at WineConf! For those who didn't make it, videos of the various presentations will be available shortly. And if you don't want to watch the entire keynote (can't blame you ;-) the important thing to note is that the code freeze for Wine 11.0 will start on December 5. Also with many people being in transit or in meetings last week there wasn't a lot of activity, so the 10.16 release will be delayed until this Friday, October 3. -- Alexandre Julliard julliard(a)winehq.org

1 0

slides from Mono talk
by Esme Povirk Sept. 28, 2025

Sept. 28, 2025

Here are the slides from my Wineconf talk and my notes with references for most of the history. I would link to the recording, but since the youtube stream didn't work, and the winehq twitch channel doesn't seem to have VODs enabled, I can't find any.

2 1

WineConf 2025 Live Stream
by Jeremy Newman Sept. 27, 2025

Sept. 27, 2025

We will be attempting to live stream during WineConf this year. This may or may not work. We will also be recording and the files for the conf will be posted later as well. If you want to check out the live stream, you can do so from here: https://youtube.com/live/FDncgrlCoFc The stream should start at Saturday September 27th at 09:00 CEST (GMT+2) -- CodeWeavers, Inc. 🐉 Jeremy Newman ⛭ Director of IT ────────────────────────────────────────────────────── 📧 jnewman(a)codeweavers.com 🌐 https://www.codeweavers.com/about/people/jnewman

2 4

Gitlab blocking user account
by Wine Sept. 17, 2025

Sept. 17, 2025

Has anyone else had issues with their dev account getting blocked by Gitlab? I've been locked out for a couple of hours now. Once an account gets blocked, Gitlab just returns a white screen. There seems to be a timer that elapses after 10 or so minutes that allows me to log back in but very soon after my account gets flagged again for some reason. My alt account is able to login so it seems user specific. Even my alt account eventually gets locked out so maybe it's ExpressVPN related? Previously changing ExpressVPN locations seemed to help but none have worked yet this time around. When the block occurs I'll receive a message at the top of Gitlab indicating a timeout or something. I haven't been able to screenshot the message yet so I'll keep trying for reference. If there's a more appropriate channel to resolve this issue please let me know. I figured Jeremy Newman may have some insights but my only interaction with him so far has been on Gitlab fixing AppDB issues which I can't access.

1 0

Gitlab News
by Alexandre Julliard Sept. 15, 2025

Sept. 15, 2025

Folks, As you may have noticed, now that the ARM64 support is done (just kidding), I've picked up the work on the Gitlab migration: 1. The Wiki has been moved to Gitlab, it's now at [1]. Existing URLs to the previous Wiki are redirected to the appropriate page. There are also separate Wikis for appdb, vkd3d and wine-staging, under their respective project pages. As part of the migration I've done some minor edits, but most of the Wiki is badly out-of-date, and could use some love. Help is welcome! Check the Writers page [2] for details on how to contribute. 2. We are now hosting the Mono project on the WineHQ Gitlab [3]. Please join me in welcoming the Mono developers to our community! 3. We have new hardware for the Gitlab server, which is now noticeably faster. Thanks to Jeremy Newman for setting this up! This also made it possible to enable robots.txt again so that our content is indexed. The next step will be to install new hardware for the Gitlab runners to offer more CI bandwidth. 4. The Gitlab issue tracker is currently disabled because it was attracting too much spam. I'm going to re-enable it, first for use by Mono, and then ultimately also for Wine itself. To fight the spam I'm planning to add an explicit user verification step, modelled along the procedure used by Freedesktop.org [4]. 5. As part of the new sign-up process, I think it would be a good idea to have an explicit Code of Conduct to spell out our expectations. Instead of reinventing the wheel, I propose that we adopt the Contributor Covenant [5] that many other projects (including Mono) are already using. Thoughts? Questions? Comments? [1]: https://gitlab.winehq.org/wine/wine/-/wikis [2]: https://gitlab.winehq.org/wine/wine/-/wikis/Writers [3]: https://gitlab.winehq.org/mono [4]: https://gitlab.freedesktop.org/freedesktop/freedesktop/-/wikis/home [5]: https://www.contributor-covenant.org/ -- Alexandre Julliard julliard(a)winehq.org

4 4

Wine staging 10.15 release
by Alistair Leslie-Hughes Sept. 13, 2025

Sept. 13, 2025

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.15 (XXXX patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * msxml3: Correct looping of Document Element properties. * d3dx11_43: Implement D3DX11GetImageInfoFromMemory. * d3dx11_43: D3DX11GetImageInfoFromMemory - Only use frame for non DDS images Removed (No longer required). * None Added: * [48598] d3dx9: Improve ID3DXAnimationController Animation set support. * [58673] msxml: Add GB2312 support for builtin character converter. Updated: * vkd3d-latest * odbc32-fixes * winedevice-Default_Drivers * d3dx11_43-D3DX11CreateTextureFromMemory 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 1

Clarification about Reverse Engineering Windows applications
by Barath Rk Sept. 9, 2025

Sept. 9, 2025

Is it alright to RE Windows applications as long as you are not trying to RE MS API implementations or MS applications? I do not quite understand the "Clean Room Guidelines" in this regard and would like some clarification.

2 2