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

[Bug 35848] New: Sound, Black Screen then crash
by wine-bugs＠winehq.org Sept. 27, 2026

Sept. 27, 2026

http://bugs.winehq.org/show_bug.cgi?id=35848 Bug ID: 35848 Summary: Sound, Black Screen then crash Product: Wine Version: 1.7.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adec2010(a)hotmail.co.uk Killing Time. After installation, set to windows 95 compatibility. It runs with a black screen. I can hear sound but then a crash back to the desktop -- 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 53267] New: user32:win - test_mouse_input() fails on Windows 10 21H1+
by WineHQ Bugzilla Sept. 27, 2026

Sept. 27, 2026

https://bugs.winehq.org/show_bug.cgi?id=53267 Bug ID: 53267 Summary: user32:win - test_mouse_input() fails on Windows 10 21H1+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:win - test_mouse_input() fails on Windows 10 21H1+: win.c:4549: Test failed: hwnd 000401CA/000401CA message 0204 win.c:4554: Test failed: hwnd 000401CA/000401CA message 0205 win.c:4559: Test failed: hwnd 000401CA/000401CA message 0206 win.c:4564: Test failed: hwnd 000401CA/000401CA message 0205 win.c:4580: Test failed: hwnd 002D039C/002D039C message 0204 win.c:4584: Test failed: hwnd 002D039C/002D039C message 0205 win.c:4593: Test failed: hwnd 000401CA/000401CA message 0204 win.c:4596: Test failed: hwnd 000401CA/000401CA message 0205 win.c:4629: Test failed: hwnd 00F802E8/00F802E8 message 00a4 win.c:4635: Test failed: hwnd 00F802E8/00F802E8 message 00a5 win.c:4642: Test failed: hwnd 00F802E8/00F802E8 message 0206 win.c:4644: Test failed: wparam 2 win.c:4655: Test failed: hwnd 00F802E8/00F802E8 message 0205 https://test.winehq.org/data/patterns.html#user32:win This is quite similar to the failures in the Korean locale (bug 51395). -- 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 57175] New: Multiple issues with Audacity after upgrading to Wine 9.17
by WineHQ Bugzilla Sept. 27, 2026

Sept. 27, 2026

https://bugs.winehq.org/show_bug.cgi?id=57175 Bug ID: 57175 Summary: Multiple issues with Audacity after upgrading to Wine 9.17 Product: Wine Version: 9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 77073 --> https://bugs.winehq.org/attachment.cgi?id=77073 Audacity 3.6.3 in Wine 9.17 with DPI=144 and classic Windows theme After I upgraded Wine from version 9.10 to 9.17, Audacity has become horrible to use and look at. I've always been using DPI=144 because I have a High DPI 14" monitor. So, * Fonts in Audacity have become much smaller than they were before * Fonts now look very blurry A screenshot will be attached. On the outside of Audacity you can see IrfanView which continues to scale properly and fonts are rendered just fine. -- 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 48

[Bug 59200] New: dmime: Pirates of Caribbean crash when moving mouse in menu screen
by WineHQ Bugzilla Sept. 27, 2026

Sept. 27, 2026

