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

[Bug 58297] [Wayland-only mode] Minimize button click makes the app window buttons lock up

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58297 Alex Schwartz <alexschwartz01(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Alex Schwartz <alexschwartz01(a)gmail.com> --- Fixed by https://gitlab.winehq.org/wine/wine/-/merge_requests/10487 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 58297] [Wayland-only mode] Minimize button click makes the app window buttons lock up

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58297 --- Comment #2 from Alex Schwartz <alexschwartz01(a)gmail.com> --- Fixed as of wine 11.8 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59775] German umlauts won't be handled correctly by typing

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59775 --- Comment #6 from AndyF <andreas.franz(a)arcor.de> --- Issue still exists with 11.10. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59811] New: RDR2 (Red Dead Redemption 2) fails to initialize graphics device (Error Code 18) since 11.10

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59811 Bug ID: 59811 Summary: RDR2 (Red Dead Redemption 2) fails to initialize graphics device (Error Code 18) since 11.10 Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: DANIELE.AMODEO(a)OUTLOOK.COM Distribution: --- Red Dead Redemption 2 fails to launch with "Error Code 18: failed to initialize graphics device" since upgrading Wine Staging from 11.9 to 11.10. Downgrading back to Wine Staging 11.9 immediately resolves the issue. System: - OS: Arch Linux - GPU: AMD Radeon RX 6950 XT - Driver: RADV Mesa 26.1.1 - Wine mode: wow64 (64-bit prefix) - DXVK and VKD3D installed via winetricks - Graphics API set to kSettingAPI_DX12 in system.xml Steps to reproduce: 1. Install Wine Staging 11.10 2. Launch Red Dead Redemption 2 via Wine 3. Error Code 18 appears immediately, game does not start Expected: game launches normally (as it did with 11.9) Actual: "Rockstar Games failed to initialize graphics device. Error Code: 18" Suspected cause: dcomp-DCompositionCreateDevice2 patches introduced in 11.10. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 32342] Multiple applications and games using 'Webkit', 'Blink' or 'CEF' (libcef) web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=32342 Robert Walker <bob.mt.wya(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|bob.mt.wya(a)gmail.com | -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59807] Regression in multithreaded application

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59807 gianluca+wine(a)sottospazio.it changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gianluca+wine(a)sottospazio.i | |t --- Comment #1 from gianluca+wine(a)sottospazio.it --- Created attachment 81052 --> http://bugs.winehq.org/attachment.cgi?id=81052 Smallest reproducer Hello, I managed to make the smallest reproducer for the regression. The application attached opens a window and waits for string from a thread. When a string is received the GUI shows the string in the client area and creates a Printer Device Context. In Wine 11.9 the application shows "Hello Alice!", "Hello Bob!" and exits. In Wine 11.10 the application shows "Hello Alice!" and gets stuck because the call to SendMessage() from the non-GUI thread never returns. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59810] New: Buffered paint alpha/clear operations are missing

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59810 Bug ID: 59810 Summary: Buffered paint alpha/clear operations are missing Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)list.winehq.org Reporter: juan3(a)yandex.com Distribution: --- Applications using the buffered paint API can fail to render themed/translucent controls correctly because Wine does not perform the clear and alpha operations requested through BufferedPaintClear() and BufferedPaintSetAlpha(). These calls are used after BeginBufferedPaint() to prepare or adjust the backing buffer before EndBufferedPaint() copies the result to the target DC. On Windows, callers can clear a sub-rectangle of the paint buffer and apply a uniform alpha value to a sub-rectangle. Wine currently leaves those operations ineffective. Expected behavior: - BufferedPaintClear(buffer, NULL) clears the whole buffered paint area. - BufferedPaintClear(buffer, rect) clears the requested rectangle, clipped to the buffer. - BufferedPaintSetAlpha(buffer, NULL, alpha) applies alpha to the whole buffered paint area. - BufferedPaintSetAlpha(buffer, rect, alpha) applies alpha to the requested rectangle, clipped to the buffer. - Empty rectangles should succeed without changing pixels. Impact: Applications that depend on these operations may leave stale pixels in the buffered paint surface, lose expected transparency, or draw themed controls with incorrect backgrounds/alpha. One possible implementation direction would be to update the DIB-backed buffer directly for these operations, clipping the requested rectangle to the buffer bounds. For non-DIB-backed buffers, BufferedPaintClear() could clear through the memory DC. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59809] New: XF86VidModeSetGamma BadValue X error can terminate process

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59809 Bug ID: 59809 Summary: XF86VidModeSetGamma BadValue X error can terminate process Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)list.winehq.org Reporter: juan3(a)yandex.com Distribution: --- XF86VidModeSetGamma may raise a BadValue X error for out-of-range gamma values. In winex11.drv, X11DRV_XF86VM_SetGamma() calls pXF86VidModeSetGamma() without wrapping the request in Wine's X error handling path. Other XF86VidMode requests in this area use X11DRV_expect_error() / X11DRV_check_error(). Without the guard, the X error can escape to Xlib's default handler and terminate the process. Observed issue: - X Error of failed request: BadValue (integer parameter out of range for operation) - Major opcode: XFree86-VidModeExtension - Minor opcode: XF86VidModeSetGamma Expected behavior: Wine should handle the X error and return failure from the gamma call instead of allowing the process to terminate. One possible fix would be to wrap pXF86VidModeSetGamma() with X11DRV_expect_error(gdi_display, XVidModeErrorHandler, NULL), synchronize when needed, check X11DRV_check_error(), and return FALSE on X errors. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59808] New: Windows Form with ToolStripMenuItem closes program when selected in Bottles running in Linux Mint.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59808 Bug ID: 59808 Summary: Windows Form with ToolStripMenuItem closes program when selected in Bottles running in Linux Mint. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: david.hine(a)outlook.com Distribution: --- I am writing my own programs in Visual Studio 2026 (Windows 11) to be used in a Bottles environment in Linux Mint. I am using the ToolStripMenu (menuStrip1 from the ToolBox). My programs compiled using .net 7.00 & before work ok in Bottles when the menu item is selected, but any .net releases after .net 7.00 cause the application to close. As .net 7.00 is no longer supported this will cause a future problem for me. The Bottles version is 64.1. Linux Mint version 22.3 Zena. I attempted to report the problem to Bottles, but their web page tells me to report Windows application problems to Wine or Proton. I hope you can help in this matter. Thank you. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026

[Bug 59807] New: Regression in multithreaded application

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59807 Bug ID: 59807 Summary: Regression in multithreaded application Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: gianluca+wine(a)sottospazio.it Distribution: --- Hello, after upgrading from Wine 11.9 to Wine 11.10 I noticed a regression in my application. This is a GUI application that starts a network thread to connect to a server, waiting to receive messages using overlapped operations. After receiving a message, the network thread uses SendMessage() to send the received data to the GUI thread, which creates a Device Context and prints the data. But after creating the Device Context the networking thread becomes stuck and doesn't receive data anymore. I bisected the repo to find the commit that introduced the problem and the bisection points to: commit c9e4e0152548e6a369bd7bcdeedc5bd64f446fb6 (HEAD) Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu May 21 12:03:07 2026 +0200 win32u: Use pthread instead of the TEB to access internal per-thread data. I tried to revert it but unfortunately there are conflicts with later commits and I didn't know how to resolve them. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

May 31, 2026