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

[Bug 55632] New: ntdll:file - test_file_link_information() fails on Windows 10 1709 and older
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55632 Bug ID: 55632 Summary: ntdll:file - test_file_link_information() fails on Windows 10 1709 and older Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:file - test_file_link_information() fails on Windows 10 1709 and older: file.c:2249: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2251: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2256: Test failed: file should exist file.c:2291: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2321: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2323: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2354: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2356: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2367: Test failed: Link did not change casing on existing target file: got L"foo3368.tmp" file.c:2399: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2434: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2472: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2522: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2559: Test failed: res expected STATUS_OBJECT_NAME_COLLISION or STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2599: Test failed: res expected STATUS_OBJECT_NAME_COLLISION or STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2637: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2676: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2716: Test failed: res expected STATUS_OBJECT_NAME_COLLISION or STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2756: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2798: Test failed: res expected STATUS_FILE_IS_A_DIRECTORY, got c0000003 file.c:2833: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2867: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2901: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2903: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2908: Test failed: file should exist file.c:2942: Test failed: got status c0000003 file.c:2948: Test failed: got io status 0xdeadbeef file.c:2950: Test failed: got status c0000003 file.c:2976: Test failed: got status c0000003 file.c:2982: Test failed: got io status 0xdeadbeef file.c:2984: Test failed: got status c0000003 file.c:2992: Test failed: Link did not change casing on same file: got L"foo3396.tmp" See https://test.winehq.org/data/patterns.html#ntdll:file Where 0xc0000003 == STATUS_INVALID_INFO_CLASS These failures are systematic and started happening on 2023-09-19. A bisect shows that these started with the commit below: commit 67479f8c2fc03c2043b8414bc063e671e36fdbda Author: Joel Holdsworth <joel(a)airwebreathe.org.uk> AuthorDate: Fri Sep 15 17:49:52 2023 +0100 ntdll/tests: Test both FileRenameInformation and FileRenameInformationEx in test_file_rename_information. Signed-off-by: Joel Holdsworth <joel(a)airwebreathe.org.uk> -- 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 55631] New: ntdll:file - test_file_rename_information fails on Windows 10 1607 and older
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55631 Bug ID: 55631 Summary: ntdll:file - test_file_rename_information fails on Windows 10 1607 and older Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:file - test_file_rename_information fails on Windows 10 1607 and older: file.c:1550: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1552: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1555: Test failed: file should not exist file.c:1558: Test failed: file should exist file.c:1565: Test failed: FileName expected L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F4E.tmp", got L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F4D.tmp" file.c:1594: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1624: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1626: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1629: Test failed: file should not exist file.c:1661: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1696: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:1731: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1733: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1736: Test failed: file should not exist file.c:1739: Test failed: file should exist file.c:1746: Test failed: FileName expected L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F68.tmp", got L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F57.tmp" file.c:1783: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:1827: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1865: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1899: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1901: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1904: Test failed: file should not exist file.c:1940: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:1979: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2017: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2058: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2093: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2127: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2161: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2163: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2166: Test failed: file should not exist file.c:2169: Test failed: file should exist file.c:2176: Test failed: FileName expected L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F8D.tmp", got L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F8C.tmp" file.c:2203: Test failed: got io status 0xdeadbeef file.c:2205: Test failed: got status c0000003 See https://test.winehq.org/data/patterns.html#ntdll:file Where 0xc0000003 == STATUS_INVALID_INFO_CLASS These failures are systematic and started happening on 2023-09-19. A bisect shows that they started with the commit below: commit 67479f8c2fc03c2043b8414bc063e671e36fdbda Author: Joel Holdsworth <joel(a)airwebreathe.org.uk> Date: Fri Sep 15 17:49:52 2023 +0100 ntdll/tests: Test both FileRenameInformation and FileRenameInformationEx in test_file_rename_information. Signed-off-by: Joel Holdsworth <joel(a)airwebreathe.org.uk> -- 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 55627] New: secur32:negotiate & secur32:ntlm crash from a NULL dereference on macOS
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55627 Bug ID: 55627 Summary: secur32:negotiate & secur32:ntlm crash from a NULL dereference on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com secur32:negotiate & secur32:ntlm crash from a NULL dereference on macOS: Unhandled exception: page fault on read access to 0x0000000000000008 in 64-bit code (0x0000017004f9ed). See https://test.winehq.org/data/patterns.html#secur32:negotiate https://test.winehq.org/data/patterns.html#secur32:ntlm Initially this looked like the same issue as secur32:secur32 (bug 55555), i.e. a missing libkrb5 library. But changes were made for that library and that test no longer crashes on macOS so this must be another issue. Also other secur32 test units don't crash. -- 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

