December 2022 - Wine-bugs - list.winehq.org

[Bug 50043] New: Kholat from GOG does not launch anymore
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50043 Bug ID: 50043 Summary: Kholat from GOG does not launch anymore Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Created attachment 68493 --> https://bugs.winehq.org/attachment.cgi?id=68493 Message box I get the attached message box instead. This is a regression but I can't bisect as I the following errors with older wine versions: wine: could not find __wine_start_process in kernel32.dll, status c000007a 0024:err:environ:run_wineboot failed to start wineboot c000007a -- 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 23

[Bug 50315] New: Silent Hill 2 failed to install -installshield extraction error
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50315 Bug ID: 50315 Summary: Silent Hill 2 failed to install -installshield extraction error Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)gmail.com Distribution: --- Created attachment 68897 --> https://bugs.winehq.org/attachment.cgi?id=68897 screenshot installshield error message Hello, with last wine version 6, Silent Hill 2 failed to install with an installshield extraction error (cf screenshot joined). This bug is new, I can not reproduce it with Wine 5.x Nothing interesting in terminal log, only that lines: 010c:fixme:file:NtLockFile I/O completion on lock not implemented yet Initial process has exited (return code: 0) 010c:err:ole:CoReleaseMarshalData StdMarshal ReleaseMarshalData failed with error 0x8001011d -- 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 54105] New: taskschd:scheduler fails on Windows 10 1607+
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54105 Bug ID: 54105 Summary: taskschd:scheduler fails on Windows 10 1607+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: taskschd Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com taskschd:scheduler fails on Windows 10 1607+: scheduler.c:786: Test failed: DeleteTask error 0x80070002 See https://test.winehq.org/data/patterns.html#taskschd:scheduler This new failure is caused by the following commit: commit 7acd3aa429f2d45d96f4699906dc81e47ebd9c13 Author: Sven Baars <sbaars(a)codeweavers.com> Date: Wed Dec 7 17:19:48 2022 +0100 taskschd/tests: Fix a test failure on w1064v1507. This failure was also detected by the TestBot in MR!1732 but it was merged anyway. -- 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 54014] New: advapi32:security sometimes exits prematurely in Wine
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54014 Bug ID: 54014 Summary: advapi32:security sometimes exits prematurely in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- advapi32:security sometimes exits prematurely in Wine: security.c:5550: Test marked todo: expected execute access 0x120000, got 0xdeadbeef advapi32:security:03a8 done (0) in 0s 6852B What's missing here is the "tests executed..." summary line which typically indicates some underlying library called "exit()". This is usually accompanied with a warning message complaining about something being wrong but there is no trace of such a message in the task log. There are some strange aspects to this: * There is no record of it ever happening in the nightly WineTest runs. * But it impacted 9 merge requests so far: 2022-11-28 MR!1575 2022-11-29 MR!1595 MR!1583 MR!1594 2022-11-25 MR!1537 2022-11-16 MR!1379 2022-11-14 MR!1363 MR!1356 2022-11-13 MR!1315 When it happens the report shows 4 instances of the 5550 todo. Comparing that to a successful run indicates the early exit happened between the end of test_kernel_objects_security() and the start of test_CreateWellKnownSid(). Maybe a piece of good news: advapi32:security crashes with WINEDEBUG=heap. However that crash happens in test_CreateDirectoryA() instead of the expected place. So it may be an unrelated 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.

1 2

