- Wine-Bugs - list.winehq.org

[Bug 59566] New: Cygwin's Mintty doesn't open - no errors or anything, just nothing happens.
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59566 Bug ID: 59566 Summary: Cygwin's Mintty doesn't open - no errors or anything, just nothing happens. Product: Wine Version: 11.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: winehq(a)regd.hamishmb.com Distribution: --- Mintty from Cygwin as of 25th March 2026 (Cygwin 3.6.7) doesn't launch, nothing happens when launched from the commandline and no error messages are shown. -- 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 11

[Bug 47600] New: DeaDBeeF doesn't show icons
by wine-bugs＠winehq.org April 25, 2026

April 25, 2026

https://bugs.winehq.org/show_bug.cgi?id=47600 Bug ID: 47600 Summary: DeaDBeeF doesn't show icons Product: Wine Version: 4.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t6zm3v62fkp7fe5(a)yandex.ru Distribution: --- Created attachment 65017 --> https://bugs.winehq.org/attachment.cgi?id=65017 Screenshot DeaDBeeF for Windows (https://github.com/DeaDBeeF-for-Windows/deadbeef/releases/download/2019-06-…) doesn't show icons and outputs these strings when opening the menu: 002b:err:module:import_dll Library librsvg-2-2.dll (which is needed by L"C:\\Program Files\\DeaDBeeF\\lib\\gdk-pixbuf-2.0\\2.10.0\\loaders\\libpixbufloader-svg.dll") not found 002b:err:module:import_dll Library libxml2-2.dll (which is needed by L"C:\\Program Files\\DeaDBeeF\\lib\\gdk-pixbuf-2.0\\2.10.0\\loaders\\libpixbufloader-svg.dll") not found Lubuntu 18.04.2, Wine 4.13 from official PPA. -- 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 7

[Bug 59637] New: Unhandled exception: unimplemented function api-ms-win-core-memory-l1-1-3.dll.VirtualProtectFromApp called in wow64 32-bit code (0x7a8ae6f8).
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59637 Bug ID: 59637 Summary: Unhandled exception: unimplemented function api-ms-win-core-memory-l1-1-3.dll.VirtualProtectFromAp p called in wow64 32-bit code (0x7a8ae6f8). 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: davipcarmo(a)gmail.com Distribution: --- Created attachment 80728 --> http://bugs.winehq.org/attachment.cgi?id=80728 Contém log da execução. Ao tentar executar hoje o game Roblox, aconteceu esse erro. -- 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 3

