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

[Bug 59952] New: Support an environment variable disable for user mode dispatch!

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59952 Bug ID: 59952 Summary: Support an environment variable disable for user mode dispatch! 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: timothylottes(a)protonmail.com Distribution: --- The old way to work around problems in Wine on Linux was to do direct Linux system calls from inside the WIN32 application using inline assembly. However now with user mode dispatch, those SYSCALL instructions get trapped. This makes it impossible to implement in-app workarounds for Wine bugs. The request here is an environment variable that can be set before execution of "wine" that would disable use of userr-mode-dispatch, so that it restores ability to do Linux system calls instead. -- 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.

July 2, 2026

[Bug 59745] Wine crashes when a custom window is created to show information

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59745 --- Comment #9 from Matthias Zorn <matthias0178+wine(a)gmail.com> --- (In reply to Maotong Zhang from comment #8) > (In reply to Matthias Zorn from comment #5) > > I’ve tested your bug fix with Wine 11.12. The program no longer crashes on > > Linux. However, there is a slight difference in the console output, which > > can be seen when comparing the screenshots. > > Would missing a WM_ACTIVATE message affect your “special window program”? The window can be closed in Debian just as it is in Windows 11. Exception: If you click on the Debian taskbar (LXPanel 0.11.1), the Wine program will only detect this if another window is brought to the foreground. -- 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.

July 2, 2026

[Bug 59951] Missing i386-part of wine-11.11 and wine-11.12 Debian bookworm packages

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59951 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Rosanne DiMesio <dimesio(a)earthlink.net> --- The 11.11 i386 bookworm package did fail due to the gcc bug, but since Debian 12 is EOL and those would have been the last packages for it anyway, I did not pursue it any further. My mistake was in not remembering to purge the amd64 part from the OBS, so they got synced over with everything else. 11.10 are the last working packages here for Debian 12. -- 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.

July 1, 2026

[Bug 59550] Implement AppDefaults registry toggle for wcmd to sanitize forward slashes in execution paths (Resolves Unreal Engine update scripts)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59550 --- Comment #7 from smcclenahan(a)gmail.com --- Created attachment 81325 --> http://bugs.winehq.org/attachment.cgi?id=81325 GbxRelaunch log As requested an excerpt from the cxlog file with recommended Wine log settings. -- 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.

July 1, 2026

[Bug 59951] New: Missing i386-part of wine-11.11 and wine-11.12 Debian bookworm packages

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59951 Bug ID: 59951 Summary: Missing i386-part of wine-11.11 and wine-11.12 Debian bookworm packages Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)list.winehq.org Reporter: bernhardu(a)mailbox.org CC: dimesio(a)earthlink.net Distribution: --- In https://dl.winehq.org/wine-builds/debian/pool/main/w/wine/ are currently only the amd64 packages of wine-11.11 and wine-11.12. Bug #59928 may be a possible reason why the build could have failed? -- 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.

July 1, 2026

[Bug 59928] Std 32-bit build fails with "../wine/dlls/oleaut32/vartype.c:3000:1: internal compiler error"

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59928 --- Comment #10 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- (In reply to Rafał Mużyło from comment #9) > > As Bernhard stated he was able to reproduce the problem and kindly provided version information you asked for. > > Actually, he didn't. I mean, if I were familiar with that distro, that could > have meant something, but I'm not. We could assume he meant 'the tools as > provided by a standard install of that distro's version', but that would be > just an assumption. I thought I did ;-) I wrote "I get a simlar crash" but didn't put all information in the comment because it wasn't my bug and it was not yet clear if Renzo was using gcc or gcc-mingw because the callstack was a little different. And the attached file contains full command line and the version how the compiler identifies itself and the version from the package management. From that link [2] it may be possible that gcc-mingw 12.3 already fixed this issue. I wonder if this gcc-mingw bug could be the reason why no official bookworm 32-bit packages appear in the download directory [1], the last 32-bit package is wine-devel-i386_11.10~bookworm-1_i386.deb? [1] https://dl.winehq.org/wine-builds/debian/pool/main/w/wine/ [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111107#c13 -- 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.

July 1, 2026

[Bug 59944] BOINC's project dialog is messed up

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59944 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|48bb5d586467895c329b840ed95 | |40525edf3b422 | --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- I don't think that's it either, I'm seeing the same issue in Wine 10.17, which is before the mentioned commit. I'm not convinced that this is actually a regression. -- 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.

July 1, 2026

[Bug 58922] Mouse cursor invisible in WebView2 browser

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58922 theonetheonlydan2004(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |theonetheonlydan2004@gmail. | |com --- Comment #2 from theonetheonlydan2004(a)gmail.com --- Having the exact same issue. The mouse isn't drawn on apps requiring WebView2, even after installing it from the "Evergreen Standalone Installer." -- 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.

July 1, 2026

[Bug 59944] BOINC's project dialog is messed up

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59944 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|ntdll |tools -- 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.

July 1, 2026

[Bug 59944] BOINC's project dialog is messed up

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59944 --- Comment #7 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- > 48bb5d586467895c329b840ed9540525edf3b422 — Bug Just for clarity: I'm not saying Bug 48, that seems to be a Bugzilla issue. -- 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.

July 1, 2026