June 2023 - Wine-Bugs - list.winehq.org

[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 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 35128] New: Air Conflicts (Pacific Carriers/Secret Wars) hangs at the loading screen
by wine-bugs＠winehq.org Sept. 14, 2026

Sept. 14, 2026

http://bugs.winehq.org/show_bug.cgi?id=35128 Bug ID: 35128 Summary: Air Conflicts (Pacific Carriers/Secret Wars) hangs at the loading screen Product: Wine Version: 1.7.8 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Classification: Unclassified Created attachment 46858 --> http://bugs.winehq.org/attachment.cgi?id=46858 terminal output I have this bug with both games from the Air Conflicts series when running under Wine. The native Linux version of AC:Pacific Carriers (running under the Linux version of Steam) doesn't have the problem. Also, running the Windows version in Virtualbox doesn't have the problem. The problem: the game starts fine and mouse/keyboard work as expected in the menus, but when I start a mission the game is stuck in the loading screen. The game is not completely dead because game tips are cycling through on the screen and the text 'Press any key to continue' is flashing, but the game doesn't accept mouse or keyboard input any more so I can't get in the game. The ACPC.exe process is consuming 30-40% cpu, but nothing happens, I have to kill the process to exit. Fedora 19 Nvidia binary drivers 325.15 X.Org X Server 1.14.4 -- 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 17

[Bug 49747] New: ICO_ExtractIconExW causes crash on incomplete windows executable
by WineHQ Bugzilla Sept. 12, 2026

Sept. 12, 2026

https://bugs.winehq.org/show_bug.cgi?id=49747 Bug ID: 49747 Summary: ICO_ExtractIconExW causes crash on incomplete windows executable Product: Wine Version: 5.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: andi(a)notmuch.email Distribution: --- Created attachment 68049 --> https://bugs.winehq.org/attachment.cgi?id=68049 backtrace of explorer.exe crashing I have 31% of a binary in a local directory because some installer/patcher crashed during installation. Whenever I use `winefile` or `wine explorer.exe` and scroll to that file in the directory wine crashes with the attached backtrace. It appears to be related to the ICO handling code within wine that expects more input but that doesn't exist yet. Attached is the backtrace of running the patcher for the "Dark Age of Camelot" freeshard "Phoenix" (https://playphoenix.online) which did cause this issue for me. -- 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 7

[Bug 48415] New: The Magic School Bus Explores The Solar System fails to install
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

https://bugs.winehq.org/show_bug.cgi?id=48415 Bug ID: 48415 Summary: The Magic School Bus Explores The Solar System fails to install Product: Wine Version: 4.21 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Regression SHA1: f2060812418bc049105c2a30ceb039ee6d5f0fd7 Distribution: --- It claims: "File Copy operation failed - incorrect number of bytes written to disk - source file or destination disk may be corrupted - use ChkDsk. Source: '\\?\D:\MSBSOLAR\SETUP\_MSSETUP.EXE' Dest: 'C:\WINDOWS\_MSRSTRT.EXE'." Patch sent. -- 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 52254] New: Cold Steel Subs: Application is not transparent (relies on DwmExtendFrameIntoClientArea)
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

https://bugs.winehq.org/show_bug.cgi?id=52254 Bug ID: 52254 Summary: Cold Steel Subs: Application is not transparent (relies on DwmExtendFrameIntoClientArea) Product: Wine Version: 7.0-rc2 Hardware: x86-64 URL: https://zerofield.net/2020/09/30/hajimari-no-kiseki-sp readsheet-translation/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwmapi Assignee: wine-bugs(a)winehq.org Reporter: johnny(a)localmomentum.net Distribution: --- Created attachment 71376 --> https://bugs.winehq.org/attachment.cgi?id=71376 ColdSteelSubs transparency code (currently not in the distributed application) This application provides a transparent clickthrough overlay to show English translations on top of the original Japanese source. It relies on layered windows and DwmExtendFrameIntoClientArea to handle the transparent display. Currently, the main UI elements show, but the game (or any other application) does not show through. This seems to be because DwmExtendFrameIntoClientArea is only a stub. I'm not sure if that's the only reason it's not transparent, but it's at least one of the reasons. The program itself uses the unity3d engine along with some native dll calls to the relevant user32 apis to handle the transparency. I was able to get a copy of the relevant code (but not the whole application), of which I will attach. Since I can't get all of the code, I've been using an unity sample application to try to figure out some parts myself (the relevant code is here https://github.com/pheonise/Unity3D-Desktop-Overlay/blob/master/Assets/Scri…) This unity3d application works as expected on windows, but is not transparent via wine (as expected). When i comment the call to DwmExtendFrameIntoClientArea, then it its also no longer transparent on windows as well. It seems that if the sample application works, then I can make sure the dev applies to the same technique to the overlay application. Please let me know If i can provide any more information. -- 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 18