[Bug 59482] New: MASH (Microsoft Agent Scripting Helper) doen't really work!
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59482 Bug ID: 59482 Summary: MASH (Microsoft Agent Scripting Helper) doen't really work! Product: Wine Version: 11.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: DSKJConserver(a)gmail.com Distribution: --- I tried using the Mash Version 7.5 (Microsoft Agent scripting Helper), and I couldn't -- 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 59567] New: Cygwin installer v2.937 doesn't resize correctly after the first run
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59567 Bug ID: 59567 Summary: Cygwin installer v2.937 doesn't resize correctly after the first run Product: Wine Version: 11.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: winehq(a)regd.hamishmb.com Distribution: --- After the first run of the Cygwin installer, the GUI doesn't resize correctly, leaving GUI elements shrunk into a smaller area and becoming unclickable if you try to resize it too much. -- 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 59564] New: printf does not support %Z
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59564 Bug ID: 59564 Summary: printf does not support %Z Product: Wine Version: 11.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)list.winehq.org Reporter: me(a)trungnt2910.com Distribution: --- Created attachment 80622 --> http://bugs.winehq.org/attachment.cgi?id=80622 C++ example program This simple C++ program prints "Hello World!" on Windows: #include <cstdio> #include <winternl.h> int main() { wchar_t string[] = L"Hello World!"; UNICODE_STRING unicodeString { sizeof(string), sizeof(string), string }; printf("%Z\n", &unicodeString); return 0; } On Wine, it prints just "Z", meaning that this specifier is not supported. -- 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 59686] New: Popotan Po!: No text/fonts when using new WoW64 mode (but works using win32)
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59686 Bug ID: 59686 Summary: Popotan Po!: No text/fonts when using new WoW64 mode (but works using win32) Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce. de Distribution: --- Created attachment 80788 --> http://bugs.winehq.org/attachment.cgi?id=80788 Wine log files of the configurations tested Running "Popotan Po!" (ぽぽたん Po!) in a new wow64 mode prefix results in no in-game text. Instead, whenever text is supposed to be rendered, wine has 100 % CPU load according to htop for about 40 to 110 seconds, depending on the situation. Text on normal widgets (e.g. menu bar or window title bar) works fine. Host architecture: x86_64 (Arch running Linux 6.19.13) Guest architecture: i386 Tested with the following Wine packages/versions used on Arch (logs attached): - BAD: wow64 prefix with wine 11.7-1 (https://archlinux.org/packages/extra/x86_64/wine/) - BAD: wow64 prefix with wine-staging 11.7-1 (https://archlinux.org/packages/extra/x86_64/wine-staging/) - GOOD: win32 prefix with wine32 11.7-1 (https://aur.archlinux.org/packages/wine32) Further observations: - The problem does not appear in a win32 prefix (and it never did for the last 10 years or so). - Whether you use wine or wine-staging makes no apparent difference. Steps to reproduce: 1. Create a new wine prefix using winecfg and make wine emulate an 800x600 desktop. 2. Use the appropriate locale (otherwise, all dialogs only show mojibake): export LANG="ja_JP.eucjp" export LC_ALL="ja_JP.eucjp" 3. Install the game using the defaults suggested by the installer. 4. Launch the game. For this issue, there seems to be no difference between "tsuujouban" (通常版) and "koukinouban" (高機能版). Choose "tsuujouban". 5. At that point, if the problem occurs, you might get the 100 % CPU load mentioned above. Also, the whole wine dektop window freezes. Be patient. 6. The intro video starts. (In my case, playback only works in the wow64 prefixes but not in the win32 prefix. Instead, the screen appears all-black or all-white. Ignore that issue.) Use ESC to skip the intro. 7. In the main menu, choose "Config" (コンフィグ). 8. In the top-right corner, you can choose a "Font" (フォント). The name of the font is rendered between the two arrows using itself for demonstration purposes. Due to the issue at hand, the space between the two arrows appears empty as if no font is available. 9. Go back (ゲームへ戻る). 10. Now, back in the main menu, choose "tsuzuki kara" (つづきから). 11. Again, if the problem occurs, you might get 100 % CPU load and a frozen window. Be patient. 12. If everything works normally, saved game states should be listed. Even unused slots show some text like "----/--/-- --:--" (without quotes). However, due to the issue at hand, all lines appear empty (except for the numbers to the left which are, apparently, rendered using bitmaps, just like everything else so far). 13. Go back (タイトルへ). 14. Now, again back in the main menu, choose "hajime kara" (はじめから). The actual game starts. 15. Normally, a text box at the lower bottom appears, along with text in it as the story progresses. However, if the problem occurs, you might get 100 % CPU load and freezes along the way. Be patient whenever that happens. 16. A star symbol appears at the end of the text in the text box. The exact position of the star seems to be fixed. That is, the position seems to be independent of the glyphs used to render the text. As a result, if the problem occurs, the star seems to appear at various positions within the box, with no actually visible text ahead of it but close to where the text *should* have ended. Attempted workarounds: - Using "winetricks corefonts" or "winetricks allfonts" did not help. - Running "fc-cache -fv" also did not help. - Assuming it might be an encoding or locale problem, I tried *really hard* to make the whole thing run with locale ja_JP.UTF-8, with the result that it actually *did* run with that locale somehow. However, the issue persisted. - Using that same experimental prefix, I tried running it with locale ja_JP.UTF-8 again, but this time with "Windows Version" set to "Windows XP" in winecfg, to no avail. - When I tried to make it run with locale en_US.UTF-8, it crashed before I got to the intro. (This is not too surprising.) Further investigation and speculation: - The game seems to only list fonts it considers usable, so probably only fonts that are compatible enough for Japanese. - The config is stored in the registry, and by default (at least in my case), the installation in the win32 prefix as well as the installation in the wow64 prefix both use "FontFace"="ＭＳゴシック" according to regedit. Thus, despite already knowing the name of a font face to use, only the win32 prefix can make sense of it while the wow64 prefix cannot. - Even copying a working non-default value like "さざなみゴシック" from the registry of the win32 prefix and then pasting it as the new value into the wow64 registry did not help. - You can actually switch between different fonts using the arrows in the config screen mentioned above, even if you do not see it happening in the wow64 prefix. For example, after switching randomly and then closing the game, the corresponding value in the registry now reads "AR PL UMing TW MBE", for example. The very same font can be chosen normally in the win32 prefix as well. This indicates that the game in the wow64 version knows of the available fonts it considers usable, it just fails to render text properly using them. - For some unknown reason, though, the config screen opens quickly while everything else that normally has some text in it just burns CPU and displays no text at all. - Maybe it has something to do with Unicode stuff? -- 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 8

