- Wine-Bugs - list.winehq.org

[Bug 57258] New: MailWasher renders dropdown as black
by WineHQ Bugzilla May 9, 2026

May 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=57258 Bug ID: 57258 Summary: MailWasher renders dropdown as black Product: Wine Version: 9.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 77174 --> https://bugs.winehq.org/attachment.cgi?id=77174 Screenshot To Test: - Install the program - Start the program, ignore the crash with esent.dll.JetCreateInstance - Click Next, enter a dummy "Account description", click next - When clicking the dropdown for "Server Type" the contents are completely black -- 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 56978] New: Keyboard Inspector 1.0: No keyboard input is detected
by WineHQ Bugzilla May 9, 2026

May 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=56978 Bug ID: 56978 Summary: Keyboard Inspector 1.0: No keyboard input is detected Product: Wine Version: 9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kotrigmd(a)gmail.com Distribution: ArchLinux Program download: https://github.com/mat1jaczyyy/Keyboard-Inspector/releases Version 1.0 of Keyboard Inspector uses raw input in combination with an IMessageFilter to detect key presses/releases. After pressing "Start Recording", pressing several keys, and then pressing "Stop Recording", no data is displayed. Keyboard input is detected perfectly fine on native Windows. Version 0.4 relies on WH_KEYBOARD_LL instead, and works without issue on both Linux and native Windows. -- 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 56964] New: error in paint.net
by WineHQ Bugzilla May 9, 2026

May 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=56964 Bug ID: 56964 Summary: error in paint.net Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d-util Assignee: wine-bugs(a)winehq.org Reporter: grandrodri3(a)gmail.com Distribution: --- Created attachment 76787 --> https://bugs.winehq.org/attachment.cgi?id=76787 paint.net installer error (only .net 7) Hello, how are you? I come to report an error in a program that I used daily, it is paint.net, it is giving me two errors applying two different configurations, I pass two files, the first, the error that it only gives me when installing net framework 7 (now this program asks) and I pass what I get on the terminal screen with directx installed (along with the net framework 7), when I start the installer, the extract screen appears but the installer doesn't even load. The wine I use is 9.12 beta without staging, Ubuntu 22.04 MATE edition can you review it? All the best -- 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 56914] New: PowerToys 0.82.0 fails to install
by WineHQ Bugzilla May 9, 2026

May 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=56914 Bug ID: 56914 Summary: PowerToys 0.82.0 fails to install Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 76734 --> https://bugs.winehq.org/attachment.cgi?id=76734 Terminal output The PowerToys installer displays "Processing: Microsoft Edge WebView2" for about a minute, then says "0x80070643 - Installation failure." In the terminal output, Wine prints errors about several missing WinRT libraries: Windows.System.Diagnostics.Telemetry.PlatformTelemetryClient Windows.System.UserProfile.AssignedAccessSettings Windows.Data.Json.JsonObject I'm guessing that the lack of Windows.Data.Json.JsonObject is the problem. $ sha256sum PowerToysSetup-0.82.0-x64.exe 01b59c00bb43c25befef274755875717ab4deab57c0354ab96cf5b1da4837c9a -- 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

[Bug 56835] New: memory allocation error in wine9.0
by WineHQ Bugzilla May 9, 2026

May 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=56835 Bug ID: 56835 Summary: memory allocation error in wine9.0 Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: csumushu(a)126.com Distribution: --- Our program can run using Wine 8.0, but because Wine 8.0 does not sufficiently support the WinPcap library, it exits the function directly after calling pcap_loop without listening to the network card. Therefore, we plan to use Wine 9.0. We tested it with a test program, and it did not have this issue. However, when running our software, we encountered the following error log: ‘0104:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x3c141000, unix_prot 0x1’. Could this be due to some configuration 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.

2 12

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

May 9, 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 0

[Bug 59732] New: Custom WinXP/7 app printing garbled from wine 9 onwards
by WineHQ Bugzilla May 9, 2026