[Bug 55528] New: Vitis 2020.1 can't find its libraries (cmd.exe bug with nested one-line if statement that sets PATH)
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55528 Bug ID: 55528 Summary: Vitis 2020.1 can't find its libraries (cmd.exe bug with nested one-line if statement that sets PATH) Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75087 --> https://bugs.winehq.org/attachment.cgi?id=75087 Terminal output Steps to reproduce: 1. Run `tar -xvf Xilinx_Unified_2020.1_0602_1208.tar.gz` 2. Run `wine Xilinx_Unified_2020.1_0602_1208/xsetup.exe` 3. When the installer complains that it can't connect to the internet, click Ignore 4. Run `XIL_PA_NO_REDIST_CHECK=1 wine 'C:\Xilinx\Vitis\2020.1\bin\vitis.bat'` The following errors are printed to the terminal: Syntax error Can't recognize ')' as an internal or external command, or batch script. 0138:err:module:import_dll Library libboost_filesystem.dll (which is needed by L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe") not found 0138:err:module:import_dll Library libboost_program_options.dll (which is needed by L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe") not found 0138:err:module:import_dll Library librdi_common.dll (which is needed by L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe") not found 0138:err:module:LdrInitializeThunk Importing dlls for L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe" failed, status c0000135 I was able to narrow down the problem to code in loader.bat that looks similar to this (this is a minimal example, these aren't the real variable names): set FOO=1 if %FOO% == 1 ( if %FOO% == 1 set PATH=C:\Xilinx\Vitis\2020.1\lib\win64.o;%PATH% if %FOO% == 1 ( echo %PATH% ) ) I don't know why Wine thinks that there is a syntax error in this code. There must be a bug in the command parser that is triggered by a nested one-line if statement that sets a variable. Registration is required to download Vitis. $ sha256sum Xilinx_Unified_2020.1_0602_1208.tar.gz a9e0f81a61eca260c4453ab93a8d17eac31956dd54d0d5fd74dc8b4f2727e3eb -- 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 55273] New: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55273 Bug ID: 55273 Summary: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709: wow64.c:783: Test failed: 0:0: wrong offset 4 wow64.c:783: Test failed: 0:1: wrong offset 6 wow64.c:783: Test failed: 0:2: wrong offset 4 wow64.c:783: Test failed: 0:3: wrong offset 6 wow64.c:783: Test failed: 0:4: wrong offset 4 wow64.c:783: Test failed: 0:5: wrong offset 6 wow64.c:783: Test failed: 0:6: wrong offset 4 wow64.c:783: Test failed: 0:7: wrong offset 6 wow64.c:783: Test failed: 1:0: wrong offset 16 wow64.c:783: Test failed: 1:1: wrong offset 14 wow64.c:783: Test failed: 1:2: wrong offset 12 wow64.c:783: Test failed: 1:3: wrong offset 10 wow64.c:783: Test failed: 1:4: wrong offset 8 wow64.c:783: Test failed: 1:5: wrong offset 6 wow64.c:783: Test failed: 1:6: wrong offset 4 wow64.c:783: Test failed: 1:7: wrong offset 18 wow64.c:783: Test failed: 2:0: wrong offset 8 wow64.c:783: Test failed: 2:1: wrong offset 6 wow64.c:783: Test failed: 2:2: wrong offset 4 wow64.c:783: Test failed: 2:3: wrong offset 10 wow64.c:783: Test failed: 2:4: wrong offset 8 wow64.c:783: Test failed: 2:5: wrong offset 6 wow64.c:783: Test failed: 2:6: wrong offset 4 wow64.c:783: Test failed: 2:7: wrong offset 10 wow64.c:783: Test failed: 3:0: wrong offset 16 wow64.c:783: Test failed: 3:1: wrong offset 14 wow64.c:783: Test failed: 3:2: wrong offset 12 wow64.c:783: Test failed: 3:3: wrong offset 10 wow64.c:783: Test failed: 3:4: wrong offset 8 wow64.c:783: Test failed: 3:5: wrong offset 6 wow64.c:783: Test failed: 3:6: wrong offset 4 wow64.c:783: Test failed: 3:7: wrong offset 18 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 so in this case it is just a coincidence. See also bug 55272 for ntdll:exception crashes that started at the same time on the same set of machines. -- 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 55241] New: The 64-bit winmm:capture & winmm:wave crash on Windows 8
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55241 Bug ID: 55241 Summary: The 64-bit winmm:capture & winmm:wave crash on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit winmm:capture & winmm:wave crash on Windows 8: capture.c:171: this is the last test seen before the exception 07d0:capture: unhandled exception c0000005 at 00007FFDC66DCF38 wave.c:686: this is the last test seen before the exception 0b14:wave: unhandled exception c0000005 at 00007FFDC66DCF38 See https://test.winehq.org/data/patterns.html#winmm:capture https://test.winehq.org/data/patterns.html#winmm:wave This started with the GitLab CI's switch to Debian 12 (bookworm) for the build system: * The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM produces no failures when run on Windows while GitLab CI's binary for the same Wine version produces this set of failures. * And the TestBot runs the official WineTest builds on its Windows VMs which is why the failures appeared on 2023-07-10 which corresponds to this commit: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. Now the question is whether the new build environment revealed a preexisting bug in Wine, or if the new build environment itself is broken, or if the bug is elsewhere such as in the MinGW compiler. This is also likely the same issue as bug 55240. -- 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 55211] New: Print file not truncated when printing to file in FrameMaker 8
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55211 Bug ID: 55211 Summary: Print file not truncated when printing to file in FrameMaker 8 Product: Wine Version: 8.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- A existing print file ist not truncated when printing to the same file again. So when printing a smaller document to the print file which was generated for a larger file, the resultung file contains garbage at its end. This happens in Framemaker 8 and may happen in other apps too. To reproduce - Install Framemaker from the given URL - Print the attached Document Large.fm to a file (select print to file in the printer dialog). Check the size of the generated file. - Print the attached Document Small.fm to the same file generated in the previous step. Check again the size of the file - its the same. Depending on the used Postscript interpreter reading the file fails because of the garbage at the files end. This is simple to see when using different documents as descibed above. When printing existing documents again after (even small) changes the resulting print file may be garbage without notice. -- 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 13