http://bugs.winehq.org/show_bug.cgi?id=59200 Bug ID: 59200 Summary: dmime: Pirates of Caribbean crash when moving mouse in menu screen Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dmusic Assignee: wine-bugs(a)list.winehq.org Reporter: jeremielapuree(a)yahoo.fr Distribution: --- Pirates of Caribbeans install, intro movies play. Menu screen appears. But when you move the mouse in this screen, the game crashes. Installing dmime with winetricks -q dmime fixes the crash Here is the short console output: 0134:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 0134:fixme:rawinput:NtUserRegisterRawInputDevices Unhandled flags 0x230 for device 0. 0130:fixme:d3d:state_linepattern_w Setting line patterns is not supported in OpenGL core contexts. 012c:fixme:dmime:performance_InitAudio flags parameter not used 012c:fixme:dmime:performance_CreateStandardAudioPath (0011DA80)->(1, 128, 0, 0011DAB8): semi-stub 012c:fixme:dmusic:synth_port_SetDirectSound (055EEB60/055EEB60)->(055F55DC, 00000000): semi-stub 012c:fixme:dmsynth:synth_sink_Activate (05602938)->(1): semi-stub 012c:fixme:dmime:IDirectMusicAudioPathImpl_Activate (056195B8, 0): semi-stub 012c:fixme:dmime:performance_AddNotificationType (0011DA80, GUID_NOTIFICATION_SEGMENT): stub 012c:fixme:dmime:performance_Stop (0011DA80, 00000000, 00000000, 0, 0): semi-stub 012c:fixme:dmime:performance_Stop flags parameter 0 not implemented 012c:fixme:dmime:wave_track_Init (05871620, 05871258): stub 012c:fixme:dmime:wave_track_Init (05879258, 05878E90): stub 012c:fixme:dmime:wave_track_Init (05886FD8, 05886C10): stub 012c:fixme:dmime:wave_track_Init (05898E10, 05898A48): stub 012c:fixme:dmime:wave_track_Init (058A15A0, 058A11D8): stub 012c:fixme:dmime:wave_track_Init (058AA198, 058A9DD0): stub 012c:fixme:dmime:wave_track_Init (058B7E28, 058B7A48): stub 012c:fixme:dmime:wave_track_Init (058B8568, 058886E8): stub 012c:fixme:dmime:wave_track_Init (058B8CA8, 058D5B10): stub 012c:fixme:dmime:wave_track_Init (058B93E8, 058E0270): stub 012c:fixme:dmime:wave_track_Init (058B9B28, 058E5E58): stub 012c:fixme:dmime:wave_track_Init (058BA268, 058F2D80): stub 012c:fixme:dmusic:parse_wave_chunk Ignoring chunk 'bext' '' 012c:fixme:dmusic:parse_wave_chunk Ignoring chunk 'minf' '' 012c:fixme:dmusic:parse_wave_chunk Ignoring chunk 'elm1' '' 012c:fixme:dmusic:parse_wave_chunk Ignoring chunk 'regn' '' 012c:fixme:dmusic:parse_wave_chunk Ignoring chunk 'ovwf' '' 012c:fixme:dmusic:parse_wave_chunk Ignoring chunk 'umid' '' 012c:fixme:dmime:wave_track_Init (058BA9A8, 05913EE0): stub 012c:fixme:dmime:wave_track_Init (058BB0E8, 059165A8): stub 012c:fixme:dmime:wave_track_Init (058BB828, 0591E828): stub 012c:fixme:dmime:wave_track_Init (058BBF68, 05926480): stub 012c:fixme:dmime:wave_track_Init (058BC6A8, 0592A520): stub 012c:fixme:dmime:wave_track_Init (058BCDE8, 05938E60): stub 012c:fixme:dmime:wave_track_Init (058BD528, 05939240): stub 012c:fixme:dmime:wave_track_Init (058BDC68, 05939620): stub 012c:fixme:dmime:wave_track_Init (058BE3A8, 05939A00): stub 012c:fixme:dmime:wave_track_Init (058BEAE8, 05939DE0): stub 012c:fixme:dmime:wave_track_Init (059831F0, 0593A1C0): stub 012c:fixme:dmime:wave_track_Init (05983930, 0593A5A0): stub 012c:fixme:dmime:performance_CreateStandardAudioPath (0011DA80)->(7, 1, 1, 01AB1174): semi-stub 012c:fixme:dmusic:synth_port_SetDirectSound (055EEC10/055EEC10)->(055F55DC, 00000000): semi-stub 012c:fixme:dmsynth:synth_sink_Activate (0849ECF8)->(1): semi-stub 012c:fixme:dmsynth:synth_sink_Activate (05602938)->(0): semi-stub 012c:fixme:dmime:IDirectMusicAudioPathImpl_Activate (082D55A8, 1): semi-stub 012c:fixme:dmime:performance_PlaySegmentEx (0011DA80, 05939240, (null), 00000000, 0x80, 0, 0022F8FC, 082D55A8, 082D55A8): stub 012c:fixme:dmime:performance_PlaySegmentEx flags 0x80 not implemented 012c:fixme:dmime:wave_track_InitPlay (058BD528, 058CB010, 0011DA80, 056021AC, 1, 0): stub 012c:fixme:dmime:segment_state_GetObjectInPath (058CB010, -5, 24576, 0, {00000000-0000-0000-0000-000000000000}, 0, {279afa85-4981-11ce-a521-0020af0be560}, 0022F8CC): stub 01a8:fixme:dmime:performance_tool_ProcessPMsg Unhandled message type 0xb 01a8:fixme:dmime:performance_tool_ProcessPMsg Unhandled message type 0xb wine: Unhandled page fault on read access to 00000000 at address 00000000 (thread 012c), starting debugger... 01a8:fixme:dmime:wave_track_EndPlay (058BD528, 8A234BE3): stub -- 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 59659] New: SimTower installer instantly terminates with "Insufficient memory or disk space"
by WineHQ Bugzilla Sept. 26, 2026

