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

[Bug 60106] New: Flash Player 10.3.183.7 installer window never appears
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=60106 Bug ID: 60106 Summary: Flash Player 10.3.183.7 installer window never appears Product: Wine Version: 11.14 Hardware: x86-64 URL: https://www.oldversion.com/windows/macromedia-flash-pl ayer/macromedia-flash-player-10-3-183-7-ie/ OS: Linux Status: NEW Keywords: download, Installer Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: imwellcushtymelike(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81657 --> http://bugs.winehq.org/attachment.cgi?id=81657 Wine 11.14 console output The installer for Flash Player 10.3.183.7 never appears under Wine, but works fine under Windows 10, albeit useless in the end. I tried a number of native DLLs to work around missing functions but the best result I got was an error window about a script, wherein choosing either Yes or No to continue appears to make no difference. WINEDLLOVERRIDES=ieframe,iertutil,mshtml,msls31,shdoclc,shdocvw,urlmon=n I tried a Frankenstein mixture of DLLs from IE4, 6, 7 and 8 before giving up and installing IE8 completely, which is a workaround. With the workaround the window shows, but hits another bug. sha1sum: 5245aceea5e0d78b42c65c3fe0c402e244761217 install_flashplayer10ax_aih_10.3.183.7.exe -- 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 18715] New: No statusbar in Notepad
by wine-bugs＠winehq.org Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=18715 Summary: No statusbar in Notepad Product: Wine Version: 1.1.22 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: Eldmannen+wine(a)gmail.com The Notepad that comes with Wine has no statusbar. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

3 10

[Bug 60083] New: Allow relative WINEPREFIX location
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=60083 Bug ID: 60083 Summary: Allow relative WINEPREFIX location Product: Wine Version: 11.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: EpicTux123(a)proton.me Target Milestone: --- Distribution: --- When using something such as $ WINEPREFIX="./wine/" wine app.exe (with or without quotes, same result) Wine complains it is not an absolute path. Make it so it works with relative paths such as using . or .. (at least . which is very useful). Thanks. -- 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 21278] New: python's test_zipimport_support test fails
by wine-bugs＠winehq.org Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=21278 Summary: python's test_zipimport_support test fails Product: Wine Version: 1.1.35 Platform: x86 URL: http://www.python.org OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=25590) --> (http://bugs.winehq.org/attachment.cgi?id=25590) test output Install python and run: wine 'c:\Python31\python.exe' -m test.test_zipimport_support test_doctest_main_issue4197 (__main__.ZipSupportTests) ... Expected line File "C:\windows\temp\tmppzq0bh\script.py", line 2, in __main__.Test Got stdout: ********************************************************************** File "C:\windows\temp\tmppzq0bh\script.py", line 2, in __main__.Test Failed example: 'line 2' Expected nothing Got: 'line 2' Full output attached. Vincent wrote in the wiki that somehow a 'C:' was changed to a 'c:'. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 8

[Bug 59927] New: win32u: SystemParametersInfo returns failure for SPI_SETSTICKYKEYS/SPI_SETFILTERKEYS (MapleStory launch)
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=59927 Bug ID: 59927 Summary: win32u: SystemParametersInfo returns failure for SPI_SETSTICKYKEYS/SPI_SETFILTERKEYS (MapleStory launch) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: win32u Assignee: wine-bugs(a)list.winehq.org Reporter: f0rm4tm3(a)gmail.com Distribution: --- MapleStory (Steam app 216150) calls SystemParametersInfo with SPI_SETSTICKYKEYS and SPI_SETFILTERKEYS at launch to disable those accessibility features. In Wine, both SET actions are only stubbed through WINE_SPI_FIXME (dlls/win32u/sysparams.c), which logs and returns failure. The failed calls contribute to the game failing to launch. The corresponding GET actions (SPI_GETSTICKYKEYS, SPI_GETFILTERKEYS) are implemented (return zeroed structs + success), but the SET actions are not. Suggested fix: switch the two stubs from WINE_SPI_FIXME to WINE_SPI_WARN, which logs and returns success — matching how Wine already handles other unimplemented SET actions such as SPI_SETANIMATION and SPI_LANGDRIVER. The settings are not actually applied (Wine has no host accessibility integration on this path), only accepted. Patch attached. Reproduce: 1. Steam -> MapleStory (216150) under any recent Wine/Proton. 2. Launch -> the accessibility SPI calls fail; contributes to the launch failure. (See also bug 59926 for the related kernelbase CharPrevExA NULL-deref crash that also blocks MapleStory launch.) -- 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 4

