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

[Bug 59655] New: comctl32: Infinite WM_PAINT loop in SysListView32 when parent triggers layout update during NM_CUSTOMDRAW (MPC-BE)
by WineHQ Bugzilla June 16, 2026

June 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=59655 Bug ID: 59655 Summary: comctl32: Infinite WM_PAINT loop in SysListView32 when parent triggers layout update during NM_CUSTOMDRAW (MPC-BE) Product: Wine Version: 11.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: comctl32 Assignee: wine-bugs(a)list.winehq.org Reporter: lldmakhbfcrmqyluns(a)nesopf.com Distribution: --- Steps to reproduce: Open MPC-BE. Ensure the Playlist panel is visible (View -> Playlist). Click on the top of the playlist window. The application GUI freezes permanently. Analysis / Root Cause: By adding extensive custom tracing to dlls/comctl32/listview.c, an infinite WM_PAINT loop was identified. Here is what happens during a single iteration of the loop: WM_PAINT is dispatched, calling LISTVIEW_Refresh. LISTVIEW_Refresh sets infoPtr->bIsDrawing = TRUE and starts drawing. During the drawing process, the listview sends NM_CUSTOMDRAW (stage CDDS_PREPAINT / CDDS_ITEMPREPAINT) to the parent window (MPC-BE). The parent's custom draw handler executes logic that indirectly triggers a layout update of the listview (e.g., via SetWindowPos on the header or changing item metrics). This layout update calls LISTVIEW_UpdateSize, which eventually calls LISTVIEW_InvalidateList. LISTVIEW_InvalidateList calls LISTVIEW_InvalidateRect(infoPtr, NULL), marking the entire client area as dirty. LISTVIEW_Refresh finishes and sets infoPtr->bIsDrawing = FALSE. Because the client area was invalidated during step 6, the system immediately generates a new WM_PAINT message. The cycle repeats indefinitely. Native Windows does not freeze, suggesting it ignores invalidation requests while the control is already actively painting itself. The Fix: The LISTVIEW_INFO structure already contains the bIsDrawing flag specifically to prevent reentrancy issues. The fix is to simply return early from LISTVIEW_InvalidateList if bIsDrawing is TRUE. Since LISTVIEW_Refresh is currently repainting the entire visible area anyway, queuing another full invalidation is both redundant and dangerous. Patch / Diff diff --- a/dlls/comctl32/listview.c +++ b/dlls/comctl32/listview.c @@ -1792,6 +1792,7 @@ static inline void LISTVIEW_InvalidateList(const LISTVIEW_INFO *infoPtr) { + if (infoPtr->bIsDrawing) return; LISTVIEW_InvalidateRect(infoPtr, NULL); } -- 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.

1 8

[Bug 50888] New: FlatOut 2 shadows are red with builtin d3dx9_30
by WineHQ Bugzilla June 16, 2026

June 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=50888 Bug ID: 50888 Summary: FlatOut 2 shadows are red with builtin d3dx9_30 Product: Wine Version: 6.5 Hardware: x86-64 URL: https://www.pcworld.pl/ftp/pobierz/gry/3642.html OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 69701 --> https://bugs.winehq.org/attachment.cgi?id=69701 +d3dx wine-6.5-41-g6ca1a92684f -- 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.

2 6

[Bug 57287] New: Wayland issues
by WineHQ Bugzilla June 15, 2026

June 15, 2026

https://bugs.winehq.org/show_bug.cgi?id=57287 Bug ID: 57287 Summary: Wayland issues Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: mike(a)fireburn.co.uk Distribution: --- I'm not sure if these issues are in wine or kwin (tested with 6.1.5 & 6.2.0) Apps don't use system toolbars, this can be seen with winecfg or regedit Battle.net doesn't render anything to the screen The systray isn't integrated Launching WoW works, identifies that there are 3 screens but you can't control which is primary correctly, the default screen doesn't have the correct resolutions available, maxes out at 1920x1080 Switching to windowed mode stops any further mouse input to the game screen - keyboard entries are fine This is the first version that things have launched without crashing Everything works fine under x11, is there anything I can do to pinpoint if these are kwin bugs or not? -- 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.

2 2

[Bug 58316] New: Wine Wayland window only opens on "monitor 1" and cannot be moved
by WineHQ Bugzilla June 15, 2026

June 15, 2026