[Bug 54032] New: user32:msg - test_broadcast() sometimes fails due to ERROR_INVALID_PARAMETER on w7pro64
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54032 Bug ID: 54032 Summary: user32:msg - test_broadcast() sometimes fails due to ERROR_INVALID_PARAMETER on w7pro64 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:msg - test_broadcast() sometimes fails due to ERROR_INVALID_PARAMETER on w7pro64: msg.c:17400: Test failed: 5: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,0: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,1: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,2: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,3: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,8: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,9: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,10: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,11: message ffff, got 0, error 87 msg.c:17405: Test failed: 5,12: message ffff, got 0, error 87 See https://test.winehq.org/data/patterns.html#user32:msg Notes: * This is specific to w7pro64 and happens roughly twice a month. * The first known instance dates back to 2022-08-17 and there was none in the 2 months prior. * The w7pro64 snapshot dates back to 2021-08-23. So the conclusion is that something changed in Wine back in August that causes these failures. Since the logs show no change to that test in that timeframe (the next day does not count), it must be caused by a change in another test :-( -- 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 2

[Bug 54193] New: dinput:force_feedback - test_windows_gaming_input() sometimes fails in Wine
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54193 Bug ID: 54193 Summary: dinput:force_feedback - test_windows_gaming_input() sometimes fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- dinput:force_feedback - test_windows_gaming_input() sometimes fails in Wine. For instance: * 2022-12-20 on debian11-win32-he-IL (6 failures) force_feedback.c:5932: Test failed: got status 0 force_feedback.c:5932: Test marked todo: got error 0 force_feedback.c:5932: Test marked todo: GetResults returned 0x8000000e force_feedback.c:5937: Test failed: handler not invoked force_feedback.c:5938: Test failed: got async 00000000 force_feedback.c:5939: Test failed: got status 0 force_feedback.c:5945: Test failed: got status 2 force_feedback.c:5945: Test marked todo: got error 0 force_feedback.c:5945: Test marked todo: GetResults returned 0x8000000e force_feedback.c:4703: iface 006C9128, async 019BEEE8, status 4 force_feedback.c:4703: iface 006C9128, async 019C39C8, status 1 force_feedback.c:4705: Test failed: invoked twice force_feedback.c:4703: iface 006C9128, async 019C39C8, status 4 * 2022-11-24 fgtb-debian11-wow64 (3 failures) force_feedback.c:5839: Test failed: got status 0 force_feedback.c:5839: Test marked todo: got error 0 force_feedback.c:5839: Test marked todo: GetResults returned 0x8000000e force_feedback.c:5844: Test failed: handler not invoked force_feedback.c:4615: iface 00000000006C8EB0, async 0000000001D77D50, status 3 force_feedback.c:5845: Test failed: got async 0000000000000000 force_feedback.c:5852: Test marked todo: got error 0x8007001e force_feedback.c:5852: Test marked todo: GetResults returned 0x8007001e * 2022-11-01 debiant-wow64 (1 failure) force_feedback.c:5776: Test marked todo: get_SupportedAxes returned 0x80004001 force_feedback.c:5778: Test marked todo: got axes 0xdeadbeef force_feedback.c:5796: Test failed: got status 0 See https://test.winehq.org/data/patterns.html#dinput:force_feedback The oldest known instance dates back to 2022-09-01 (same 6 failures as above) and there has only been a total of 5 instances to date (in the nightly WineTest runs). So these failures are probably caused by a change some time in August. -- 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 1

