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

[Bug 48078] New: Astro Avenger 2 fails to run with seh:setup_exception_record stack overflow
by WineHQ Bugzilla Sept. 18, 2026

Sept. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=48078 Bug ID: 48078 Summary: Astro Avenger 2 fails to run with seh:setup_exception_record stack overflow Product: Wine Version: 4.19 Hardware: x86-64 URL: https://astro-avenger.en.softonic.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iodreamify(a)gmail.com Distribution: Ubuntu Created attachment 65628 --> https://bugs.winehq.org/attachment.cgi?id=65628 winedebug warn+all log Astro Avenger 2 manages to launch but clicking "Run" in the launcher makes the game freeze forever with a "002a:err:seh:setup_exception_record stack overflow 816 bytes in thread 002a eip 00ac1926 esp 00231000 stack 0x230000-0x231000-0x330000" error. Tried it both in 64bit and 32bit prefixes in windows 7, XP, 2000 and 98 modes and also disabling csmt.I've added a winedebug=warn+all log below. A demo 60 min trial can be found at the link above. I've also done a +relay log but i'm not sure if it's relevant. 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.

2 6

[Bug 52621] New: Failed test of `alternate_success_code` from `windows-rs`
by WineHQ Bugzilla Sept. 18, 2026

Sept. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=52621 Bug ID: 52621 Summary: Failed test of `alternate_success_code` from `windows-rs` Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- This test pass on Windows 10 Failures ``` running 1 test test test ... FAILED failures: ---- test stdout ---- thread 'test' panicked at 'assertion failed: hr == CO_E_NOTINITIALIZED', crates\tests\alternate_success_c ode\tests\test.rs:9:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace failures: test ``` Rust for Windows can be installed via https://forge.rust-lang.org/infra/other-installation-methods.html or directly https://static.rust-lang.org/dist/rust-1.59.0-x86_64-pc-windows-gnu.msi Steps to reproduce git clone https://github.com/microsoft/windows-rs.git cd windows-rs git checkout 9965e3c44829d0c86b2d9d2b3c5338376f158bde cd crates/tests/alternate_success_code/ wine cargo test -- 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 52620] New: Failed test of `win32_arrays` from `windows-rs`
by WineHQ Bugzilla Sept. 18, 2026

Sept. 18, 2026

https://bugs.winehq.org/show_bug.cgi?id=52620 Bug ID: 52620 Summary: Failed test of `win32_arrays` from `windows-rs` Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- This test pass on Windows 10 Failures ``` failures: ---- keyboard_state stdout ---- thread 'keyboard_state' panicked at 'assertion failed: state != zeroed', crates\tests\win32_arrays\tests\ fixed.rs:9:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ---- temp_file stdout ---- thread 'temp_file' panicked at 'assertion failed: `(left == right)` left: `[46, 92, 116, 101, 115, 55, 98, 46, 116, 109, 112, 0]`, right: `[46, 92, 116, 101, 115, 55, 66, 46, 116, 109, 112, 0]`', crates\tests\win32_arrays\tests\fixed.r s:20:9 failures: keyboard_state temp_file ``` Rust for Windows can be installed via https://forge.rust-lang.org/infra/other-installation-methods.html or directly https://static.rust-lang.org/dist/rust-1.59.0-x86_64-pc-windows-gnu.msi Steps to reproduce git clone https://github.com/microsoft/windows-rs.git cd windows-rs cd crates/tests/win32_arrays/ wine cargo test -- 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 53795] New: Emojis crash Naver LINE (and possibly all Qt applications)
by WineHQ Bugzilla Sept. 17, 2026

