August 2025 - Wine-devel - list.winehq.org

Gitlab News
by Alexandre Julliard 15 Sep '25

15 Sep '25

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

Clarification about Reverse Engineering Windows applications
by Barath Rk 09 Sep '25

09 Sep '25

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

Wine staging 10.14 release
by Alistair Leslie-Hughes 30 Aug '25

30 Aug '25

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

How can I debug an issue where a specific commit breaks transparency?
by zhengxianwei 16 Aug '25

16 Aug '25

>> | * cb787d0c566 - (2 months ago) win32u: Use a pbuffer to implement GL on memory DCs. - Rémi Bernon This commit caused one of my images to go from transparent to non-transparent. How should I debug this? I tried using RenderDoc to capture, but it errors out saying that on Linux it supports the core profile and not the compatibility profile. When I capture a trace with apitrace, it seems the program isn’t using a standard OpenGL frame rendering flow. May I ask what the default method is in Wine for debugging OpenGL or investigating incorrect/garbled rendering?

1 0

Wine staging 10.13 release
by Alistair Leslie-Hughes 16 Aug '25

16 Aug '25

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 10.13 (300 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ws2_32: Add afunix.h header. Removed (No longer required). * None Added: * [31675] oleaut32: Use correct flag to detect IDispatch interfaces. Updated: * vkd3d-latest * oleaut32-default-pic-size 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