Sept. 26, 2026

http://bugs.winehq.org/show_bug.cgi?id=59659 Bug ID: 59659 Summary: SimTower installer instantly terminates with "Insufficient memory or disk space" Product: Wine Version: 11.6 Hardware: x86-64 URL: https://www.myabandonware.com/game/simtower-the-vertic al-empire-3f2#download OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: lingm+winebz(a)posteo.org Distribution: --- 1) Download the version labeled "Floppy" on myabandonware. All three appear affected, but let's go with this one for now. 2) Extract and run "wine SETUP.EXE". 3) Instantly a message box saying "Insufficient memory or disk space" appears. Not a single line of console output. The issue does not reproduce with Proton 10.0-4 and others have reported issues way further along. Maybe new WoW64 related? The archive: > $ sha1sum SimTower-The-Vertical-Empire_Win-3x_EN_Floppy-version.zip > 444f5e1b55b24332508324ecafbee5502c64a18d SimTower-The-Vertical-Empire_Win-3x_EN_Floppy-version.zip > $ du -h SimTower-The-Vertical-Empire_Win-3x_EN_Floppy-version.zip > 2,8M SimTower-The-Vertical-Empire_Win-3x_EN_Floppy-version.zip The installer exe itself: > $ sha1sum SETUP.EXE > a654343f6730c3fedee250b61a7f4222461c0aea SETUP.EXE > $ du -h SETUP.EXE > 28K SETUP.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 6

[Bug 58921] New: WebView2 does not work with Windows version setting 8.1 or newer
by WineHQ Bugzilla Sept. 25, 2026

Sept. 25, 2026

http://bugs.winehq.org/show_bug.cgi?id=58921 Bug ID: 58921 Summary: WebView2 does not work with Windows version setting 8.1 or newer Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: felixhaedicke(a)web.de Distribution: --- Created attachment 79605 --> http://bugs.winehq.org/attachment.cgi?id=79605 webview.log (log created by WebView2) For testing WebView2, I am using my "SimpleWebView2Browser", see https://github.com/felixhaedicke/SimpleWebView2Browser for source code and binaries. Steps to get it running on a fresh wineprefix: * Install WebView2 runtime using the "Evergreen Standalone Installer" for x64 from Inst https://developer.microsoft.com/en-us/microsoft-edge/webview2 * Set Windows version to Windows 7 or 8. * Use my "SimpleWebView2Browser" binaries from https://github.com/felixhaedicke/SimpleWebView2Browser/releases/tag/v0.1 It is sufficient to set the Windows version for "msedgewebview2.exe" (which is part of the WebView2 runtime): wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\msedgewebview2.exe" /v Version /t REG_SZ /d win8 It does not work with Windows version set to 8.1, 10 or 11. The problem is probably that WebView2 tries to use the DirectComposition API on Windows 8.1 or newer. Message in the WebView2 debug log: DCompositionCreateDevice failed: Not implemented. (0x80004001) The attached WebView2 debug log was captured using the WebView2 logging functions, which can be enabled using the WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS environment variable. Command line used to start the browser process, and to capture the attached logs: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS="--enable-logging --v=1 --log-file=c:/webview.log" wine SimpleWebView2Browser.exe 2> wine-output.txt -- 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 17

