May 2026 - Wine-Devel - list.winehq.org

GitLab merge warnings
by Alex Henrie May 30, 2026

May 30, 2026

Hello Wine maintainers, Currently, unless a merge request is based on the absolute latest upstream master branch, GitLab displays the following warnings: ⛔ Merge blocked: 1 check failed ⛔ Fast forward merge is not possible. Please rebase. More than once, I've seen well-meaning contributors follow those instructions and rebase their merge requests every single day to resolve the warning. That adds pointless noise to the merge request and wastes time rerunning the test suite. GitLab 19.0 introduced a new feature to suppress those warnings, called "automatic rebase".[1] To enable it, a GitLab administrator needs to go to the project Settings, click "Merge requests", under "Fast-forward merge" check the box "Enable automatic rebase prior to merge", and click "Save changes". Can we please update gitlab.winehq.org to GitLab 19.0 and enable automatic rebase on all of the WineHQ projects? Since few people are allowed to merge MRs and none of you seem to actually do merges via the GitLab UI, the change should be purely cosmetic and not affect your workflow at all. -Alex [1] https://gitlab.com/gitlab-org/gitlab/-/work_items/895

3 2

Wine staging 11.10 release
by Alistair Leslie-Hughes May 30, 2026

May 30, 2026

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.10 (287 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * [45364] - Frostpunk is very dark * [57980] - kernel32: Implement SetThreadpoolTimerEx. * [43703] - rtscom: Rebelle demo crashes when using "Microsoft Ink compatible" tablet * [31554] - inkobj: PDF Annotation crashes on second startup Updated: * vkd3d-latest * dcomp-DCompositionCreateDevice2 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

Feedback needed for a theme PR
by fatihbakal7＠protonmail.com May 27, 2026

May 27, 2026

I currently need feedback as to how to implement a theming improvement to wine. My recommendation is that all prefixes use $HOME/.config/wine.msstyle/.theme if possible. I was told this is the place to ask for feedback. Please see https://gitlab.winehq.org/wine/wine/-/merge_requests/10920

7 16

Re: GitLab merge warnings
by Alex Henrie May 27, 2026

May 27, 2026

On Tue, May 26, 2026 at 2:16 PM Esme Povirk <esme(a)codeweavers.com> wrote: > > If it matters, I actually do use the GitLab UI to do merges. > > However, the GitLab UI discourages using it for rebases, linking to this > page: > https://gitlab.winehq.org/help/ci/pipelines/merge_request_pipelines.html#ru… > > Therefore, I do not use the GitLab UI to do rebases. Does the new > version address this somehow? If I understand that page correctly, it's just saying that merge requests can introduce malicious code that is run as part of the test suite before the merge request is actually merged. GitLab is just trying to warn you to not do test runs on untrusted code, and warn you that you clicking "Rebase" will automatically trigger a test run even if the merge request's author does not have permissions to do a test run. If you want to rebase without doing a test run, there is a separate "Rebase without pipeline" button on the merge request. The "automatic rebase" option that I'd like to enable effectively clicks "Rebase without pipeline" for you when you click "Merge".[1] I think the new option would be perfect for your workflow. -Alex [1] https://docs.gitlab.com/19.0/user/project/merge_requests/methods/#automatic…

1 0

Reference terminal for writing conformance tests for console functions
by Barath Rk May 25, 2026

May 25, 2026

I am trying to implement the ReadConsoleInputExW function, and while writing tests for the same, realized that the behaviour of my test programs vary across consoles inside my Windows 10 VM. For example, the output is different when I use cmd to run the tests versus using MSYS2(which uses mintty) to run the tests. My question is: should the behaviour exhibited by the test program when run on cmd in Windows be taken as the canonical reference in this case? If so, then when testing my implementation on the programs using wine, is it enough for the output in wineconsole to be consistent with the cmd output? Thanks in advance.

3 6

Explanation of CTL_CODES
by Barath Rk May 23, 2026

May 23, 2026

I am trying to implement the ReadConsoleInputEx(A|W) functions in kernelbase(It is needed for Microsoft's edit.exe. See bug #58252). I figured I could do that by defining a new CTL_CODE in include/wine/condrv.h. However, after a long time spent in exploring the source code, I don't get where the handler for the codes, such IOCTL_CONDRV_READ_INPUT are defined. Would appreciate some direction on this. Thanks in advance.

3 2

Wine staging 11.9 release
by Alistair Leslie-Hughes May 16, 2026

May 16, 2026

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.9 (273 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * vkd3d: Fix compile errors under mingw. * d3d9: Add a fake d3d9 device vtbl initialization sequence. Removed (No longer required). * None Added: * None Updated: * vkd3d-latest * dcomp-DCompositionCreateDevice2 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

Fwd: Potential Clean Room issues with xinputaup
by Yusuf May 4, 2026

May 4, 2026

Hi All! For the xinputuap bits I remember that I may(?) have examined the Debug Symbols for it, reading the Clean Room guidelines it seems to be against the conditions here. I don't plan to contribute to the wine projects(nowadays I have moral objections to it) yet if you wish ban me from your project. Yusuf

2 3

[PATCH] d2d1: Fix arc center translation to use center.y in _31 update.
by Giang Nguyen May 4, 2026

May 4, 2026

In d2d_arc_to_bezier(), when computing the affine transform that maps the canonical unit-arc parameter space to the actual arc, the translation contribution from the arc center is meant to be the linear matrix-vector product M * center, i.e.: (_31, _32) += (M11*cx + M12*cy, M21*cx + M22*cy) The first line of the update used center.x in both terms, which yields M11*cx + M12*cx instead of M11*cx + M12*cy. Effect is invisible when M12 == 0 (i.e. arc->rotationAngle == 0), which is the common case for unrotated arcs in UI rendering. Becomes visible for arcs with a non-zero rotationAngle, where the arc center ends up displaced along the rotation axis. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=59718 Signed-off-by: Giang Nguyen <nen24t(a)gmail.com> --- dlls/d2d1/geometry.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dlls/d2d1/geometry.c b/dlls/d2d1/geometry.c index 68de4c2193c..b7dc2b7b55e 100644 --- a/dlls/d2d1/geometry.c +++ b/dlls/d2d1/geometry.c @@ -1311,7 +1311,7 @@ static int d2d_arc_to_bezier(const D2D_POINT_2F *start_point, const D2D1_ARC_SEG m._32 = 0.5f * (arc->point.y + start_point->y); if (!zero_center) { - m._31 += (m._11 * center.x + m._12 * center.x); + m._31 += (m._11 * center.x + m._12 * center.y); m._32 += (m._21 * center.x + m._22 * center.y); } -- 2.43.0

2 1

[PATCH] d2d1: Strip translation from transform when scaling arc radii.
by Giang Nguyen May 4, 2026

May 4, 2026

d2d_arc_transform() applies the same affine matrix to the arc's end point and to its two radius vectors (width, 0) and (0, height). That is correct for the end point (a position) but wrong for the radii (direction vectors): when the matrix includes a non-zero translation (_31, _32), the transformed radius vector becomes (width * _11 + _31, width * _12 + _32) and the resulting d2d_point_length() returns sqrt((width*_11 + _31)^2 + (width*_12 + _32)^2) instead of the intended sqrt((width*_11)^2 + (width*_12)^2) = width * sqrt(_11^2 + _12^2) i.e. the magnitude of the linear part only. Visible whenever a path that contains an arc is wrapped in a transformed geometry whose transform has both a non-trivial linear part and a translation — common for plugin host UIs with offset rendering. Fix: build a local copy of the matrix with _31 = _32 = 0 and use it for the radius transforms. Keep the original transform for the end point. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=59718 Signed-off-by: Giang Nguyen <nen24t(a)gmail.com> --- dlls/d2d1/geometry.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/dlls/d2d1/geometry.c b/dlls/d2d1/geometry.c index 68de4c2193c..eda79d35e2b 100644 --- a/dlls/d2d1/geometry.c +++ b/dlls/d2d1/geometry.c @@ -4479,12 +4479,19 @@ static HRESULT STDMETHODCALLTYPE d2d_path_geometry_Open(ID2D1PathGeometry1 *ifac static inline void d2d_arc_transform(D2D1_ARC_SEGMENT *arc, const D2D1_MATRIX_3X2_F *transform) { + D2D1_MATRIX_3X2_F linear = *transform; D2D_POINT_2F point; + /* Radii are direction vectors, so they should be transformed with the + * linear part of the matrix only. Including the translation would add + * (_31, _32) to (width, 0) and (0, height) and yield incorrect lengths. */ + linear._31 = 0.0f; + linear._32 = 0.0f; + d2d_point_transform(&arc->point, transform, arc->point.x, arc->point.y); - d2d_point_transform(&point, transform, arc->size.width, 0.0f); + d2d_point_transform(&point, &linear, arc->size.width, 0.0f); arc->size.width = d2d_point_length(&point); - d2d_point_transform(&point, transform, 0.0f, arc->size.height); + d2d_point_transform(&point, &linear, 0.0f, arc->size.height); arc->size.height = d2d_point_length(&point); } -- 2.43.0

1 0

[PATCH] d2d1: Fix uninitialized points[0] in degenerate-radius arc fallback.
by Giang Nguyen May 4, 2026

May 4, 2026

When d2d_arc_to_bezier() rejects an arc because both radii are below the fuzz threshold, it returns 0 to signal "treat as a straight line". The caller d2d_figure_add_arc() then passes points[0] to d2d_figure_add_lines() as the line endpoint: count = d2d_arc_to_bezier(&figure->vertices[last], arc, points); if (count > 0) return d2d_figure_add_beziers(figure, ...); else if (count == 0) return d2d_figure_add_lines(figure, points, 1); But points[0] is never written on the radius-rejection path, so add_lines() consumes uninitialized stack memory as the endpoint. Result: random line target, undefined visual behavior for any path that contains a degenerate-radius arc. Fix is to write the arc's specified end point into points[0] before returning 0, which matches the natural fallback semantics ("draw a line from the previous vertex to the arc's endpoint"). Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=59718 Signed-off-by: Giang Nguyen <nen24t(a)gmail.com> --- dlls/d2d1/geometry.c | 1 + 1 file changed, 1 insertion(+) diff --git a/dlls/d2d1/geometry.c b/dlls/d2d1/geometry.c index 68de4c2193c..51d587673dd 100644 --- a/dlls/d2d1/geometry.c +++ b/dlls/d2d1/geometry.c @@ -1247,6 +1247,7 @@ static int d2d_arc_to_bezier(const D2D_POINT_2F *start_point, const D2D1_ARC_SEG if (!d2d_arc_check_radius(rHalfChord2, fuzz2, &radius.x) || !d2d_arc_check_radius(rHalfChord2, fuzz2, &radius.y)) { + points[0] = arc->point; return 0; } -- 2.43.0

1 0

Wine staging 11.8 release
by Alistair Leslie-Hughes May 2, 2026

May 2, 2026

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 11.8 (281 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Removed (No longer required). * None Added: * [59708] - d3d9: missing MSVC vtable byte-pattern Updated: * vkd3d-latest * dcomp-DCompositionCreateDevice2 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