[Bug 54744] New: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54744 Bug ID: 54744 Summary: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows: taskbarlist.c:61: Test failed: Got hr 0x80004001. taskbarlist.c:66: Test failed: Got hr 0x80004001. See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist Where 0x80004001 == E_NOTIMPL On average this happens about once every other month on recent Windows 10 versions: * 2022-08-31 on w1064-tsign-64 (21h2) * 2022-11-14 on w1064-tsign-32 (21h2) * 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2) * 2023-02-06 on w10pro64-rx550-64 (22h2) * 2023-03-27 on w10pro64-ar-64 (21h1) -- 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 54069] New: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54069 Bug ID: 54069 Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+. ddraw7.c:18954: Test failed: Got unexpected color 0x00000040. and ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Notes: * There is no evidence of this happening on Windows 11. * This seems to only happen with Microsoft's "Microsoft Basic Display Adapter" driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA PCI passthrough configurations. * The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff result seems to only happen on Windows 10 2004+. * ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but don't have this failure. -- 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 43185] New: "Battle Bugs" game in unresponsive once game starts
by wine-bugs＠winehq.org Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: "Battle Bugs" game in unresponsive once game starts Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matt(a)nightrealms.com Distribution: --- Created attachment 58457 --> https://bugs.winehq.org/attachment.cgi?id=58457 Wine output from before starting the game When playing the free game "Battle Bugs" (https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game start screen loads just fine, and pressing an indicated key starts the game just fine, but once the game starts nothing is moving and the game doesn't respond to any keys. Got the same results with both versions of the executable, and both WINEARCH unspecified or set to win32 -- 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 43017] New: Unreal Tournament 2004/UT2004.exe crashes due to " intel_do_flush_locked failed: Cannot allocate memory"
by wine-bugs＠winehq.org Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=43017 Bug ID: 43017 Summary: Unreal Tournament 2004/UT2004.exe crashes due to "intel_do_flush_locked failed: Cannot allocate memory" Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Unreal Tournament 2004/UT2004.exe crashes due to `intel_do_flush_locked failed: Cannot allocate memory` the debug output of PlayOnLinux reads ``` [05/12/17 23:55:35] - Running wine-2.7 UT2004.exe (Working directory : /home/richter/.PlayOnLinux/wineprefix/UnrealT2004/drive_c/Program Files/Unreal Tournament 2004/System) err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142 fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32e540,0x32e53c): stub fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:create_server class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject no class object {96749377-3391-11d2-9ee3-00c04f797396} could be created for context 0x7 fixme:win:EnumDisplayDevicesW ((null),0,0x32bc98,0x00000000), stub! fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:imm:ImmReleaseContext (0x1007c, 0x2165e0): stub fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x6404c88, 0x32ccc4 err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1042267284)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1082643741)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129305379)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1017464658)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106373278)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1061644189)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103102115)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102202262)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127878391)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1133393126)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064431753)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056334452)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103590910)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1128011843)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1012511863)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129177136)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064579615)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107545964)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127492263)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1131588260)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1009667614)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064940315)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102388947)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107645235)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127352012)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106599611)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065065837)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056114040)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1104285584)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127422744)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1029644321)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1126051816)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065075311)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". intel_do_flush_locked failed: Cannot allocate memory ``` -- 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 55656] New: user32:dialog - test_IsDialogMessage() fails in the hi-u8 and mx-MX locales on Windows
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55656 Bug ID: 55656 Summary: user32:dialog - test_IsDialogMessage() fails in the hi-u8 and mx-MX locales on Windows 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:dialog - test_IsDialogMessage() fails in the hi-u8 and mx-MX locales on Windows: w10pro64-hi-u8: dialog.c:869: Test failed: Got unexpected wparam 0x97ade5. dialog.c:580: Test failed: Got unexpected wparam 0xfffd. w10pro64-mx-MX: dialog.c:867: Test failed: Got unexpected wparam 0x3f. dialog.c:578: Test failed: Got unexpected wparam 0x3f. See https://test.winehq.org/data/patterns.html#user32:dialog The 'mx-MX' locale is a mix of locales and may indicate the test only succeeds when all the Windows locales match. For reference, mx-MX uses the following settings: SystemDefaultLCID 0411 UserDefaultLCID 040c ThreadLocale 0411 SystemPreferredUILanguages 0412,0409 UserDefaultUILanguage 0412 ThreadUILanguage 0412 KeyboardLayout 00000000040A0C0A Country 231 ACP 932 A bisect shows that both sets of failures started with the commit below: commit fe594a83d4a87fccaced20372a83ecb2ef28de6c Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri Aug 18 11:39:19 2023 +0800 user32/tests: Test IsDialogMessageA() converting ASCII WM_CHAR messages. -- 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 55652] New: A FindResourceW() call prevents windows.applicationmodel:model from running on Windows 8
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55652 Bug ID: 55652 Summary: A FindResourceW() call prevents windows.applicationmodel:model from running on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com A FindResourceW() call prevents windows.applicationmodel:model from running on Windows 8: model.c:0: Tests skipped: missing entry point (details below) | windows.applicationmodel_test.exe - Entry Point Not Found | The procedure entry point FindResourceW could not be located in the dynamic link library C:\Users\winetest\Documents\windows.applicationmodel_test.exe. See https://test.winehq.org/data/patterns.html#windows.applicationmodel:model This is caused by this commit: commit 8609fef5c822e32998725bad58582764d289c194 Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Wed Aug 23 11:21:33 2023 +0200 windows.applicationmodel/tests: Test IPackageManager_RegisterPackageAsync. -- 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 55236] New: scrrun:dictionary - test_hash_value() gets bad hashes on Windows
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55236 Bug ID: 55236 Summary: scrrun:dictionary - test_hash_value() gets bad hashes on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com scrrun:dictionary - test_hash_value() gets bad hashes on Windows: dictionary.c:676: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:686: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:695: Test failed: got hash 0x2db, expected 0x2da dictionary.c:721: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:732: Test failed: got hash 0x2eb, expected 0x2ea dictionary.c:742: Test failed: got hash 0x2db, expected 0x2da See https://test.winehq.org/data/patterns.html#scrrun:dictionary Note that the hash values change with every run causing false positives. -- 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 55108] New: xaudio2_8:xaudio2 fails on Windows 10+
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55108 Bug ID: 55108 Summary: xaudio2_8:xaudio2 fails on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com xaudio2_8:xaudio2 fails on Windows 10+: xaudio2.c:1218: Test failed: Got hr 0x80004002. See https://test.winehq.org/data/patterns.html#xaudio2_8:xaudio2 Note that this is the same failure as what happened on Windows 8 in the late stages described in bug 55016. A bisect shows that this failure started with the commit below: commit e8b0e7c1fcf090ba80c543f68b0bdae185316327 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Jun 16 15:13:14 2023 -0500 xaudio2/tests: Fix the IID_IXAudio28 declaration. This was accidentally copied from the 2.9 version instead in 14c44d0b0. -- 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 54791] New: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54791 Bug ID: 54791 Summary: explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:nstc - test_events() sometimes gets unexpected events on Windows 7. This can either be a single event but it can also happen multiple times for multiple events: nstc.c:2265: Test failed: Got event 4, count 1 or nstc.c:1906: Test failed: Got event 7, count 0 nstc.c:1908: Test failed: Got event 4, count 0 nstc.c:1912: Test failed: Got event 4, count 1 nstc.c:1912: Test failed: Got event 7, count 1 nstc.c:1912: Test failed: Got event 12, count 8 See https://test.winehq.org/data/patterns.html#explorerframe:nstc This first happened on 2022-12-07 and has been happening roughly once every three week since. So it's probably caused by a commit in the fall of 2022. -- 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 54441] New: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54441 Bug ID: 54441 Summary: windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com windows.media.speech:speech - test_Recognition() sometimes gets unexpected recognizer state on Windows 10: speech.c:1775: Test failed: recog_state was 0. See https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure started on 2023-01-25. -- 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 9

[Bug 54156] New: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54156 Bug ID: 54156 Summary: comctl32:edit & user32:edit - test_paste() sometimes gets an empty string on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:edit - test_paste() sometimes gets an empty string on Windows edit.c:3238: Test failed: got 0 See https://test.winehq.org/data/patterns.html#comctl32:edit This happens on Windows 10 1809 to 21H2 a bit less than 3 times per month. Where 0 is the length of the string in the field we pasted to. So that field is empty instead of having received the string we pasted. We can also get this failure in user32:edit (2022-11-15 w10pro64v1809): edit.c:3211: Test failed: got 0 See https://test.winehq.org/data/patterns.html#user32:edit But the case above is for the single-line to single-line case and there is also the same issue happening in the multi-line to multi-line case (2022-10-25 w11pro64-amd): edit.c:3240: Test failed: got 0 So it's a pretty general, if rare (only 4 known instances in 6 months), problem. Note that while one could expect this to be caused by yet another OpenClipboard() failure, like in bug 53276, there is no failure message indicating this to be the case. -- 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 53276] New: user32:edit - test_paste() sometimes fails to access the clipboard on Windows
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=53276 Bug ID: 53276 Summary: user32:edit - test_paste() sometimes fails to access the clipboard on Windows 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:edit - test_paste() sometimes fails to access the clipboard on Windows: edit.c:3222: Test failed: expected 1, got 0 le=5 edit.c:3224: Test failed: expected 1, got 0 edit.c:3226: Test failed: expected 00000000008500A8, got 0000000000000000 edit.c:3228: Test failed: expected 1, got 0 edit.c:3234: Test failed: got 21 edit.c:3240: Test failed: got 21 https://test.winehq.org/data/patterns.html#user32:edit Where 5 is ERROR_ACCESS_DENIED and indicates that the clipboard has already been opened in another thread, process, etc. This happens a lot on machines with an AMD GPU due to known interference from the Radeon driver (see bug 47888). But it also happens sometimes on machines with an Nvidia GPU (cw-gtx560) and even on pure QEmu VMs such as w1064-1qxl (or fgtb-w10pro64). So there is either some other source of interference, maybe from some Windows component, or an issue (a race condition?) in the test itself. It would be nice to identify the source of interference, if any, to see if it can be neutralized. But maybe the only solution is to work around the issue as in user32:clipboard (see commit 316eec8f6658). -- 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 52641] New: dsdmo has missing implementation causing game crash on loaded
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=52641 Bug ID: 52641 Summary: dsdmo has missing implementation causing game crash on loaded Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw Distribution: --- log has shown a missing implementation on dsdmo dll this cause game crash when loading Affect game: Feeding Frenzy 2 Log: 0290:warn:dsdmo:effect_inner_QueryInterface {6d6cbb60-a223-44aa-842f-a2f06750be6d} not implemented; returning E_NOINTERFACE. -- 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 55606] New: Finale 27 printing - incorrect linecap
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55606 Bug ID: 55606 Summary: Finale 27 printing - incorrect linecap Product: Wine Version: 8.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineps.drv Assignee: wine-bugs(a)winehq.org Reporter: davech(a)t-online.de Distribution: --- Wine 8.16 uses 'setlinecap' incorrectly in the postscript output. This is correct in wine 7.0.2 -- 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 54699] New: Motorola Ready For Assistant does not start, RoOriginateLanguageException in Windows.Networking
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54699 Bug ID: 54699 Summary: Motorola Ready For Assistant does not start, RoOriginateLanguageException in Windows.Networking Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lischak(a)gmail.com Distribution: --- Created attachment 74209 --> https://bugs.winehq.org/attachment.cgi?id=74209 install+run of v04.0.0.010.000 on Wine 8.4 Motorola Ready For Assistant is a software for interfacing with Motorola smartphones from desktop, allowing either phone screen mirror or a full-sized Android-powered desktop similar to Samsung DeX. The installer appears to finish successfully, but the application will not start. This is a continuation of Bug 54495 in which two previous issues were fixed (thanks!). The installation file is freely downloadable: https://web.archive.org/web/20230214220515/https://download.lenovo.com/leno… cd ~/Downloads WINEPREFIX=~/.wine_readyfor wine ReadyFor_setup_04.0.0.010.000.exe cd ~/.wine_readyfor/drive_c/Program\ Files/Lenovo/Ready\ For\ Assistant WINEPREFIX=~/.wine_readyfor wine ReadyFor.exe Attaching log from installation and from a follow-up run. Env: Fedora 37, using the appropriate official WineHQ repo. Note: The software is apparently only available via MS Store nowadays, but the Store install just downloads a normal Win32 .exe from Motorola/Lenovo's servers in the background. -- 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 12

