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

[Bug 59944] BOINC's project dialog is messed up

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59944 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |48bb5d586467895c329b840ed95 | |40525edf3b422 --- Comment #6 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Thanks, AJ. Ran a bisect multiple times and came up with different results. Finally, after nuking everything between each recompile I landed on: commit 48bb5d586467895c329b840ed9540525edf3b422 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Nov 12 13:43:14 2025 +0100 winebuild: Assign section file positions once the offset is known. Didn't trust the result so I ran multiple loops with both this commit, and the previous commit, compiling from scratch and installing in a clean wineprefix each time, and got consistent results. 48bb5d586467895c329b840ed9540525edf3b422 — Bug 48bb5d586467895c329b840ed9540525edf3b422^ — No bug For my sanity: wine boinc_7.14.2_windows_intelx86.exe /v/qn /S wine "c:\program files\boinc\boincmgr.exe" Tested with the 32-bit release to save some time. -- 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.

July 1, 2026

[Bug 59950] Shader compilation fails when starting Just Cause.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59950 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |d56bae228090e474f96bd2310f2 | |609270bd32b98 CC| |z.figura12(a)gmail.com Keywords| |regression -- 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.

July 1, 2026

[Bug 59950] Shader compilation fails when starting Just Cause.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59950 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- 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.

July 1, 2026

[Bug 59932] Slingplayer 2's help has an extra window

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59932 --- Comment #3 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Looks good here. -- 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.

July 1, 2026

[Bug 59950] New: Shader compilation fails when starting Just Cause.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59950 Bug ID: 59950 Summary: Shader compilation fails when starting Just Cause. Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d-util Assignee: wine-bugs(a)list.winehq.org Reporter: ldmwbjbipxjqwacdhk(a)kjkpc.net Distribution: --- Created attachment 81324 --> http://bugs.winehq.org/attachment.cgi?id=81324 Patch that fixes the issue Shader compilation fails when starting Just Cause. When I start Just Cause on Wine 11.10 or newer, I get 3 message boxes complaining about syntax errors. Title: Vertex shader error! Line 40: Unexpected input e Line 40: Error "syntax error" from bison Title: Vertex shader error! Line 42: Unexpected input e Line 42: Error "syntax error" from bison Title: Vertex shader error! Line 48: Unexpected input e Line 48: Error "syntax error" from bison Here is a snippet of some interesting lines when enabling tracing with WINEDEBUG=trace+d3dcompiler,asmshader 0024:trace:asmshader:asmshader_parse Vertex shader 1.1 0024:trace:asmshader:asmparser_constF Adding float constant 90 at pos 0. 0024:trace:asmshader:asmparser_constF Adding float constant 91 at pos 1. 0024:trace:d3dcompiler:compilation_message Line 40: Unexpected input e 0024:trace:d3dcompiler:compilation_message Line 40: Error "syntax error" from bison 0024:trace:d3dcompiler:assemble_shader Assembler messages: 0024:trace:d3dcompiler:assemble_shader "Line 40: Unexpected input e\nLine 40: Error \"syntax error\" from bison\n" 0024:trace:d3dcompiler:assemble_shader Shader source: 0024:trace:d3dcompiler:assemble_shader "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\r\nvs_1_1 \r\ndef c90 , 768 , 256 , 0.5 , - 0.00138883968 \r\ndef c91 , 0.159154937 , 0.25 , 0.5 , 0.0416666418 \r\ndef c92 , 6.28318548 , - 3.14159274 , - 2.52398507e-007 , 2.47609005e-005 \r\ndef c93 , - 0.5 , 1 , 0 , "... 0024:trace:d3dcompiler:D3DCreateBlob data_size 70, blob 0032F594. 0024:trace:d3dcompiler:D3DCreateBlob Created ID3DBlob 0558F108 0024:trace:d3dcompiler:d3dcompiler_blob_GetBufferPointer iface 0558F108 0024:err:d3dcompiler:assemble_shader Asm reading failed This is a regression. The game starts fine on Wine 11.0, 11.5, 11.7, 11.9, and probably older versions as well. Suspected cause: If I am reading the git log correctly, Wine 11.10 defaulted to builtin Direct3D libraries, instead of using the native libraries. This revealed a deficiency in the Direct3D shader parser. The problem seems to be that the game uses the exponent notation for some floating-point literals, but the Wine's parser grammar does not accept that. Proposed solution: A one line change to dlls/d3dcompiler_43/asmshader.l , that adds support for the exponent notation, seems to solve the problem. -- 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.

July 1, 2026

[Bug 59949] wmvcore fails to allocate sample buffer (E_OUTOFMEMORY) in WOW64 mode, causing video playback to stop after a few seconds

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59949 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Component|quartz |-unknown Ever confirmed|0 |1 --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- This is Wine bugzilla, not Proton bugzilla. Try again in vanilla Wine 11.12 and DO NOT USE AI. https://gitlab.winehq.org/wine/wine/-/wikis/Bugs -- 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.

