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

[Bug 48912] New: Allow blacklisting unreliable and always new failures
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48912 Bug ID: 48912 Summary: Allow blacklisting unreliable and always new failures Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A number of tests produce false positives because: * Either the failure message contains a value that changes with each run (e.g. an HWND). In some cases these values are really necessary for diagnosis and moving them to a separate line would make the code quite a bit more complex. * Or the test fails intermittently and is hard to fix. Sometimes the cause of the failures may also come from external factors such as bugs in QEmu (for instance long execution delays causing timeouts). * Sometimes the intermittent failure is the product of a new Windows version or configuration, which requires investigating before a fix is found. In all cases the tests should be fixed eventually, but a solution is needed for the interim so these tests to not make the TestBot so unreliable that its results are ignored. So the goal is to provide a way to blacklist some test failures so they do not cause a patch to be rejected. Some safeguards are needed to ensure that: * Failures are not blacklisted lightly. The preference should always be to fix the test. * The blacklist does not get so large that it becomes hard to maintain. * Once a test is fixed the corresponding blacklist entries are removed in a timely fashion. * There is still an incentive to fix the tests. So here is a proposal for implementing this blacklist: * Each blacklist entry should be associated with a Wine bug describing the issue. That bug should provide some minimal diagnosis: whether it's a new Windows behavior, a race condition or some issue that was reported to QEmu. That would ensure we know why the blacklist entry was added. One could also check the status of the bug when reviewing the blacklist entries. A closed bug would be a strong hint that the blacklist entry is no longer needed. * Rather than blacklisting whole test units, blacklist entries should target specific test failures via a regular expression. Besides being finer grained this would be useful for cases like user32:win which has different issues depending on the locale and where each should be linked to a different bug (bugs 48815, 48819 and 48820). * The TestBot should record when each blacklist entry was last used. This relies on having the above regular expression since without it the TestBot would not know anything beyond 'the test unit was run and had failures'. Also the regular expression would only be used against *new* failures. So this would really record the last time the blacklist entry was actually useful. An entry that was unused for a long time would be a prime candidate for reviewing the corresponding bug and for removal. (Note: The blacklist would also be used on WineTest reports so it would get a chance of matching its target at least 5 days / week). * The blacklist entries would only be needed for 'base' test configurations since they are the only ones wine-devel patches run on. * There should be a page listing the blacklist entries so developers have a good starting point to work on them. * Ideally the blacklist page would also point to the tasks where the blacklist was last used. Since most of the blacklisted failures are either intermittent or specific to a given test configuration this would make it easier for developers to find reports where the failure did happen. Note that Wine VMs often test multiple configurations per task (e.g. wow32 and wow64, different locales), each producing its own test report. So pointing at just the task would leave the developer guessing which report should be looked at. But that may be sufficient guidance. * (test:unit, testbot-vm) tuples make it impossible to target a specific Wine test configuration such as a specific locale since they all run on the same VM. Similarly it would make blacklisting bitness-blind on Windows VMs. If necessary the tuple could be extended either with the specific mission the blacklist applies to, or with the basename of the corresponding report (the latter being easier to use in comparisons). Whether that's practical and worth the effort remains to be determined. One complication for instance is that this would lead to more blacklist entries: many 64 bit VMs would need two entries, one for 32 bit tests and one for 64 bit tests. * Pseudo database schema and sample use: FailureBlacklists ----------------- PK Bug 48815 PK TestModule user32 PK TestUnit win Name 0x738 message FailureRegExp Test failed: hwnd [0-9A-F]{8,16} message 0738 LastUse 2020-03-27 FailureBlacklistVMs ------------------- PK Bug 48815 PK TestModule user32 PK TestUnit win PK VMName Entries for w1064v1709, w1064v1809, etc. (48815, user32, win, w1064v1709) (48815, user32, win, w1064v1809) (48815, user32, win, w1064v1809_2scr) ... FailureBlacklistUses (optionally) --------------------------------- PK Bug PK TestModule PK TestUnit PK JobId PK StepNo PK TaskNo (48815, user32, win, 68507, 1, 7) (48815, user32, win, 68508, 1, 7) ... -- 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 38583] New: Legions Overdrive: In-game textures black
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=38583 Bug ID: 38583 Summary: Legions Overdrive: In-game textures black Product: Wine Version: 1.7.42 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: gaming4jc2(a)yahoo.com Distribution: --- Created attachment 51481 --> https://bugs.winehq.org/attachment.cgi?id=51481 D3D fixmes Since the entire world is black excepting the sky and some text, it is still not possible to play this in native wine without DLL overrides. I am attaching a bug report showing various D3D fixmes needed. -- 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 14

[Bug 54472] New: Cryostasis: Sleep of Reason demo crashes due to HLSL syntax error 'unexpected KW_TECHNIQUE10'
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54472 Bug ID: 54472 Summary: Cryostasis: Sleep of Reason demo crashes due to HLSL syntax error 'unexpected KW_TECHNIQUE10' Product: vkd3d Version: 1.6 Hardware: x86-64 URL: https://www.guru3d.com/files-details/cryostasis-sleep- of-reason-game-demo.html OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 00d4:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x804. 00d4:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 00d4:err:d3dcompiler:D3DCompile2 Shader log: 00d4:err:d3dcompiler:D3DCompile2 signature.fx:8:1: E5000: syntax error, unexpected KW_TECHNIQUE10 00d4:err:d3dcompiler:D3DCompile2 1.6-110-g240b2f96 -- 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 41123] New: 8-bit Armies requires "fx_5_0" compilation target
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=41123 Bug ID: 41123 Summary: 8-bit Armies requires "fx_5_0" compilation target Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- When I was testing this bug: https://bugs.winehq.org/show_bug.cgi?id=40725 I noticed that 8-bit Armies would show this line in the terminal before crashing: fixme:d3dcompiler:compile_shader Compilation target "fx_5_0" not yet supported Native d3dcompiler_43 via "winetricks d3dcompiler_43" works around the 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.