[Bug 3930] Miles Sound System (WAIL32.DLL) SuspendThread() deadlock in WINMM callback (silent black screen on HOMM startup)
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=3930 XJDHDR <XJDHDR.PUE004+bugs.winehq.org(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |XJDHDR.PUE004+bugs.winehq.o | |rg(a)gmail.com --- Comment #93 from XJDHDR <XJDHDR.PUE004+bugs.winehq.org(a)gmail.com> --- (In reply to Damjan Jovanovic from comment #80) > void (*ail_startup)(void); > int (*ail_waveOutOpen)(HWAVEOUT** phWaveOut, HWAVEOUT** phWaveOut2, > UINT uDeviceId, WAVEFORMATEX *waveFormatEx); Please excuse the off-topic comment, but where did you find these function signatures? -- 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 59679] New: Some sections of PKHeX crash with Wine 11.5+
by WineHQ Bugzilla April 25, 2026

April 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=59679 Bug ID: 59679 Summary: Some sections of PKHeX crash with Wine 11.5+ Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: tw0ali(a)tutanota.com Distribution: --- Created attachment 80775 --> http://bugs.winehq.org/attachment.cgi?id=80775 PKHeX logs Some sections of PKHeX crash starting from Wine version 11.5 (including 11.6 and 11.7). For example, “Trainer Info” or the “Search” button in the boxes. This bug is not reproducible in version 11.4, which is the last version without issues. -- 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 59687] New: 'const' variable modifier causes null return-value in vertex shader
by WineHQ Bugzilla April 24, 2026

April 24, 2026

http://bugs.winehq.org/show_bug.cgi?id=59687 Bug ID: 59687 Summary: 'const' variable modifier causes null return-value in vertex shader Product: Wine Version: 11.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)list.winehq.org Reporter: bczhc0(a)126.com Distribution: --- Created attachment 80789 --> http://bugs.winehq.org/attachment.cgi?id=80789 trace-ok.log Take this HLSL code which basically is a hello-triangle. ```hlsl struct VsOut { float4 pos : SV_Position; }; static const float2 VERTICES[3] = { float2(0.0, 0.5), float2(-0.5, -0.5), float2(0.5, -0.5) }; static const float4 RED = float4(1.0, 0.0, 0.0, 1.0); VsOut vs_main(uint vid : SV_VertexID) { float2 position = VERTICES[min(vid, 2u)]; VsOut output = { float4(position, 0.0, 1.0) }; return output; } float4 fs_main() : SV_Target { return RED; } ``` I have this wgpu program: https://gist.github.com/bczhc/e8d11db2280ffd20fee43fb1fed7410e to run and render this shader. (Sorry I'm not familiar with hlsl and windows programming so I just now only able to write the wgpu program to demonstrate it and suppose it may not be related to wgpu anyway) To compile and run it, do: ```bash # ensure to put it in a cargo project first cargo build --target x86_64-pc-windows-gnu # run WINEPREFIX=`pwd`/prefix WGPU_BACKEND=dx12 wine target/x86_64-pc-windows-gnu/debug/demo.exe the-hlsl-above.hlsl vs_main ``` It will display a red triangle. However, modify this line `VsOut output = { float4(position, 0.0, 1.0) };` to `const VsOut output = { float4(position, 0.0, 1.0) };`, then compile the Rust program then run it using wine again, the red triangle will not show. Or, if that line is left as is but you add another const variable, like this: ```hlsl VsOut vs_main(uint vid : SV_VertexID) { float2 position = VERTICES[min(vid, 2u)]; VsOut output = { float4(position, 0.0, 1.0) }; const VsOut output1 = output; return output1; } ``` The red triangle is also not able to display. This is originally reported as a wgpu issue here: https://github.com/gfx-rs/wgpu/issues/9056. At that time, only proton has this issue (wine is okay). However now with wine 11.6 I tested it again, wine has this issue either. So I suspect this is an upstream vkd3d hlsl compiler issue then? I haven't done the bisect yet because I haven't managed how to properly compile this project and substitute it for wine. -- 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 7