http://bugs.winehq.org/show_bug.cgi?id=58316 Bug ID: 58316 Summary: Wine Wayland window only opens on "monitor 1" and cannot be moved Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: dakky198(a)gmail.com Distribution: --- I've tested this both on Mutter and KWin. When launching a fullscreen game using Wine's Wayland drivers (by utilizing `env -u DISPLAY game.exe` the game launches on my secondary monitor no matter what you try doing. I've determined this is because my graphics drivers have that monitor set as "monitor 1". If I try to move the window to my other monitor, the window snaps back immediately to it's original position. Windowed applications also spawn only on "monitor 1" but allow themselves to be moved to another monitor. However, they retain the resolution/scaling/etc from their original position and do not update to match the new monitor. In my case, they spawn on a 1080p monitor and when moving them to 1440p the window scales to be quite small. -- 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.

2 3

[Bug 40960] New: mIRC: Skips over previous window/channel/ query when clicking the current window/channel/query icon/name.
by wine-bugs＠winehq.org June 14, 2026

June 14, 2026

https://bugs.winehq.org/show_bug.cgi?id=40960 Bug ID: 40960 Summary: mIRC: Skips over previous window/channel/query when clicking the current window/channel/query icon/name. Product: Wine Version: 1.9.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ineedalifetoday(a)live.com Distribution: --- $ wine --version wine-1.9.14 (Debian 1.9.14-1) $ sha1sum mirc745.exe 8d8c2949756dd619c9bbb5ade7a04bc24d2ee40b mirc745.exe http://www.mirc.com/get.html 1, Install mIRC 7.45 2, At end of installer, [Check] Run mIRC. 3, Click "Finish". 4, "About mIRC" window will show up. Click "Continue". Wait ~10 seconds Click "Continue". 5, "mIRC Options" Click "OK". 6, In the text box type: "//window @apple | window @baked | window @cake | window @dish" Press ENTER. This will create four windows. 7, Click "Yes" at the Command Warning. 8, In the treebar (thing on the left side of mIRC). Click the text or icon "@cake" then "@baked" then "@apple". 9, Click "@apple" again. In Windows, mIRC will go to "@baked" window as intended. Clicking the current window/channel/query icon/name you are in will take you back to the previous window. Now that you are in the "@baked" window, if you click the "@baked" window/icon again, it will take you to the "@cake" icon/window. In Wine, mIRC will go to "@baked" then jump to the "@cake" window. This is wrong. -- 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.

2 3

[Bug 59056] New: Kontakt 8: fails to install: "FALSE"
by WineHQ Bugzilla June 14, 2026

June 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=59056 Bug ID: 59056 Summary: Kontakt 8: fails to install: "FALSE" Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)list.winehq.org Reporter: mail+winehq(a)astr.cc Distribution: --- Created attachment 79824 --> http://bugs.winehq.org/attachment.cgi?id=79824 install traces for both kontakt 7 and 8 When trying to install Native Instruments' Kontakt 8 (both full and Player), the installer fails with the error "The Native Instruments Kontakt 8 Setup has failed: "FALSE". Please check your settings and try again". Kontakt 7 (Player), which uses a nearly identical installer setup (InstallAware Wizard-based), installs just fine. The Player version is free, but requires going through the Native Access download manager (which itself is annoying to get working on Wine, see AppDB): https://www.native-instruments.com/en/products/komplete/samplers/kontakt-8-… I'm working with these binaries: 73632dc3fa6ac54365ca9c3f892083598fd42c72 Kontakt 7 7.10.9 Setup PC.exe c71edf4f829dc3cbf34a92d152cccbb6092c5666 Kontakt 8 8.7.2 Setup PC.exe I've attached install logs on a fresh prefix with WINEDEBUG=+msi,+msidb,+warn for both 7 and 8 so you can look at the differences. Notably, it seems like the .msi file by Kontakt 8 extracted to C:\Windows\Installer is malformed in some way - trying to open it with msitools yields "Table size is invalid 148/3" when loading _Tables (and this is in the Wine logs as well), and real Windows agrees with this. The string pool seems to have a lot of empty(?) entries at the end (see string_totalsize traces), which for 8 is enough to push it past the 2^16 threshold in msi_save_string_table (https://gitlab.winehq.org/wine/wine/-/blob/4dfbf077cf708e4bbffa8e086d78d665…) This then makes the _Tables table fail to load. If I run the installer in a windows VM, the dropped .msi file won't have the blank entries at the end, and will install correctly (with a string pool size of ~50k rather than ~80k). I'm not sure what's causing the extra entries and whether *that's* the bug, or if it just needs to be saved differently? -- 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.

2 3

[Bug 58494] New: Panel headers not readible (application stimfit)
by WineHQ Bugzilla June 14, 2026