[Bug 57100] New: Command Post fails to load
by WineHQ Bugzilla Sept. 25, 2026

Sept. 25, 2026

https://bugs.winehq.org/show_bug.cgi?id=57100 Bug ID: 57100 Summary: Command Post fails to load Product: Wine Version: 9.16 Hardware: x86-64 URL: https://cgf-uploads.net/production/public/files/Comman dPostInstaller.zip OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 76978 --> https://bugs.winehq.org/attachment.cgi?id=76978 Wine 9.16 console output Immediately following installation of Command Post, the application fails to load. Subsequent attempt to run the application fails in the same way. wine "c:\program files\command post\commandpost.exe" > System.Runtime.Remoting.RemotingException: Channel CommandPost-KW-UniqueKeytest:SingeInstanceIPCChannel is not securable while ensureSecurity is specified as true Workaround is dotnet45 (if using Winetricks you need to set the Windows version to Windows 7 after installation: "winetricks dotnet45 win7"). https://cgf-uploads.net/production/public/files/CommandPostInstaller.zip https://web.archive.org/web/20240825002112/https://cgf-uploads.net/producti… c7b571e5020866e068c8b780782be72cf5f8df3f CommandPostInstaller.exe d29f3e8bceace7fc43113728555c2eae4f684d1b CommandPostInstaller.zip -- 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 50418] New: ArcGIS Pro fails to launch with wine-mono
by WineHQ Bugzilla Sept. 24, 2026

Sept. 24, 2026

https://bugs.winehq.org/show_bug.cgi?id=50418 Bug ID: 50418 Summary: ArcGIS Pro fails to launch with wine-mono Product: Wine Version: 6.0-rc4 Hardware: x86-64 URL: http://data.wvgis.wvu.edu/SecureFTP/securedownload/arc /ArcGIS%20Pro/ArcGISPro_22_163783.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Unhandled Exception: System.InvalidProgramException: Invalid IL code in ActiproSoftware.Windows.Controls.Ribbon.UI.RibbonMeasurements:set_BackstageTabWidth (double): IL_0002: stsfld 0x04000137 at ArcGIS.Desktop.Framework.FrameworkApplication..ctor () [0x00169] in <a27482abd44f4054a15c91c81cd4a531>:0 at ArcGIS.Desktop.Core.ProApp..ctor () [0x00012] in <5f84b0450bdb4a808e04ab6ef46dd283>:0 at <Module>.main (System.String[] args) [0x00000] in <bb19de946d75458385874ec2b780dbb5>:0 I haven't tried debugging yet. -- 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 59068] New: ScriptPlace() total run width sum inconsistent with advance width array sum
by WineHQ Bugzilla Sept. 23, 2026