[Bug 56739] New: Alchemy is rotated 90°
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=56739 Bug ID: 56739 Summary: Alchemy is rotated 90° Product: Wine Version: 9.8 Hardware: x86-64 URL: https://alchemy.software.informer.com/download/ OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: zzhang(a)codeweavers.com Regression SHA1: 4a330b29212402b9700828be82939112bd11a786 Distribution: Ubuntu Created attachment 76518 --> https://bugs.winehq.org/attachment.cgi?id=76518 Screenshot The game Alchemy is rotated 90°. A bisect points to: 4a330b29212402b9700828be82939112bd11a786 is the first bad commit commit 4a330b29212402b9700828be82939112bd11a786 Author: Zhiyi Zhang Date: Tue Sep 22 15:02:24 2020 +0800 winex11.drv: Support display orientations for XRandR 1.4 display settings handler. Running in an emulated desktop works around this. https://alchemy.software.informer.com/download/ $ sha1sum alchemysetup-en.exe 2fa2bd427e79b7fb585d090891ae368b0cea0156 alchemysetup-en.exe $ xrandr --version xrandr program version 1.5.1 Server reports RandR version 1.6 -- 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 9

[Bug 60104] New: ws2_32: socket readiness notifications (WSAIoctl IOC_VENDOR 210 / ProcessSocketNotifications) unimplemented: World of Warcraft 12.x login takes minutes (30s timeout per round-trip)
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=60104 Bug ID: 60104 Summary: ws2_32: socket readiness notifications (WSAIoctl IOC_VENDOR 210 / ProcessSocketNotifications) unimplemented: World of Warcraft 12.x login takes minutes (30s timeout per round-trip) Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)list.winehq.org Reporter: renatoiwa(a)gmail.com Target Milestone: --- Distribution: --- Created attachment 81653 --> http://bugs.winehq.org/attachment.cgi?id=81653 unimplemented ioctl trace Product: Wine Component: winsock Version: 11.0 (observed under Proton Experimental; Wine 11.0 per game's gx.log) Severity: normal Hardware/OS: x86_64 / Linux 7.1.5-arch1-2 --- Description --- World of Warcraft retail 12.x ("Midnight") introduced a new network layer (Blizzard "bsSocket", also used by the Battle.net launcher) that registers each socket for readiness notifications via: WSAIoctl(s, _WSAIOR(IOC_VENDOR, 210), ...) -> NtDeviceIoControlFile AFD ioctl 0x120348 Wine logs: fixme:winsock:WSAIoctl unimplemented ioctl _WSAIOR(IOC_VENDOR, 210) fixme:winsock:server_ioctl_sock Unsupported ioctl 0x120348 (device=0x12 access=0 func=0xd2 method=0) This appears to be the Windows 10 2004+ "Winsock socket state notifications" mechanism (ProcessSocketNotifications / SOCK_NOTIFY_REGISTRATION, completion-port based: https://learn.microsoft.com/en-us/windows/win32/winsock/winsock-socket-stat…) ws2_32.spec does not export ProcessSocketNotifications, and the AFD ioctl is rejected. Effect: the game ignores the registration failure. Its network worker threads then block on event waits expecting readiness notifications that are never posted, and every request/response step of the Battle.net login protocol only advances when a ~30 s fallback timeout fires. A login needs 3–5 round-trips → the "Connecting..." screen takes 1.5–3 minutes (and "Retrieving realm list" another 30 s). On Windows the same login is instant. Gameplay after login is unaffected (world-server connection is serviced by a different code path). --- Evidence --- 1) Server replies arrive immediately and sit unread in the socket receive queue (ss -tanpoe sampled ~1/s while stuck on "Connecting..."): auth socket (us.actual.battle.net:1119): 187 bytes arrive 07:53:59.9, drained 07:54:29.5 (~29.6 s later); next step identical. The client's own Connection.log shows protocol steps quantized to EXACTLY 30.000 s (e.g. "OnSendLogon" -> "Logon complete" = 30.000 s to the millisecond). 2) WINEDEBUG=+timestamp,+winsock trace during one such stall (attachment trace-2-30s-stall-socket-0xb24.txt): the auth socket (handle 0xb24) has no WSAEventSelect, no overlapped I/O, and no blocking select() spanning the stall. The recv thread does a non-blocking WS2_recv_base -> STATUS_DEVICE_NOT_READY (data arrived 1.2 s later), then ALL connection threads are completely winsock-silent for ~30 s (parked in NtWaitForMultipleObjects), wake on timeout, and a blind recv drains the queued reply. Sends still work mid-stall. 3) The registration attempt (attachment trace-1-unimplemented-ioctl.txt) is issued at socket-layer init and per-socket by both WoW.exe and Battle.net.exe. 4) Differential inside the same process: logging in by typing credentials at the WoW login screen (which authenticates through a different, non-notification code path) completes the same :1119 auth conversation in ~6 s with the receive queue empty in every sample. Only the launcher-token flow, which depends on the notification mechanism, exhibits the 30 s-per-step behavior. --- Notes for implementation --- A stub returning success would make things worse (the app would still never receive notifications and lose even its current fallback behavior); the mechanism needs actual registration bookkeeping and completion-port posting (readiness events analogous to epoll edge notifications) in wineserver. Reproduction: Battle.net launcher (non-Steam app under Proton or plain Wine) → install World of Warcraft retail 12.x → click Play → observe "Connecting..." for 1–3 minutes, with `ss -tan` on the host showing bytes parked in Recv-Q on the :1119/:443 connections, and the fixmes above in the log. -- 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 0