3 6

[Bug 49810] New: WhenSilenceDimsTheStarsAbove demoscene demo crashes on startup
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=49810 Bug ID: 49810 Summary: WhenSilenceDimsTheStarsAbove demoscene demo crashes on startup Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 68135 --> https://bugs.winehq.org/attachment.cgi?id=68135 demo itself Wine-dbg>cont 00cc:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0060957d). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:0060957d ESP:0031fdd8 EBP:00008000 EFLAGS:00010202( R- -- I - - - ) EAX:00000000 EBX:000001bd ECX:0031fdac EDX:ffffffff ESI:00000000 EDI:01026560 Stack dump: 0x0031fdd8: 00000007 0031fe38 00000000 007447ca 0x0031fde8: 00000000 f6dc15c0 00606131 0102619c 0x0031fdf8: 0102619c 00000000 004d2270 00000013 0x0031fe08: 00081000 01fc0000 00080000 0031fe30 0x0031fe18: 0031fe88 7bc53f21 0000000a 00110000 0x0031fe28: 0031fe88 7bc53f21 00110094 7ffc2c00 Backtrace: =>0 0x0060957d in whensilencedimsthestarsabove.ex (+0x3957d) (0x00008000) 0x0060957d: movl 0x0(%eax),%ecx -- 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 20

[Bug 48426] New: Wine-Gecko can't be installed.
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=48426 Bug ID: 48426 Summary: Wine-Gecko can't be installed. Product: Wine-staging Version: 5.0-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)evolution-hosting.eu CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- wine-staging 64/32 is asking to install Gecko, but the installation attempt hangs at "loading down" with no progress. -- 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 3

[Bug 49006] New: Wrong detection the Windows' version by Uplay
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=49006 Bug ID: 49006 Summary: Wrong detection the Windows' version by Uplay Product: Wine-staging Version: 5.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: iroalexis(a)outlook.fr CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- When we fix the windows' version on Windows 10, Uplay detect Windows 8 (visible in launcher_log.txt file) Problematic for the furture -- 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 8

[Bug 54763] New: Build-time tests fail in an autobuilder environment
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54763 Bug ID: 54763 Summary: Build-time tests fail in an autobuilder environment Product: vkd3d Version: 1.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: smcv(a)collabora.com Distribution: --- In a typical distribution autobuilder environment, all builds will be run in a chroot or container, usually on server-class hardware or in a virtual machine. This means tests that just do computation (such as shader compilation) should still succeed, but tests that want to access a real GPU will find that either there is no VkDevice at all, or there is a VkDevice but it's only software rendering (lavapipe). It seems like vkd3d already has some partial handling for this: run_shader_tests_vulkan() skips itself if a VkDevice cannot be created. However, run_shader_tests_d3d12() still tries to run, and crashes when it can't create a Vulkan instance, for example: FAIL: tests/cast-to-half ======================== vkd3d:err:vkd3d_instance_init Failed to create Vulkan instance, vr -9. vkd3d:fixme:hresult_from_vk_result Unhandled VkResult -9. vkd3d:err:vkd3d_instance_init Failed to create Vulkan instance, vr -9. vkd3d:fixme:hresult_from_vk_result Unhandled VkResult -9. FAIL tests/cast-to-half.shader_test (exit status: 139) (Exit status 139 is a segmentation fault.) Would you consider patches that make the tests skip themselves in this situation? Or should distro packaging just not be running build-time tests at all? -- 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 9

[Bug 54372] New: World in Conflict crashes due to missing SM1 'cast' handling
by WineHQ Bugzilla Aug. 5, 2026

Aug. 5, 2026

https://bugs.winehq.org/show_bug.cgi?id=54372 Bug ID: 54372 Summary: World in Conflict crashes due to missing SM1 'cast' handling Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- Split off from bug 41310. 0024:err:d3dcompiler:D3DCompile2 Shader log: 0024:err:d3dcompiler:D3DCompile2 <anonymous>:7:1: E5017: Aborting due to not yet implemented feature: SM1 "cast" expression. 0024:err:d3dcompiler:D3DCompile2 -- 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 35312] New: "Toggle All" currently means "Inverse Selection"
by wine-bugs＠winehq.org Aug. 5, 2026

Aug. 5, 2026

http://bugs.winehq.org/show_bug.cgi?id=35312 Bug ID: 35312 Summary: "Toggle All" currently means "Inverse Selection" Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com Classification: Unclassified When selecting VMs the button "Toggle All" actually inverses the current selection. function ToggleAll() { for (var i = 0; i < document.forms[0].elements.length; i++) { if(document.forms[0].elements[i].type == 'checkbox') document.forms[0].elements[i].checked = !(document.forms[0].elements[i].checked); } } A possible solution: var toggledstate = true; function ToggleAll() { toggledstate = !toggledstate; for (var i = 0; i < document.forms[0].elements.length; i++) { if(document.forms[0].elements[i].type == 'checkbox') document.forms[0].elements[i].checked = toggledstate; } } -- 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 4