Sept. 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=53795 Bug ID: 53795 Summary: Emojis crash Naver LINE (and possibly all Qt applications) Product: Wine Version: 7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: pq2sx44teeigl7za(a)chyen.cc Distribution: --- Created attachment 73289 --> https://bugs.winehq.org/attachment.cgi?id=73289 Source of a trivial Qt application to reproduce the issue Naver LINE (installer at [1]) crashes if I paste some kinds of emojis, like ???? (U+1F972) or ???? (U+1F970). Crashes happen with all kinds of text boxes, including username in the login dialog, search box and messaging dialog. Crash does not happen if I uninstalled the Noto Color Emoji font [2]. Without WINEDEBUG, crashes are intermittent. With WINEDEBUG=+font, I always get crashes. The issue can be reproduced with a trivial Qt application (source attached). The backtrace from a Qt 5.12.12 MinGW debug build [3] is also attached. >From the backtrace, Qt crashes when trying to get the string from otm->otmpFullName [4]. In a gdb session, the address (otm + otm->otmpFullName) points to an invalid address (needs to add otm per [5]). Apparently GetOutlineTextMetrics does not correctly assign that pointer. [1] https://desktop.line-scdn.net/win/new/LineInst.exe [2] https://archlinux.org/packages/extra/any/noto-fonts-emoji/ [3] https://download.qt.io/archive/qt/5.12/5.12.12/qt-opensource-windows-x86-5.… [4] https://github.com/qt/qtbase/blob/v5.12.12/src/platformsupport/fontdatabase… [5] https://learn.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-outlin… -- 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 51443] New: Test fails in remove_dir_all crate when creating file
by WineHQ Bugzilla Sept. 17, 2026

Sept. 17, 2026

https://bugs.winehq.org/show_bug.cgi?id=51443 Bug ID: 51443 Summary: Test fails in remove_dir_all crate when creating file Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Hi, Steps to reproduce on clear wine-devel 6.12 ``` wget https://static.rust-lang.org/dist/rust-1.53.0-x86_64-pc-windows-gnu.msi msiexec /i rust-1.53.0-x86_64-pc-windows-gnu.msi git clone https://github.com/XAMPPRocky/remove_dir_all.git cd remove_dir_all git checkout 9b164cecdb4a0590af68be8b22f9c747402237e3 wine cargo test ``` should print this ``` running 4 tests test removes_read_only ... FAILED test removes_empty ... ok test removes_files ... ok test removes_dirs ... ok failures: ---- removes_read_only stdout ---- thread 'removes_read_only' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 5, kind: PermissionDenied, message: "Access denied." }', tests\windows.rs:68:49 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace failures: removes_read_only test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s error: test failed, to rerun pass '--test windows' ``` I tested it and this works fine in Windows Server 2019 Source code of failed test - https://github.com/XAMPPRocky/remove_dir_all/blob/9b164cecdb4a0590af68be8b2… ``` fn removes_read_only() { env_logger::init(); for i in 0..5 { let path = format!("./readonly/{}/subdir", i); fs::create_dir_all(&path).unwrap(); let file_path = format!("{}/file.txt", path); { let file = File::create(&file_path).unwrap(); ``` -- 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 33126] New: divided SysEx and coalesced midiOutLongMsg
by wine-bugs＠winehq.org Sept. 16, 2026

Sept. 16, 2026

http://bugs.winehq.org/show_bug.cgi?id=33126 Bug #: 33126 Summary: divided SysEx and coalesced midiOutLongMsg Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: winealsa.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net Classification: Unclassified Johannes Kroll reported in wine-patches that the KORG Kontrol Editor software hung after sending an ill-formed SysEx via winealsa's midiOutLongMsg. http://www.winehq.org/pipermail/wine-patches/2013-January/121335.html The MIDIHDR data is F0 ... F7 00 00 00 (125 bytes). http://www.winehq.org/pipermail/wine-devel/2013-February/098852.html He observed that no hang occurs when skipping the trailing 3 zero bytes. F7 is the "End Of SysEx" (EOX) marker. It is still unclear what happens. MIDI HW is expected to skip over bogus bytes, thus the zero bytes should cause no harm. OTOH, ALSA might be getting into trouble processing ill-formed messages, and we don't know if or how many bytes ALSA actually sent out through the serial port. In any case, midiOutLongMsg handling in Wine needs fixes. - winealsa should extract the F0...F7 part and send that as a SysEx. - More generally, midiOutLong is known to accept not only SysEx packets, but also coalesced status messages. Some MIDI authors prefer to send e.g. chords via one LongMsg rather than successive calls to midiOutShortMsg, arguing that it's faster. Hence all Wine MIDI drivers need to decompose midiOutLongMsg into packets consisting of status message, regular SysEx ... and possibly junk. - All APIs (MS, ALSA, OSS, CA) acknowledge the existence of divided SysEx. As a result, framing SysEx with F0 ... F7 is entirely under application control. The current winealsa framing code is simply wrong. - winecoreaudio always declared 3 bytes for short messages, even program change. I have written a sequence of patches to fix all of this. The only thing that is unclear is how to encapsulate garbage data like the above 3 zero bytes or real time messages with ALSA. What ALSA API function and what ALSA message type to use? Heck, I'm not even sure winealsa.drv/midi.c:modData is ok to send a 2-byte MTC quarter frame via snd_seq_ev_set_sysex instead of using a primitive that sets the type SND_SEQ_EVENT_CLOCK/TICK. -- 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 5

[Bug 56043] New: Native Wayland Touchpad scroll doesn't work
by WineHQ Bugzilla Sept. 16, 2026

Sept. 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=56043 Bug ID: 56043 Summary: Native Wayland Touchpad scroll doesn't work Product: Wine Version: 9.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: capybaraserene(a)gmail.com Distribution: --- Native Wayland is working almost perfect for several of my apps for the first time. Great job! It's almost perfect now except touchpad scrolling doesn't work. WineHQ: wine-devel64-9.0.rc2-1.1.x86_64 Fedora 39 GNOME Wayland XWayland: Touchpad scroll works =============================== * DISPLAY=:0 * wine explorer.exe * two finger scroll works Native Wayland: Touchpad scroll doesn't work ============================================ * regedit HKEY_CURRENT_USER\Software\Wine\Drivers\Graphics x11,wayland * unset DISPLAY * wine explorer.exe * two finger scroll doesn't work -- 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 55705] New: PDF Xchange editor crashes
by WineHQ Bugzilla Sept. 16, 2026

Sept. 16, 2026

https://bugs.winehq.org/show_bug.cgi?id=55705 Bug ID: 55705 Summary: PDF Xchange editor crashes Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donescamillo(a)gmail.com Distribution: --- Wine 8.17 development branch. PdfXchange Editor free version i.e. not registered version. portable, version 10.0.1.371 Linux Mint 21.2 PdfXchange editor works OK, can highlight, add labels, images, whatever the free version allows. The problem is that after some time, when PdfXchange Editor is being closed, it hangs, and the dialog asking for forcing the application to close appears. This happens in previous versions, too. -- 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 21

[Bug 46871] New: err:rpc: rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87
by wine-bugs＠winehq.org Sept. 15, 2026

Sept. 15, 2026

https://bugs.winehq.org/show_bug.cgi?id=46871 Bug ID: 46871 Summary: err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87 Product: Wine Version: 4.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)earthlink.net Distribution: --- Created attachment 63932 --> https://bugs.winehq.org/attachment.cgi?id=63932 NaturallySpeaking 13 setup log When installing Dragon NaturallySpeaking 13, the installation hangs up right at the last instruction. A prior bug 46160 was filed about NatSpeak 13 hanging up at the end of installation, and I think that bug might have been fixed in the most recent wine version, and this other bug uncovered. bug 46160 Anyway, the installation stops as of this: err:rpc:rpcrt4_protseq_np_wait_for_new_connection wait failed with error 87 I have posted the installation log. If I kill the installation and then try to start the program, the program works up to a point. It waves hello, and then asks if I want to register the program immediately or run it up to 5 times without registering. When I hit either of these options, the program crashes. I have included the crash log also. -- 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 13

[Bug 59737] New: IME/VK_PROCESSKEY path loses scan code in follow-up WM_KEYDOWN under Chinese HKL
by WineHQ Bugzilla Sept. 14, 2026

Sept. 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=59737 Bug ID: 59737 Summary: IME/VK_PROCESSKEY path loses scan code in follow-up WM_KEYDOWN under Chinese HKL Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: user32 Assignee: wine-bugs(a)list.winehq.org Reporter: ax+3lzp806u(a)fxzx.ident.com.es Distribution: --- ### Summary When Wine runs under a Chinese locale / Chinese HKL (`00000804`), or after a Chinese IME path is activated, normal key presses are delivered through a `VK_PROCESSKEY` path. The initial `VK_PROCESSKEY` message contains the correct scan code in `lParam`, but the following real `WM_KEYDOWN` message for the actual key, such as `VK_W` or `VK_BACK`, has scan code `0`. This breaks games and engines that rely on scan codes for keyboard input or key binding. ### Environment * Affected HKL: Chinese layout, `00000804` * Working HKL: US layout, `00000409` The runtime XKB map appears normal: ```text key <BKSP> { [ BackSpace, BackSpace ] }; key <AD02> { type= "ALPHABETIC", symbols[Group1]= [ w, W ] }; ``` So this does not appear to be caused by a broken XKB layout. ### Steps to reproduce 1. Run Wine under a Chinese locale, or use a session where Wine selects Chinese HKL `00000804`. 2. Start an affected game or test program that logs Windows keyboard messages. 3. Press normal keys such as `W` or `Backspace`. 4. Observe the generated `WM_KEYDOWN` messages and their `lParam` scan-code bits. The problem may also appear after a Chinese IME / input method is activated during the same Wine session. ### Actual behavior Wine reports Chinese keyboard layout: ```text NtUserGetKeyboardLayoutName ret L"00000804" layout 0x8040804 Default IME Wine IME WM_IME_NOTIFY ``` Pressing `W` produces: ```text WM_KEYDOWN wp=000000e5 lp=00110001 # VK_PROCESSKEY, scan code = 0x11 WM_KEYDOWN wp=00000057 lp=00000011 # VK_W, scan code = 0 WM_CHAR wp=00000077 lp=00000011 WM_KEYUP wp=000000e5 lp=c0110001 WM_KEYUP wp=00000057 lp=0000c011 ``` Pressing `Backspace` produces: ```text WM_KEYDOWN wp=000000e5 lp=000e0001 # VK_PROCESSKEY, scan code = 0x0e WM_KEYDOWN wp=00000008 lp=0000000e # VK_BACK, scan code = 0 WM_CHAR wp=00000008 lp=0000000e WM_KEYUP wp=000000e5 lp=c00e0001 WM_KEYUP wp=00000008 lp=0000c00e ``` The scan code is present on the `VK_PROCESSKEY` message, but is lost in the follow-up real key message. ### Expected behavior When Wine sends the final real key message after IME processing, the scan code in `lParam` should be preserved. Expected examples: ```text WM_KEYDOWN VK_W lp=00110001 WM_KEYDOWN VK_BACK lp=000e0001 ``` The real key message should not have scan code `0`. ### Working case When Wine is launched with an English locale: ```sh LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 wine <app> ``` Wine uses US layout: ```text NtUserGetKeyboardLayoutName ret L"00000409" ``` No `VK_PROCESSKEY` message is generated, and scan codes are correct. For `W`: ```text WM_KEYDOWN dispatched wp=00000057 lp=00110001 WM_KEYUP dispatched wp=00000057 lp=c0110001 ``` For `Backspace`: ```text WM_KEYDOWN dispatched wp=00000008 lp=000e0001 WM_CHAR dispatched wp=00000008 lp=000e0001 WM_KEYUP dispatched wp=00000008 lp=c00e0001 ``` ### Additional observation The issue can reappear after a Chinese IME/input method is activated inside the session. Before IME activation, keyboard input may work normally. After the IME appears or composition is activated, affected games may start receiving real key messages with scan code `0`. This suggests the issue is likely in Wine's IME / `VK_PROCESSKEY` handling path, not only in initial locale selection. ### Impact Games and engines that depend on scan codes for keyboard input or key binding ignore affected keys. Observed symptoms include: * `W` is not recognized unless pressed as `Alt+W`. * `Backspace` is ignored in some games. * Plain letter keys may fail in some games. * The problem disappears when Wine is launched with an English locale. `Alt+W` works because it goes through the system-key path and receives a correct scan code: ```text WM_SYSKEYDOWN wp=00000012 lp=20380001 # Alt WM_SYSKEYDOWN wp=00000057 lp=20110001 # W, scan code = 0x11 ``` ### Workaround Launching Wine with an English locale avoids the problem: ```sh LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 XMODIFIERS=@im=none wine <app> ``` ### Suspected cause Wine appears to construct the follow-up real `WM_KEYDOWN` message incorrectly after `VK_PROCESSKEY` handling. The correct scan code is available in the `VK_PROCESSKEY` message, but is not preserved in bits 16–23 of `lParam` for the real key message. -- 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