October 2025 - Wine-Devel - list.winehq.org

Wine staging 10.17 release
by Alistair Leslie-Hughes Oct. 18, 2025

Oct. 18, 2025

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.17 (295 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * draw: Return correct devices based off requested DirectX version. * odbc32: SQLGetData handle ANSI driver * odbc32: Record loaded driver SQL_ATTR_ODBC_VERSION * comctl32: Bump version to 6.0. * d3dx10/tests: Add tests for the D3DX10_IMAGE_LOAD_INFO structure argument. * d3dx10: Create 3D textures for images representing 3D textures. * shell32: Improve semi-stub SHGetStockIconInfo, try find existing iconhandle * shell32: Set SFGAO_HASSUBFOLDER correctly for normal shellfolders. * winex11.drv/window: Query the X server for the actual rect of the window before unmapping it Removed (No longer required). * None Added: * [58786] - iccvid: Support ICM_DECOMPRESSEX_BEGIN message * [36208] - d3drm: Stops crash when Star Wars Rebellion battles. * [58418] - wininet: Stop crash in InternetQueryOptionW when NULL buffer is provided. 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

Upcoming vkd3d 1.18 release
by Henri Verbeet Oct. 15, 2025

Oct. 15, 2025

Hi all, The planned release date for vkd3d 1.18 is Thursday November 20. That means the public API will become frozen next week on October 23, and features will be frozen two weeks before the release, on November 6. 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 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 1.19 is Thursday February 19. 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 10.16 release
by Alistair Leslie-Hughes Oct. 4, 2025

Oct. 4, 2025

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.16 (281 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Implement NtSetLdtEntries. * ntdll/tests: Add some tests for NtSetLdtEntries. * vbscript: redim without dim. * wscript: return TRUE for /d and /u stub switches. * Fix calculation of listbox size when horizontal scrollbar is present. * ddraw: Set dwZBufferBitDepth in ddraw7_GetCaps. * wineboot: Add some generic hardware in HKEY_DYN_DATA\Config Manager\Enum * odbc32: SQLDriverConnectW fallback to SQLDriverConnect when required. * odbc32: SQLGetInfoW support ANSI fallback. * odbc32: SQLExecDirectW call fallback SQLExecDirect Removed (No longer required). * user32-FlashWindowEx (already fixed). * eventfd_synchronization (NTSYNC is upstream now). Added: * [48598] d3dx9: Improve Rendering in MudRunner. Updated: * vkd3d-latest * 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 0

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