[Bug 54836] New: GrandMA3 onPC Version 1.9.2.2 page fault on startup (1.8.8.2 worked fine)
by WineHQ Bugzilla Sept. 11, 2026

Sept. 11, 2026

https://bugs.winehq.org/show_bug.cgi?id=54836 Bug ID: 54836 Summary: GrandMA3 onPC Version 1.9.2.2 page fault on startup (1.8.8.2 worked fine) Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: nikolaus.einhauser(a)web.de Distribution: --- So MALighting just released their new "major" update (new features, breaking old ones, etc) to their software which broke compatability with wine. Their previous version worked fine. The issue can easily be reproduced by installing the software and then starting `app_gma3.exe`. It will crash on startup. Judging by `wine: Unhandled page fault on execute access to 000000000000000F at address 000000000000000F (thread 010c)`, the problem seems to be in the application. By inspecting the `+relay` log a little closer the page fault only looks like a symptom of missing error handling. From what I can tell, the issue lies in wintrust.WinVerifyTrust but feel free to look trough the attached debug log yourself. I'd very glad to provide more in-depth debug info or help otherwise to aid in fixing this. Suggestions for workarounds are also appreciated. Thank you. PS. There is a contest currently ongoing that mandates the use of version 1.9 or higher. So staying on an older previously working version is not an option for me. -- 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 16

[Bug 39773] New: File->Open slowdown caused by desktop.ini checks
by wine-bugs＠winehq.org Sept. 9, 2026

Sept. 9, 2026

https://bugs.winehq.org/show_bug.cgi?id=39773 Bug ID: 39773 Summary: File->Open slowdown caused by desktop.ini checks Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- To reproduce this you will need two Linux machines, a Samba server and a Samba client. On the Samba server: * Create a directory with lots of subdirectories and files: mkdir smbdir cd smbdir for i in `seq 1 200`;do mkdir sub$i; done for i in `seq 1 200`;do touch file$i; done * Export smbdir through Samba. (alternatively you could export '/' and use '/usr/lib' as a replacement for smbdir) On the Samba client: * Mount the Samba share. You can either do it by adding a /etc/fstab line like: //MYSERVER/smbdir /mnt/smbdir cifs rw,username=MYLOGIN,password=MYPASSWORD,domain=MYDOMAIN 0 0 Or by starting Nautilus in GNOME, clicking on '+Other Places' -> Windows network... using GVFS. Note that in this case you'll have to work around the colon in the mount point filename (see bug 34868). * Slow down the network connection using a command like this: tc qdisc add dev eth0 root netem delay 10ms * Check the above line is effective by running: ping MYSERVER The rtt should be around 10ms. * cd /mnt/root/ wine notepad * Open the File->Open dialog, navigate to the smbdir folder exported through Samba. * BUG: The initial display will be slow and scrolling through the many subfolders will be very slow. * Change the file mask to '*.*'. * Scroll all the way to the right so only files are visible. As long as only files are visible scrolling should then be very fast! * Finally change the rtt to 0ms on the Samba server and check that the RTT is under 1ms. * Now test again notepad's File->Open dialog and everything should be reasonably fast. The problem is that whenever File->Open displays a folder in the open file dialog it checks whether it contains a desktop.ini file to display the right icon. That's not cached, thus incurring a few file lookups per folder displayed. For local file systems that's fast enough but on network shares with a non-trivial RTT the speed impact is significant. A 10+ ms RTT makes the dialog essentially unusable. Note that when displaying a filename we have everything in the cache so redisplays are lightning fast and track the mouse. Also Microsoft Office has the same problem even though it does not use the standard comdlg32 dialog (though that may depend on the Windows version being emulate). On Windows Microsoft Office suffers no slowdown in this situation. What this means is that the standard common dialog is probably the wrong level for fixing this. Hacking SHELL32_GetCustomFolderAttributeFromPath() in shell32 to just return FALSE speeds things up greatly. The display still lags a bit behind the mouse so that there may be some residual file lookups or other slowdowns but it's still night and day. -- 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