May 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59732 Bug ID: 59732 Summary: Custom WinXP/7 app printing garbled from wine 9 onwards Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: hugoac2004(a)gmail.com Distribution: --- My company have (for a decade or so) a WindowsXP/7 kind of application for general running of our business (nothing standard like, say, Microsoft Office). For all this time, I've mostly managed to make it work on Debian/Devuan Linux and Wine. Nowadays, we're using mostly Devuan Daedalus / Debian Bookworm and Wine 8, the app works perfectly. Then I've started testing Devuan Excalibur / Debian Trixie which comes with Wine 10, and I've learned it had ODBC broken which in turn broke my app. No matter, I installed wine-stable 9 from winehq, and it worked just fine. Or so I thought... Someone else which was testing the app on wine 9 let me know about several "documents" which the app prints to PDF or physical printers, which on wine 8 comes out perfectly, but on wine 9 and onwards come out garbled. You can see here on https://shorturl.at/RJ107 an example of a document printed all right, and the same document printed garbled at https://shorturl.at/q5Rjw Up to now I've had the same results with wine-stable 11 and wine-staging up to 11.8. What I'd like to know if there's some way to debug the printing, perhaps with WINEDEBUG? I've read something about "+winspool" and "+cups" -- 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 58870] New: Haltech NSP crashes on startup
by WineHQ Bugzilla May 9, 2026

May 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=58870 Bug ID: 58870 Summary: Haltech NSP crashes on startup Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: russian.pixie(a)gmail.com Distribution: --- Created attachment 79534 --> http://bugs.winehq.org/attachment.cgi?id=79534 Program error details https://www.haltech.com/wp-admin/admin-ajax.php?action=ht_latest_software NexusInstallPackageWeb_v1.53.5.exe I've installed Haltech NSP and Datalog Viewer. Dataloger opens just fine, however NSP crashes on startup. I don't have any compontents activated because I can't find what the software needs. 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.

2 4

[Bug 59734] New: Can't login anymore to battle.net after upgraded nettle from 3.10.2 to 4.0
by WineHQ Bugzilla May 9, 2026

May 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59734 Bug ID: 59734 Summary: Can't login anymore to battle.net after upgraded nettle from 3.10.2 to 4.0 Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: joachim.ionoff(a)gmail.com Distribution: --- Created attachment 80897 --> http://bugs.winehq.org/attachment.cgi?id=80897 logs with winedebug crypt I'm using archlinux and today several packages has been upgraded and I suspect it is linked to nettle upgrade. From the wine output logs I can see: attle.net\Battle.net.exe: ecc-random.c:62: _nettle_ecc_mod_random: Assertion `nbytes <= m->size * sizeof (mp_limb_t)' failed. 02dc:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. wine client error:11c: write: Bad file descriptor List of packages upgraded: nettle (3.10.2-1 -> 4.0-1) curl (8.20.0-5 -> 8.20.0-6) gstreamer (1.28.2-1 -> 1.28.2-2) gst-plugins-base-libs (1.28.2-1 -> 1.28.2-2) gst-libav (1.28.2-1 -> 1.28.2-2) gst-plugins-bad-libs (1.28.2-1 -> 1.28.2-2) gst-plugin-gtk (1.28.2-1 -> 1.28.2-2) gst-plugin-qml6 (1.28.2-1 -> 1.28.2-2) gst-plugins-bad (1.28.2-1 -> 1.28.2-2) gst-plugins-base (1.28.2-1 -> 1.28.2-2) gst-plugins-good (1.28.2-1 -> 1.28.2-2) gst-plugins-ugly (1.28.2-1 -> 1.28.2-2) gst-python (1.28.2-1 -> 1.28.2-2) lib32-nettle (3.10.2-1 -> 4.0-1) lib32-gnutls (3.8.13-1 -> 3.8.13-3) lib32-curl (8.20.0-5 -> 8.20.0-6) libcurl-compat (8.20.0-5 -> 8.20.0-6) lib32-libcurl-compat (8.20.0-5 -> 8.20.0-6) libcurl-gnutls (8.20.0-5 -> 8.20.0-6) lib32-libcurl-gnutls (8.20.0-5 -> 8.20.0-6) openconnect (1:9.12-4 -> 1:9.12-5) wget (1.25.0-3 -> 1.25.0-4) The wine version I used is 11.8 (with staging). I tried to rebuild after those packages upgrade, but no success. I attached logs with WINEDEBUG=+crypt. Don't hesitate to ask me more. Thanks for your help. -- 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 59719] New: Estlcam crashes when opening a previously good file
by WineHQ Bugzilla May 9, 2026

May 9, 2026

http://bugs.winehq.org/show_bug.cgi?id=59719 Bug ID: 59719 Summary: Estlcam crashes when opening a previously good file Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: reggiepye(a)proton.me Distribution: --- Created attachment 80860 --> http://bugs.winehq.org/attachment.cgi?id=80860 Estlcam crash on file open Estlcam worked yesterday OK, but today crashes when trying to open a file,. -- 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 1