wine-devel

wine-devel@winehq.org

5 participants
84473 discussions

Gitlab blocking user account
by Wine 17 Sep '25

17 Sep '25

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

Wine staging 10.15 release
by Alistair Leslie-Hughes 13 Sep '25

13 Sep '25

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

Travels
by Alexandre Julliard 21 Jul '25

21 Jul '25

Folks, Just a heads up that I'm going to be traveling for the next 3 weeks. I'm still going to review and commit MRs, but on a somewhat irregular schedule. Also there won't be a new release during that time, so Wine 10.13 will be out on August 15. -- Alexandre Julliard julliard(a)winehq.org

1 0

Upcoming vkd3d 1.17 release
by Henri Verbeet 17 Jul '25

17 Jul '25

Hi all, The planned release date for vkd3d 1.17 is Thursday August 21. That means the public API will become frozen a week from now on July 24, and features will be frozen two weeks before the release, on August 7. 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.18 is November 20. 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

How to use AddressSanitizer with Wine?
by Alex Henrie 13 Jul '25

13 Jul '25

Dear oenologists, I would like to use GCC's AddressSanitizer [1] to investigate a memory corruption bug in Wine. There must be a way to do it because I see multiple references to "ASan" in the Wine commit log in commits from this year.[2] I found some instructions on the WineHQ wiki,[3] but I get a myriad of linker errors when I try to follow them. What Linux distributions can successfully compile Wine with libasan? Are there special steps not mentioned in the wiki? Does AddressSanitizer work with MinGW, or only with non-PE builds? I'd love to get AddressSanitizer working myself, but even if I can't, thanks to Bernhard and Nikolay for using it to fix a lot of bugs already. -Alex [1] https://github.com/google/sanitizers/wiki/AddressSanitizer [2] https://gitlab.winehq.org/wine/wine/-/commits/master?search=ASan [3] https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#memory--address-c…

2 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel