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

[Bug 53974] New: d3drm:d3drm sometimes crashes after failing to create the IDirect3DRMDevice* interface in Wine
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53974 Bug ID: 53974 Summary: d3drm:d3drm sometimes crashes after failing to create the IDirect3DRMDevice* interface in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3drm:d3drm sometimes crashes after failing to create the IDirect3DRMDevice* interface in Wine: d3drm.c:4600: Test failed: Cannot create IDirect3DRMDevice interface, hr 0x8007000e. d3drm.c:4602: Test failed: expected ref2 > ref1, got ref1 = 1 , ref2 = 1. d3drm.c:4604: Test failed: Expected surface_ref2 > surface_ref1, got surface_ref1 = 1, surface_ref2 = 1. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0040e52b). [...useless backtrace...] d3drm.c:4776: Test failed: Cannot create IDirect3DRMDevice2 interface, hr 0x8007000e. d3drm.c:4778: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1. d3drm.c:4782: Test failed: Expected surface_ref2 > surface_ref1, got surface_ref1 = 1, surface_ref2 = 1. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x004106c1). [...useless backtrace...] d3drm.c:4407: Test failed: Cannot create IDirect3DRMDevice3 interface, hr 0x8007000e. d3drm.c:4409: Test failed: expected ref3 > ref1, got ref1 = 1 , ref3 = 1. d3drm.c:4413: Test failed: expected cref2 > cref1, got cref1 = 1 , cref2 = 1. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0041290a). [...useless backtrace...] See https://test.winehq.org/data/patterns.html#d3drm:d3drm The two "expected..." failures are not always present. This has been seen on debian11, debiant but also fgtb-debian11 and gitlab-debian. So it's not specific to dual-screen configurations nor to QEmu's QXL driver. But it seems to only happen on "virtual GPUs" (gitlab-debian uses Xorg's dummy driver). -- 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 53528] New: ntdll:info - test_query_kerndebug() fails on Windows 8 to 10 1709
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53528 Bug ID: 53528 Summary: ntdll:info - test_query_kerndebug() fails on Windows 8 to 10 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:info - test_query_kerndebug() fails on Windows 8 to 10 1709: info.c:1097: Test failed: Expected STATUS_SUCCESS, got 80000002 info.c:1102: Test failed: Expected STATUS_SUCCESS, got 80000002 https://test.winehq.org/data/patterns.html#ntdll:info The failures started on 2022-07-26. -- 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 54003] New: vbscript:run sometimes fails on Windows UTF-8 locales
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54003 Bug ID: 54003 Summary: vbscript:run sometimes fails on Windows UTF-8 locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com vbscript:run sometimes fails on UTF-8 locales: === w10pro64_en_AE_u8 (64 bit report) === vbscript: run.c:1206: Test failed: api.vbs: L"Err.number = 0" run.c:1206: Test failed: api.vbs: L"Err.description = " run.c:1206: Test failed: api.vbs: L"Err.number = 0" See https://gitlab.winehq.org/wine/wine/-/merge_requests/1534 Strangely enough so far this has not happened in the nightly WineTest runs but it did happen in another unrelated merge request (MR!1561). According to Nikolay (probably s/testChrError/testCStrError/): > This is happening on utf-8 locale, in testChrError(). > Needs to be fixed, but unrelated to this MR. -- 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 10

[Bug 54509] New: psapi:psapi_main - The 64-bit test_EnumProcessModules() gets unexpected third module on Windows 11
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54509 Bug ID: 54509 Summary: psapi:psapi_main - The 64-bit test_EnumProcessModules() gets unexpected third module on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - The 64-bit test_EnumProcessModules() gets unexpected third module on Windows 11: psapi_main.c:185: Test failed: third DLL in wow64 should be one of wow*.dll (kernel32.dll) See https://test.winehq.org/data/patterns.html#psapi:psapi_main This test and failure was introduced by the commit below: commit 00bf7293af13f3766c6c839f0125785ac9084de8 Author: Eric Pouech <eric.pouech(a)gmail.com> AuthorDate: Tue Feb 14 11:07:01 2023 +0100 psapi: Add more tests for EnumProcessModules(). Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> -- 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 54539] New: Starcraft Remastered Game Initialization Failed
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54539 Bug ID: 54539 Summary: Starcraft Remastered Game Initialization Failed Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: uberdude555(a)yahoo.com Distribution: --- Created attachment 74080 --> https://bugs.winehq.org/attachment.cgi?id=74080 stdout I updated from wine 7.0-rc3 to 8.2, and when I try to start StarCraft now I see an error dialog box with text "Game Initialization Failed: T". I tried running the exe directly (rather than through the Battle.net client) and saw the same error with only the four lines attached written to the terminal. The AppDB page shows at least three other users experiencing the same issue from version 8.1 and possibly earlier: https://appdb.winehq.org/objectManager.php?sClass=version&iId=35171. -- 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 53172] New: advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8 system locales
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=53172 Bug ID: 53172 Summary: advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8 system locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry - test_enum_value() has a pair of rare failures in UTF-8 system locales: registry.c:558: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of 'foobar' or x's, data_count=21 registry.c:576: Test failed: data set to 'xxxxxxxxxxxxxxxxxxxx' instead of 'foobar' or x's, data_count=21 https://test.winehq.org/data/patterns.html#advapi32:registry The line 558 and 576 failures happen about with the same frequency (~13% each) but independently from each other so that most times there is at most one in the report. And they only happen in the TestBot's two UTF-8 test configurations: w10pro64-en-AE-u8 and w10pro64-hi-u8. -- 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 54649] New: windows.perception.stub:perception - Windows 10 1607 does not have ISpatialSurfaceObserverStatics2
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54649 Bug ID: 54649 Summary: windows.perception.stub:perception - Windows 10 1607 does not have ISpatialSurfaceObserverStatics2 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.perception.stub:perception - Windows 10 1607 does not have ISpatialSurfaceObserverStatics2: perception.c:76: Test failed: got hr 0x80004002. perception.c:76: this is the last test seen before the exception 088c:perception: unhandled exception c0000005 at 00401483 See https://test.winehq.org/data/patterns.html#windows.perception.stub:percepti… Where 0x80004002 == E_NOINTERFACE This test was introduced in the commit below: commit 006bc33c57c96bd733147c4088d36bfc14da907e Author: Mohamad Al-Jaf <mohamadaljaf(a)gmail.com> AuthorDate: Thu Feb 23 03:50:15 2023 -0500 windows.perception.stub: Add ISpatialSurfaceObserverStatics2 stub interface. -- 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 54504] New: psapi:psapi_main - The 32-bit test_EnumProcessModules() gets a partial copy error on Windows 11
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54504 Bug ID: 54504 Summary: psapi:psapi_main - The 32-bit test_EnumProcessModules() gets a partial copy error on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - The 32-bit test_EnumProcessModules() gets a partial copy error on Windows 11: psapi_main.c:133: Test failed: got 0, error 299 psapi_main.c:134: Test failed: expected non-NULL module See https://test.winehq.org/data/patterns.html#psapi:psapi_main Where 299 == ERROR_PARTIAL_COPY This failure is specific to the 32-bit tests running on Windows 11, that is the 64-bit test has other (possibly related) failures, and Windows 10 and lower don't have failures. Also this failure has been present ever since the Windows 11 VM was added. -- 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 10

