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

[Bug 54153] New: kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code on Windows
by WineHQ Bugzilla 15 Dec '22

15 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54153 Bug ID: 54153 Summary: kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger - test_kill_on_exit() sometimes gets STILL_ACTIVE exit code on Windows: debugger.c:2078: Test failed: exit code = 00000103 See https://test.winehq.org/data/patterns.html#kernel32:debugger Where 0x103 == STILL_ACTIVE == STATUS_PENDING This should mean the process is still running. So either there is a race condition in the test or Windows 8 and 10 21H1 are buggy. With only 3 instances in 6 months this failure is pretty rare: * 2022-07-11 on w10pro64-ar (64-bit, 21H1) * 2022-10-31 on w864 (64-bit) * 2022-12-06 on w864 (64-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 1

[Bug 54107] New: Windows Defender interferes with the tests on w1064v1909
by WineHQ Bugzilla 15 Dec '22

15 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54107 Bug ID: 54107 Summary: Windows Defender interferes with the tests on w1064v1909 Product: Wine-Testbot 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 Defender interferes with the tests on w1064v1909: sc.exe:sc start programs/sc/tests/sc.c sc.exe:sc:0000 done (-225) in 0s 0B Where 225 == ERROR_VIRUS_INFECTED This is because in this snapshot was created before Windows Defender became a problem and thus has no exclusion for the folder where the TestBot puts the test binaries. w1064v2009 (and presumably snapshots of newer Windows versions) has the needed exclusion. v1064v1809 (and presumably snapshots of older Windows versions) does not have an exclusion but has "Real-time protection" turned off which should ensure Defender won't interfere (that option is not available in newer Windows (Defender) 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.

1 4

[Bug 54128] New: user32:msg - test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10
by WineHQ Bugzilla 15 Dec '22

15 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54128 Bug ID: 54128 Summary: user32:msg - test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10 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 test_PeekMessage3() sometimes gets an unexpected WM_TIMECHANGE message on Windows 10: msg.c:13549: Test failed: msg.message = 30 instead of WM_TIMER msg.c:13552: Test failed: msg.message = 275 instead of WM_USER + 1 msg.c:13554: Test failed: expected PeekMessage to return FALSE, got 1 msg.c:13564: Test failed: msg.message = 1025 instead of WM_TIMER msg.c:13566: Test failed: msg.message = 275 instead of WM_USER msg.c:13568: Test failed: expected PeekMessage to return FALSE, got 1 msg.c:13577: Test failed: msg.message = 1024 instead of WM_TIMER msg.c:13579: Test failed: expected PeekMessage to return FALSE, got 1 See https://test.winehq.org/data/patterns.html#user32:msg Where 30 == WM_TIMECHANGE 275 == WM_TIMER 1024 == WM_USER 1025 == WM_USER + 1 This is similar to the issue happening in test_PeekMessage2() in bug 53273. This last happened on 2022-12-09 on w10pro64-pt-BR where the Internet time synchronization has not been disabled. So that may be the source of the WM_TIMECHANGE messages. The TestBot now has code to disable Internet time synchronization but the snapshots have not all been updated. So this bug should be revisited once they have been updated to see if the failures are still happening. -- 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 54076] New: windows.globalization:globalization - test_GlobalizationPreferences() sometimes unexpectedly returns en_US on Windows 10
by WineHQ Bugzilla 15 Dec '22