[Bug 60103] New: Bookworm Deluxe will not install from CD
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=60103 Bug ID: 60103 Summary: Bookworm Deluxe will not install from CD Product: Wine Version: 11.14 Hardware: x86-64 URL: https://archive.org/details/BookwormDeluxe_201901 OS: Linux Status: NEW Keywords: download, Installer, obfuscation Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: imwellcushtymelike(a)gmail.com Target Milestone: --- Distribution: Ubuntu Created attachment 81651 --> http://bugs.winehq.org/attachment.cgi?id=81651 Wine 11.14 console output The installer for Bookworm Deluxe appears to hang near the end. A process named cdprotect.exe runs at 100% CPU, but nothing further happens and it has to be killed. Same with Staging. I tried attaching strace to it but it gave me nothing. The game appears to be installed, but it doesn't do anything useful. Just hangs around in the background like cdprotect.exe. -- 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 5

[Bug 60090] New: Bug list needs fixing
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

http://bugs.winehq.org/show_bug.cgi?id=60090 Bug ID: 60090 Summary: Bug list needs fixing Product: WineHQ Apps Database Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)list.winehq.org Reporter: imwellcushtymelike(a)gmail.com Target Milestone: --- Distribution: --- Before the separation of the databases, the bug list on an app's page was much simpler and neater. It now lists superfluous details. Currently: ID Summary Status App Name App Version Has Maintainer Other apps affected Delete Edit Previously (from memory): ID Summary Status Other apps affected Delete Accept (A tick icon) The "Accept" was a much quicker way to accept bug links than going through the common replies. -- 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 55958] New: [Debian-based]　wiki.winehq.org/Regression_Testing - instructions do not work on modern distros
by WineHQ Bugzilla Aug. 1, 2026

Aug. 1, 2026

https://bugs.winehq.org/show_bug.cgi?id=55958 Bug ID: 55958 Summary: [Debian-based]　wiki.winehq.org/Regression_Testing - instructions do not work on modern distros Product: WineHQ.org Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: NM64+bugs.winehq.org(a)PM.me Distribution: --- Created attachment 75550 --> https://bugs.winehq.org/attachment.cgi?id=75550 video demonstration on Linux Mint 21.2 The instructions provided on wiki.winehq.org/Regreesion_Testing for Debian-based distros seem to not be functional on modern Debian-based distros. See the attached video for a demonstration on the live ISO of Linux Mint 21.2 Cinnamon (and, while not shown in the video, I get the exact same result when trying this on an actual installation of Linux Mint 21.2 rather than using a live ISO session) -- 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 10