[Bug 40250] New: Stunt GP too fast timer for stunts, waterfall/screen animation and starting screens
by wine-bugs＠winehq.org 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=40250 Bug ID: 40250 Summary: Stunt GP too fast timer for stunts, waterfall/screen animation and starting screens Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 10mkudela(a)gmail.com Distribution: --- In the game time frame required to press Shift key to make stunt is much smaller then in Windows. Also waterfall animation and loading screens are much faster then in Windows. Everything else is at the same speed. One additional animation is faster as well: speed of the text on screen in Germany location is faster as well, but it's speed is changing from what I have noticed. There is probably a timer somewhere that is ticking faster then it should be, and that is used by all those elements. This bug was tested on 1.9.4 version of Wine, but it is also present on older versions. -- 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 53716] New: Warlords 3: Darklords Rising: opening dialog window has messed up colors
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53716 Bug ID: 53716 Summary: Warlords 3: Darklords Rising: opening dialog window has messed up colors Product: Wine Version: 7.14 Hardware: x86-64 URL: https://www.fileplanet.com/archive/p-27637/Warlords-II I-Darklords-Rising-Demo OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 47dd8a6a9b1193ec1656cdf04117b94a3cf07025 Distribution: --- Created attachment 73147 --> https://bugs.winehq.org/attachment.cgi?id=73147 Before -> after image This was tested with GOG.com version of the game but can also be reproduced with the original demo version. When you start the game the opening dialog (where you select game mode/screen resolution) has strange colors. The demo uses a 16-bit installer which is currently affected by bug #53646. Winver needs to be Win95/98. This is a regression from Wine-7.14, caused by commit 47dd8a6a9b1193ec1656cdf04117b94a3cf07025 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Sun Jul 10 16:15:10 2022 +0200 win32u: Use syscall interface for more user painting functions. Nothing obvious is visible in the terminal output. Darkdemo.zip (20M) md5sum: 30f5908552d720e8b5361e0656772da8 wine-7.17-224-g52a83ffe4ef -- 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 1

[Bug 53256] New: user32:win - test_window_from_point() and test_mouse_input() sometimes fail on Windows 10 2009+
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53256 Bug ID: 53256 Summary: user32:win - test_window_from_point() and test_mouse_input() sometimes fail on Windows 10 2009+ 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_window_from_point() and test_mouse_input() sometimes fail on Windows 10 2009+: win.c:10238: Test failed: button under static window didn't get WM_LBUTTONUP 02fc:win: 10 tests executed (0 marked as todo, 1 failure), 0 skipped. ... win.c:4549: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0204 win.c:4554: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205 win.c:4559: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0206 win.c:4564: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205 win.c:4580: Test failed: hwnd 00000000007902D6/00000000007902D6 message 0204 win.c:4584: Test failed: hwnd 00000000007902D6/00000000007902D6 message 0205 win.c:4593: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0204 win.c:4596: Test failed: hwnd 00000000009C02AE/00000000009C02AE message 0205 win.c:4629: Test failed: hwnd 00000000005C0340/00000000005C0340 message 00a4 win.c:4635: Test failed: hwnd 00000000005C0340/00000000005C0340 message 00a5 win.c:4642: Test failed: hwnd 00000000005C0340/00000000005C0340 message 0206 win.c:4644: Test failed: wparam 2 win.c:4655: Test failed: hwnd 00000000005C0340/00000000005C0340 message 0205 https://test.winehq.org/data/patterns.html#user32:win Where: * 204 == WM_RBUTTONDOWN * 205 == WM_RBUTTONUP * 206 == WM_RBUTTONDBLCLK Although they seem unrelated, the test_window_from_point() failure and the set of 13 test_mouse_input() failures always happen together which means they probably have a common cause. Also these failures are usually rare but can be almost systematic at times, for instance from 2022-04-25 to 2022-05-30 on w1064 32-bit. -- 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 2

[Bug 54188] New: user32:win - test_GetMessagePos() sometimes gets an unexpected position on Windows
by WineHQ Bugzilla 20 Dec '22

20 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54188 Bug ID: 54188 Summary: user32:win - test_GetMessagePos() sometimes gets an unexpected position 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:win - test_GetMessagePos() sometimes gets an unexpected position on Windows and Wine: win.c:10841: Test failed: pos = 00e700d0 win.c:10845: Test failed: pos = 00e700d0 win.c:10849: Test failed: pos = 00e700d0 or win.c:10841: Test failed: pos = 00e600d0 win.c:10845: Test failed: pos = 00e600d0 win.c:10849: Test failed: pos = 00e600d0 See https://test.winehq.org/data/patterns.html#user32:win This happens most frequently on Windows 7 but also happens on Windows 10 21H2 and 22H2. -- 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 1