July 1, 2026

[Bug 59949] New: wmvcore fails to allocate sample buffer (E_OUTOFMEMORY) in WOW64 mode, causing video playback to stop after a few seconds

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59949 Bug ID: 59949 Summary: wmvcore fails to allocate sample buffer (E_OUTOFMEMORY) in WOW64 mode, causing video playback to stop after a few seconds Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)list.winehq.org Reporter: skitz2307(a)gmail.com Distribution: --- Created attachment 81323 --> http://bugs.winehq.org/attachment.cgi?id=81323 Full Log File Summary: When running 32-bit games with PROTON_USE_WOW64=1, video playback stops after a few seconds. The demuxer reads and decodes frames correctly, but then wmvcore fails to allocate a buffer for the next sample with E_OUTOFMEMORY (0x8007000e), after which demuxer_destroy fails with Access Violation (0xc0000005). Environment: - OS: CachyOS (Arch-based Linux) - GPU: NVIDIA GeForce RTX 5060, driver 610.43.2 - Proton version: GE-Proton 11-1 - Wine mode: WOW64 (PROTON_USE_WOW64=1) - Game: Resident Evil Revelations 2 (Steam App ID: 287290) - Game type: 32-bit DirectX 9, MT Framework engine Steps to reproduce: 1. Set launch options: PROTON_USE_WOW64=1 WINEDEBUG=+quartz PROTON_LOG=1 2. Launch Resident Evil Revelations 2 3. Start campaign mode 4. Wait for any cutscene to begin playback 5. Video plays for ~2 seconds then goes black (audio continues) Expected behavior: Video plays completely without interruption. Actual behavior: Video stops after a few seconds. Log shows the following sequence: 05cc:warn:quartz:winedmo_demuxer_read Reached end of media file on demuxer 0x7f99f47ecc40. 05cc:warn:quartz:winedmo_transform_drain Draining transform. 05c8:err:wmvcore:wm_reader_read_stream_sample Failed to allocate sample of 1382400 bytes, hr 0x8007000e. 05c8:warn:quartz:winedmo_demuxer_destroy demuxer_destroy failed, status 0xc0000005 Root cause analysis: wmvcore fails to allocate ~1.4MB buffer for an uncompressed video frame (1382400 bytes = 1280x720 RGBA frame) with E_OUTOFMEMORY. This only happens in WOW64 mode — without PROTON_USE_WOW64=1 video works but the game crashes due to a separate WOW64 assertion failure in the main process (also a WOW64-related issue in 32-bit games on RTX 50xx GPUs). Without WOW64 mode crash log shows: Unhandled exception: assertion failed in wow64 32-bit code (0xf7fd522c) warn:virtual:virtual_setup_exception exception outside of stack limits Additional notes: - PROTON_NVIDIA_LIBS_NO_32BIT=1 extends memory before crash from ~2GB to ~3GB but breaks video entirely - wmvcore=b,n override does not fix the issue - Problem is reproducible consistently -- 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.

July 1, 2026

[Bug 59928] Std 32-bit build fails with "../wine/dlls/oleaut32/vartype.c:3000:1: internal compiler error"

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59928 --- Comment #9 from Rafał Mużyło <galtgendo(a)o2.pl> --- If you want to know, it's Gentoo for me, but my ebuild is somewhat customized (not the one currently in the tree), mostly due to minor patches. It's still a 64+32 mingw build, not new wow64 (or however it's referred to). That tail end of the command line are the CFLAGS being explicitly passed to the build, both for me and from comment 5. This is simply the part that differs for me when compared to command 5. For some laughs, my cpu is also Ryzen, but a few generations older. > As Bernhard stated he was able to reproduce the problem and kindly provided version information you asked for. Actually, he didn't. I mean, if I were familiar with that distro, that could have meant something, but I'm not. We could assume he meant 'the tools as provided by a standard install of that distro's version', but that would be just an assumption. As cpuinfo for both of our cpus confirms sse2 support, this is a CFLAGS combination failure, so a compiler bug. As you might have noted, my gcc is kinda old, so I'm a bit curious when things broke, yet even if the wine devs decided to make some changes, the problem would still lie with gcc. Side note: after what I've wrote above, if - as google says - Debian 12 was actually using gcc 12 *and* this problem was actually fixed in gcc 13, I'd consider it quite hilarious. -- 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.

July 1, 2026

[Bug 58409] Black Mirror 2 needs support for Write fx 2.0 parameter class 0x11

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58409 --- Comment #3 from Andrey Gusev <andrey.goosev(a)gmail.com> --- Created attachment 81322 --> http://bugs.winehq.org/attachment.cgi?id=81322 shader Still reproducible with vkd3d-2.0-121-gbdfb9687 -- 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.

July 1, 2026

[Bug 59948] NinjaTrader 8 crashes on startup with Mono (winetricks dotnet48 works around it)

by WineHQ Bugzilla

July 1, 2026