[Bug 54531] New: jsproxy:jsproxy crashes on Windows 11
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54531 Bug ID: 54531 Summary: jsproxy:jsproxy crashes on Windows 11 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 jsproxy:jsproxy crashes on Windows 11: jsproxy.c:52: Test failed: got 3735928559 jsproxy.c:56: Test failed: got 3735928559 jsproxy.c:59: Test failed: got 3735928559 jsproxy.c:60: this is the last test seen before the exception 054c:jsproxy: unhandled exception c0000005 at 004013FA See https://test.winehq.org/data/patterns.html#jsproxy:jsproxy Where 3735928559 == 0xdeadbeef So InternetGetProxyInfo() fails but does not set LastError. Furthermore the proxy pointer is not initialized either so the test crashes when trying to free it. -- 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 54019] New: The 64-bit ntdll:wow64 fails on Windows 11
by WineHQ Bugzilla 17 Mar '23

17 Mar '23

https://bugs.winehq.org/show_bug.cgi?id=54019 Bug ID: 54019 Summary: The 64-bit ntdll:wow64 fails on Windows 11 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:wow64 fails on Windows 11. There are two failure modes: wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 / 00000013640C5000 wow64.c:273: Test failed: wrong len 0 wow64.c:290: Test failed: wrong len 0 wow64.c:312: Test failed: wrong len 0 wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 75cec0-75d884 wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210 wow64.c:321: Test failed: wrong CommandLine ptr 0 / 75cec0-75d884 wow64.c:321: Test failed: wrong CommandLinelen 0 / 66 wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 75cec0-75d884 wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210 wow64.c:323: Test failed: wrong Desktop ptr 0 / 75cec0-75d884 wow64.c:323: Test failed: wrong Desktoplen 0 / 30 wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 75cec0-75d884 wow64.c:326: Test failed: wrong size 0 / 3222 wow64.c:338: Test failed: wrong len 0 wow64.c:339: Test failed: BeingDebugged is 0 or with 2 extra failures and different values: wow64.c:269: Test failed: wrong Tib.ExceptionList 0000000000000000 / 000000A7ECDDA000 wow64.c:273: Test failed: wrong len 0 wow64.c:290: Test failed: wrong len 0 wow64.c:291: Test failed: BeingDebugged is 117 wow64.c:309: Test failed: wrong ptr32 0000000000000000 / 00000298B3F80000 wow64.c:312: Test failed: wrong len 0 wow64.c:320: Test failed: wrong ImagePathName ptr 0 / 0-9c4 wow64.c:320: Test failed: wrong ImagePathNamelen 0 / 210 wow64.c:321: Test failed: wrong CommandLine ptr 0 / 0-9c4 wow64.c:321: Test failed: wrong CommandLinelen 0 / 66 wow64.c:322: Test failed: wrong WindowTitle ptr 0 / 0-9c4 wow64.c:322: Test failed: wrong WindowTitlelen 0 / 210 wow64.c:323: Test failed: wrong Desktop ptr 0 / 0-9c4 wow64.c:323: Test failed: wrong Desktoplen 0 / 30 wow64.c:324: Test failed: wrong ShellInfo ptr 0 / 0-9c4 wow64.c:326: Test failed: wrong size 0 / 3112 wow64.c:338: Test failed: wrong len 0 wow64.c:339: Test failed: BeingDebugged is 117 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The values are pretty stable from one run to the next but do change from time to time (causing false positives). Note also that the 32-bit version fails on Windows 11 too. -- 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