June 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=58494 Bug ID: 58494 Summary: Panel headers not readible (application stimfit) Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 78949 --> http://bugs.winehq.org/attachment.cgi?id=78949 Debug log when starting stimfit-lite for windows under wine. The issue is described also here: https://github.com/neurodroid/stimfit/issues/110 Some text in some panels is not visible when using wine, but its working fine on Windows. In order to reproduce the issue, you need: stimfit-lite-0.16.8-win64.exe available from here https://github.com/neurodroid/stimfit/releases/download/v0.16.8/ and some example data, e.g. download and unzip https://github.com/user-attachments/files/19322137/20250314_S5_C1_CellChar.… When starting stimfit under wine, and loading the data data, e.g. with this command, wine stimfit-lite-0.16.8-win64.exe 20250314_S5_C1_CellChar.cfs The panel headers "Trace selection", "Channel selection", "Results" are not readible. The debug log is attached. I'm testing on Debian13, with Mate desktop. -- 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.

2 5

[Bug 59740] New: Programs running under Wayland do not notice when they lose focus
by WineHQ Bugzilla June 14, 2026

June 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=59740 Bug ID: 59740 Summary: Programs running under Wayland do not notice when they lose focus Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winewayland Assignee: wine-bugs(a)list.winehq.org Reporter: winezilla(a)xobs.io Distribution: --- When running under X11, programs can use `GetForegroundWindow()` to detect if they have focus or not. This gets updated as part of `X11DRV_FocusIn()` and `focus_out()` (which is called by `X11DRV_FocusOut()`. The X11 code works by setting the foreground window to the desktop when this happens: /* Abey : 6-Oct-99. Check again if the focus out window is the Foreground window, because in most cases the messages sent above must have already changed the foreground window, in which case we don't have to change the foreground window to 0 */ if (hwnd == NtUserGetForegroundWindow()) { TRACE( "lost focus, setting fg to desktop\n" ); NtUserSetForegroundWindowInternal( NtUserGetDesktopWindow() ); } The Wayland driver has no such check, and as a result programs don't notice they are not the foreground window any more. Instead, the function `keyboard_handle_leave()` has this comment: /* FIXME: update foreground window as well */ -- 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.

1 2

[Bug 59621] New: "There is not enough video memory to open this frame editor..." error message (in Construct Classic r2)
by WineHQ Bugzilla June 13, 2026

June 13, 2026

http://bugs.winehq.org/show_bug.cgi?id=59621 Bug ID: 59621 Summary: "There is not enough video memory to open this frame editor..." error message (in Construct Classic r2) Product: Wine Version: 11.6 Hardware: x86-64 URL: https://sourceforge.net/projects/construct/files/lates t/download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: gsw.eugeneulan(a)gmail.com Distribution: Mint Created attachment 80687 --> http://bugs.winehq.org/attachment.cgi?id=80687 Crash log When you try to open/create any Construct Classic's project in Linux Mint 22.3 through the latest Wine, the error message appears that tells: "There is not enough video memory to open this frame editor. Please close some other editors and try again." And after closing it, the program crashes with the log attached in this report. In Kubuntu 25.10 I was not being able to reproduce this crash - any project opens successfully for editing. To reproduce the issue, download the latest ever Construct Classic installer from this direct official link and run the installer in default Wine prefix and follow through all wizard's steps: https://sourceforge.net/projects/construct/files/latest/download SHA-256: 4a37a020a692342e2fbec1a63927a42abefc984b474730227c20311f6e256bfe Ignore the other errors during installation and program's first run, like failed dxwebsetup.exe execution and ID3.csx plugin error - they're happening on Kubuntu for me as well. On firewall prompt you can say No, then create a new project by clicking on File in the top-left corner, select New with any of the two options after it (application / Direct-X game) - then the mentioned error will appear with crash after it. -- 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.

1 6

[Bug 54436] New: wine-staging-8.0 regression (not working): Command & Conquer 3: Tiberium Wars Kane's Wrath
by WineHQ Bugzilla June 13, 2026

June 13, 2026

https://bugs.winehq.org/show_bug.cgi?id=54436 Bug ID: 54436 Summary: wine-staging-8.0 regression (not working): Command & Conquer 3: Tiberium Wars Kane's Wrath Product: Wine-staging Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73981 --> https://bugs.winehq.org/attachment.cgi?id=73981 wine-staging-8.0: left is fine, right is broken With wine-staging-7.0 "Command & Conquer 3: Tiberium Wars Kane's Wrath" was working fine. In wine-8.0 and wine-staging-8.0 it's broken. With wine-staging-8.0 the menu looks broken. See attached screenshot. (left is fine, right is broken) With wine-8.0 the menu loads, but starting a skirmish game crashes the application. There's an error dialog window saying: Direct3D error 0x8007000e (E_OUTOFMEMORY) -- 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.

2 34