[Bug 55272] New: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=55272 Bug ID: 55272 Summary: The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit ntdll:exception crashes on Windows 10 1607 & 1709: exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 exception.c:3537: vect. handler c0000005 addr:000002858E4C0000 ntdll:exception:0dd8 done (-1073741819) in 0s 6581B See https://test.winehq.org/data/patterns.html#ntdll:exception Where -1073741819 == 0xC0000005 == STATUS_ACCESS_VIOLATION The crashes started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 in this case it is just a coincidence. Note that before that ntdll:exception was exiting silently on Windows 8 & 10 <= 1809, see bug 55111. These two issues may be one and the same, just producing different results due to changes in the binary layout. -- 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 41645] New: recursive invokation of __clone+0x6d() in libc.so.6 ( 0x00000000) in start_thread+0xe4() in libpthread.so.0 (0x0608f428)
by wine-bugs＠winehq.org Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=41645 Bug ID: 41645 Summary: recursive invokation of __clone+0x6d() in libc.so.6 (0x00000000) in start_thread+0xe4() in libpthread.so.0 (0x0608f428) Product: Wine Version: 1.9.22 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Created attachment 56020 --> https://bugs.winehq.org/attachment.cgi?id=56020 Backtrace created by wine crash handler There seems to be a recursive invokation inside `__clone+0x6d()` in `start_thread+0xe4() in libpthread.so.0 (0x0608f428)`, see attached backtrace. -- 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 19

[Bug 54783] New: cryptowinrt:crypto - test_Credentials_Statics() sometimes gets unexpectedly high refcount in Wine
by WineHQ Bugzilla Oct. 16, 2023

Oct. 16, 2023

https://bugs.winehq.org/show_bug.cgi?id=54783 Bug ID: 54783 Summary: cryptowinrt:crypto - test_Credentials_Statics() sometimes gets unexpectedly high refcount in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- cryptowinrt:crypto - test_Credentials_Statics() sometimes gets unexpectedly high refcount in Wine: crypto.c:321: Test failed: got ref 3. crypto.c:323: Test failed: got ref 2. See https://test.winehq.org/data/patterns.html#cryptowinrt:crypto Where 2 and 1 was expected respectively. There are 4 known instances so far but this test has only been running since 2023-02-23: * 2023-02-27 on MR2262 * 2023-03-15 on fg-deb64-wow64 * 2023-03-23 on fg-deb64-wow32 * 2023-04-04 on MR2576 -- 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