15 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54076 Bug ID: 54076 Summary: windows.globalization:globalization - test_GlobalizationPreferences() sometimes unexpectedly returns en_US 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.globalization:globalization - test_GlobalizationPreferences() sometimes unexpectedly returns en_US on Windows 10: globalization.c:137: Test failed: IGlobalizationPreferencesStatics_get_Languages 0 returned len 5, str L"en-US", expected L"de-DE" globalization.c:177: Test failed: IGlobalizationPreferencesStatics_get_Languages 0 returned len 5, str L"en-US", expected L"de-DE" See https://test.winehq.org/data/patterns.html#ws2_32:sock This failure first happened on 2022-11-22 and impacts the de, fr, ja, ko, pt-BR and ru locales of the w10pro64 VM. It's not systematic but is frequent enough that it seems like it does not impact the other locales. The timing of the first failure is suspicious: * The w10pro64 had a problem where Windows 10 would reset UserDefaultLCID, ThreadLocale and Country to en_US when the TestBot called SetSystemTime() to update the clock in the live snapshot. As long as this issue was there there was no failure. * On 2022-11-21 LibvirtTool got a workaround to re-set these locale settings after setting the time and the failures started. So this sounds like Windows is still messing with the locales :-( -- 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 54147] New: Kholat from GOG: Splash video are not in fullscreen
by WineHQ Bugzilla 14 Dec '22

14 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54147 Bug ID: 54147 Summary: Kholat from GOG: Splash video are not in fullscreen Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- Wine wine-8.0-rc1. Ubuntu 22.10. >From bug https://bugs.winehq.org/show_bug.cgi?id=50043. -- 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 52930] New: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows
by WineHQ Bugzilla 14 Dec '22

14 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=52930 Bug ID: 52930 Summary: d3dcompiler_47:hlsl_d3d9 fails randomly on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 72305 --> https://bugs.winehq.org/attachment.cgi?id=72305 Small patch to apply on top of 58d20aae3772^ to get failures d3dcompiler_47:hlsl_d3d9 fails randomly on Windows 8.1 to 21H2: hlsl_d3d9.c:1691: Test failed: Got unexpected hr 0x88760b59. hlsl_d3d9.c:1692: Test failed: Got unexpected blob. hlsl_d3d9.c:1693: Test failed: Got unexpected errors. https://test.winehq.org/data/patterns.html#d3dcompiler_47:hlsl_d3d9 A bisect against Windows 10 21H1 on cw-gtx560 shows that the failures started with the commit below: commit 58d20aae3772473a90e43ee236b793f0421eecb1 Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Tue Feb 8 19:48:44 2022 +0100 d3dcompiler/tests: Build without -DWINE_NO_LONG_TYPES. Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The patch does not actually make any change that should matter but I have confirmed the bisect result manually: 58d20aae3772^ -> 200 consecutive runs with no failure 58d20aae3772 -> fails after 9 to 33 runs - Applying just the Makefile.in parts and last 4 chunks of hlsl_d3d9.c of that commit is sufficient to get the failures. - Patching only the makefiles is not enough. - I did not try to identify which of the 4 chunks are needed to get failures. They all patch code that's executed after the failure anyway. So there must be some memory corruption that's sensitive to memory layout or some subtle issue with the generated code. I also if(0)ed-out all the other test_xxx() functions, and also if(0)ed-out the tests that preceded the failing one in test_include() but I still get the failure so it's not a case where an ill-advised NULL-behavior test causes memory corruption. -- 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 54138] New: wine/debug.h does not compile in Visual Studio with native headers due to undefined __has_attribute
by WineHQ Bugzilla 13 Dec '22

13 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54138 Bug ID: 54138 Summary: wine/debug.h does not compile in Visual Studio with native headers due to undefined __has_attribute Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimaki(a)rocketmail.com Distribution: --- wine/debug.h does not compile in Visual Studio with native headers due to undefined __has_attribute. Other headers in Wine that use __has_attribute have below code. Probably this or something similar needed in debug.h as well. #ifndef __has_attribute #define __has_attribute(x) 0 #endif -- 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 54133] New: A WM_CLIPCHILDREN window's repaint region is not computed correctly when its child is resized or repositioned
by WineHQ Bugzilla 13 Dec '22

