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

Wine staging 10.17 release

by Alistair Leslie-Hughes

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.

Oct. 18, 2025

Upcoming vkd3d 1.18 release

by Henri Verbeet

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

Oct. 15, 2025

Wine staging 10.16 release

by Alistair Leslie-Hughes

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.

Oct. 4, 2025

RE: ALSA MIDI is not working under NixOS

by Kevin Puetz

> For me at least winepulse. drv and winealsa. drv are in content exactly identical. Maybe this could be a side-effect of reproducible builds? Here the hashes aren't identical for those two libraries ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ and winealsa.drv are in content exactly identical. > > Maybe this could be a side-effect of reproducible builds? Here the > hashes aren't identical for those two libraries Probably, yes - in PE builds, the binaries would not be exactly identical, because https://gitlab.winehq.org/wine/wine/-/commit/b0908666639d5dfe825b5d5f3b9893… was only a partial fix. Winebuild writes the export table with a reproducible hash (of the filename) to produce the export table timetime, but mingw-ld from binutils still introduces a duplicate export table (named "dll stuff" if you add -Wl,-Map=) that gets populated at https://github.com/bminor/binutils-gdb/blob/f86c456bec7969779dd044c313e419f… This is just junk data, but it ends up in the file following the one generated by winebuild that readers actually use. Now that winegcc uses Wl,--exclude-all-symbols this extra table now has zero symbols in it, but it still makes a duplicate export directory table, but that header still has a timestamp in it https://github.com/bminor/binutils-gdb/blob/f86c456bec7969779dd044c313e419f… However, NixOS is all about reproducible builds, so I'd expect their binutils to use SOURCE_DATE_EPOCH. --no-insert-timestamp, or something, like that to remove the BFD timestamps in general, and then one might get identical binaries. I dug into this at one point curious about the large/non-reproducible .edata section, found !3173, but decided the few remaining bytes of "dll stuff" junk data were basically harmless, so I never bothered to report it... but it seems topical to this thread. Certainly I think we'd rather not have the duplicate export directory table, if there was some way to get binutils to skip producing it. But there doesn't seem to be anything obvious... Public

Oct. 1, 2025