Sept. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=59068 Bug ID: 59068 Summary: ScriptPlace() total run width sum inconsistent with advance width array sum Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)list.winehq.org Reporter: benc.marek.elektro98(a)proton.me Distribution: --- Created attachment 79842 --> http://bugs.winehq.org/attachment.cgi?id=79842 Example program with ScriptPlace() that displays a run's advance width. Hello, I'm working on a Uniscribe text editor and doing a bit of testing with Wine too, and I've hit an issue where the ScriptPlace() function's last argument, the ABC width of the run, occasionally has an inconsistent width as compared to the sum of the advance width elements provided through the piAdvance array. The MSDN documentation appears to suggest that the sum of the fields provided by the ABC parameter should match the total width of the run: https://learn.microsoft.com/en-us/windows/win32/api/usp10/nf-usp10-scriptpl… """ The composite ABC width for the whole item identifies how much the glyphs overhang to the left of the start position and to the right of the length implied by the sum of the advance widths. The total advance width of the line is exactly abcA+abcB+abcC. The abcA and abcC values are maintained as proportions of the cell height represented in 8 bits and are thus roughly +/-1 percent. The total width retrieved, which is the sum of the abcA+abcB+abcC values indicated by piAdvance, is accurate to the resolution of the TrueType shaping engine. """ I'm adding the source code of a simple demonstration program to show the error in the attachment. Here's the build command: $ i686-w64-mingw32-gcc -o scriptplace_abc_testcase.exe scriptplace_abc_testcase.c -lusp10 -lgdi32 -municode -O2 -Wall -Wextra -W This example uses a string that triggered the condition for me in my text editing widget, which I noticed as the caret being misaligned, since the distance of the caret from the edge of the run was measured with the assumption that the total advance width is abcA+abcB+abcC, but that is not the case. The example program generates a single text run, displays it on-screen with the default UI font retrieved by SPI_GETNONCLIENTMETRICS (Tahoma) with a 24 pt size, and displays the advance width value for each glyph, their sum, the ABC values, and their sum. On Debian 13 with wine-10.0 (Debian 10.0~repack-6), I'm getting the following: testprog_load_1st_glyph_run(): first_run->abc: { abcA: 16, abcB: 178, abcC: 28 }, total: 222 testprog_load_1st_glyph_run(): first_run->glyph_advances: [ 17, 17, 15, 12, 10, 24, 8, 12, 18, 10, 12, 18, 12, 17, 17 }, total: 219 On Windows, I'm getting the following: testprog_load_1st_glyph_run(): first_run->abc: { abcA: 0, abcB: 209, abcC: 0 }, total: 209 testprog_load_1st_glyph_run(): first_run->glyph_advances: [ 20, 17, 16, 9, 9, 23, 7, 9, 18, 9, 9, 18, 11, 17, 17 }, total: 209 I was able to trace down the error in the Wine source code. The advances and ABC are initially set to the same value in ScriptShape, see the following: https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/gdi32/uniscribe/usp1… """ if (pABC) { pABC->abcA += abc.abcA; pABC->abcB += abc.abcB; pABC->abcC += abc.abcC; } if (piAdvance) piAdvance[i] = abc.abcA + abc.abcB + abc.abcC; } SHAPE_ApplyOpenTypePositions(hdc, (ScriptCache *)*psc, psa, pwGlyphs, cGlyphs, piAdvance, pGoffset); """ But if you look just below, there is a SHAPE_ApplyOpenTypePositions() call that accepts the glyph advance array as an argument. This eventually ends up calling GPOS_apply_lookup() in https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/gdi32/uniscribe/open… - which adjusts the advances: """ if (advance.x || advance.y) { GPOS_convert_design_units_to_device(lpotm, lplogfont, advance.x, advance.y, &devX, &devY); piAdvance[glyph_index] += round(devX); if (advance.y) FIXME("Unhandled adjustment to Y advancement\n"); } break; """ Clearly, this causes the advance array and the ABC width to de-synchronize. I also don't think the way the ABC width is calculated in the first place is correct, I see the As and Cs being summed up, but shouldn't they only be propagated for the left-most and right-most glyph, and otherwise be summed up in the B? But that's a separate issue, and it doesn't cause a problem for me. Thanks, Marek -- 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 27336] New: Starcraft 2: Broken Sound
by wine-bugs＠winehq.org Sept. 23, 2026

Sept. 23, 2026

http://bugs.winehq.org/show_bug.cgi?id=27336 Summary: Starcraft 2: Broken Sound Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mmdevapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: aeneas(a)q-mail.me Since wine 1.3.19 the sound in StarCraft 2 as well as in other games (see comments from http://appdb.winehq.org/objectManager.php?sClass=version&iId=20882 ) is very broken. It has a lot of glitches and crashes very often. If it crashes, I have to select another Sound Device in the StarCraft settings to enable the sound again. Pre 1.3.19 using a mmdevapi override (disabled) was enough to enable sound. I report this using ALSA as my sound driver. eSound actually works pretty well but has a latency of about 0.6 - 0.8 seconds which is very anoying If you need any further information, like logs or something please contact me. -- 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 15