13 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54133 Bug ID: 54133 Summary: A WM_CLIPCHILDREN window's repaint region is not computed correctly when its child is resized or repositioned Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Regression SHA1: 33617af8145b6fadfe41d48968a728ff57b3064b Distribution: --- Wine sometimes under-calculates the repaint region of WM_CLIPCHILDREN windows with a child window that has been resized or repositioned. The regression started with the following commit: commit 33617af8145b6fadfe41d48968a728ff57b3064b Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com> Date: Mon Oct 31 22:30:20 2022 +0900 server: Don't invalidate the newly exposed child region on the parent if it doesn't clip children. This partly reverts e42eaaaf3a873d29b14f8f3a3617df2d0d4210ca. Signed-off-by: Jinoh Kang <jinoh.kang.kr(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 4

[Bug 54136] New: user32:input - test_GetMouseMovePointsEx() sometimes fails when missing privileges on Windows 7 & 8
by WineHQ Bugzilla 13 Dec '22

13 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54136 Bug ID: 54136 Summary: user32:input - test_GetMouseMovePointsEx() sometimes fails when missing privileges on Windows 7 & 8 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 test_GetMouseMovePointsEx() sometimes fails when missing privileges on Windows 7 & 8: input.c:1605: Test failed: expected to get 64 mouse move points but got -1 input.c:1606: Test failed: expected error to stay deadbeef, got 493 input.c:1628: Test failed: expected to get 64 mouse move points but got -1 input.c:1629: Test failed: expected cursor position to be 6x6 but got 250 149 input.c:1630: Test failed: expected cursor position to be 6x6 but got 245 149 input.c:1642: Test failed: expected to get 64 mouse move points but got -1 input.c:1643: Test failed: expected cursor position to be 150x75 but got 250 149 input.c:1644: Test failed: expected cursor position to be 150x150 but got 245 149 input.c:1645: Test failed: expected cursor position to be 150x75 but got 241 149 input.c:1649: Test failed: expected to get 62 mouse move points but got -1 input.c:1650: Test failed: expected cursor position to be 150x75 but got 250 149 input.c:1651: Test failed: expected cursor position to be 30x30 but got 245 149 input.c:1662: Test failed: wrong extra info, got 0x0 expected 0xcafecafe input.c:1672: Test failed: cursor didn't change position after mouse_event() input.c:1678: Test failed: wrong extra info, got 0x0 expected 0xdeadbeef See https://test.winehq.org/data/patterns.html#user32:input This set of failures seems to only happen on w7u-adm and w8adm, both of which run the tests without elevated privileges. But the failures are not systematic so it is likely there is interference from some other test. Also there have been 5 instances in July but then none until December: * 2022-07-14 w8adm * 2022-07-15 w8adm * 2022-07-18 w8adm * 2022-07-19 w7u-adm * 2022-07-25 w7u-adm * 2022-12-09 w8adm * 2022-12-12 w8adm -- 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 53978] New: d3dx9_*, d3dx10_* and d3dx11_* dlls missing on some TestBot VMs
by WineHQ Bugzilla 13 Dec '22

13 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53978 Bug ID: 53978 Summary: d3dx9_*, d3dx10_* and d3dx11_* dlls missing on some TestBot VMs Product: Wine-Testbot 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 The d3dx9_*, d3dx10_* and d3dx11_* dlls are missing on some TestBot VMs. Specifically: * w7pro64 Only runs the 64-bit tests which report that these dlls are missing (plus atl100, atl110 and d3d8). w7u runs the 32-bit tests and, surprisingly, does not report any of these dlls to be missing. Adding the missing dlls on w7pro64 probably is not worth it. * w1064v1507 missing the 32- and 64-bit dlls Not worth adding them. * w10pro64v2004 missing the 32- and 64-bit dlls Not worth adding them. * w11pro64 32- and 64-bit dlls -> Add them. w11pro64_nv actually had a couple of these before I fixed the Windows Update issue. It seems that they got installed for the NVIDIA GUI and did not get installed when I rebuilt the VM with just the NVIDIA driver. * fgtb-w10pro64-64 missing the 32- and 64-bit dlls Not a TestBot VM but add them 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 2