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

[Bug 52981] New: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52981 Bug ID: 52981 Summary: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Most of test_SpeechRecognizer() is skipped when run with elevated privileges: speech.c:896: SpeechRecognizer default language L"fr-FR". speech.c:1172: Tests skipped: Could not init SpeechRecognizer with default language! https://test.winehq.org/data/patterns.html#windows.media.speech:speech The involved lines are: 919 hr = RoActivateInstance(hstr, &inspectable); 922 if (hr == S_OK) ... 1170 else if (hr == SPERR_WINRT_INTERNAL_ERROR) /* Not sure when this triggers. Probably if a language pack is not installed. */ 1171 { 1172 win_skip("Could not init SpeechRecognizer with default language!\n"); An analysis of the test results across Windows versions shows that we see this SPERR_WINRT_INTERNAL_ERROR on Windows 10 >= 1809: cw-gtx560-1507 S_OK cw-rx460-1507 S_OK w1064v1507 S_OK w1064v1607 S_OK cw-gtx560-1709 S_OK cw-rx460-1709 S_OK w1064v1709 S_OK cw-gtx560-1809 skipped cw-rx460-1809 skipped w1064v1809 skipped cw-gtx560-1909 skipped cw-rx460-1909 skipped w1064v1909 skipped w1064v2004 skipped cw-gtx560-2009 skipped cw-rx460-2009 skipped w1064v2009 skipped cw-gtx560-21h1 skipped cw-rx460-21h1 skipped w10pro64-21h1 skipped cw-gtx560-21h2 skipped cw-rx460-21h2 skipped w1064-21h2 skipped w10pro64-21h2 skipped So far that looks pretty clear cut: Microsoft changed things around 1809 such that processes running with elevated privileges cannot / are not allowed to perform speech recognition. That would mean the test should drop the privileges so it can run on any platform. However the test was not skipped in the w10pro64v2004 and w10pro64 (21H1) test configurations... until they were upgraded. So this indicates that there may be a way to get this test to work even while retaining elevated privileges. But how? To help debug the issue I added two test configurations: * w10pro64restored The w10pro64 VM restored from a backup of the pre-2022-05 upgrade VM. Surprisingly the test still ends up being skipped! * w10pro64old Luckily before the upgrade I moved the old VM out of the way. It is now available as w10pro64old with the exact same live snapshots. Comfortingly the test is still not skipped, even after waiting some time and rebooting. That last part indicates there may be something either in the way the TestBot creates the live snapshots, or in the "WineTestBot VMs" checklist I go through when preparing the VMs and the cw-* machines (but then the clear 1809 cutoff point is quite a coincidence). -- 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 0

[Bug 33621] New: [UWIN] ksh93 from UWIN generates a lot of fixme warnings
by wine-bugs＠winehq.org 11 May '22

11 May '22

http://bugs.winehq.org/show_bug.cgi?id=33621 Bug #: 33621 Summary: [UWIN] ksh93 from UWIN generates a lot of fixme warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit generates a lot of "fixme" warnings and the shell is generally not useable. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run Windows/UWIN version of ksh93: wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe' fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24 (null) (nil)) fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub! fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e98,symt:0x2970264) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2943cb0,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e90,symt:(nil)) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. IMO the most pressing problems are: 1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. 2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented 3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented 4. fixme:ntdll:NtSetInformationToken unimplemented class 4 5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 10

[Bug 52968] New: CPU BoostTester manages to run only on real cores in Windows, but not with wine
by WineHQ Bugzilla 09 May '22

09 May '22

https://bugs.winehq.org/show_bug.cgi?id=52968 Bug ID: 52968 Summary: CPU BoostTester manages to run only on real cores in Windows, but not with wine Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Hi, the following tiny porgram is used to test the boost capability of cpus. It detects real cores and only tests those, not the smt siblings. On windows it manages to run on the real cores only. On Linux it runs on the cores 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 I am using a 5950x. The real cores are 0-15. The siblings ar 16-31. 0+16 is a pair, 1+17, 2+18 etc.. So instead of testing the 16 real cores, it is testing only 8 + siblings. The software is availible here, including source. I don't know if the software is doing some strange things to detect the real cores or if the issue is on the wine side. As the source is just a handful of c++ code, someone with experience might take a look and judge where the problem is, wine or the program. Here is the link: https://github.com/jedi95/BoostTester Many thx ! -- 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 52976] New: Daagon Map Maker on itch.io crash
by WineHQ Bugzilla 08 May '22

08 May '22

https://bugs.winehq.org/show_bug.cgi?id=52976 Bug ID: 52976 Summary: Daagon Map Maker on itch.io crash Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: ildaniel999(a)hotmail.com Distribution: --- Created attachment 72346 --> https://bugs.winehq.org/attachment.cgi?id=72346 wine file loads up to 100%, changes screen settings, but then crashes -- 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 0

[Bug 52684] New: Command and Conquer Generals (and C&C Zero Hour) have no ground textures
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=52684 Bug ID: 52684 Summary: Command and Conquer Generals (and C&C Zero Hour) have no ground textures Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: bender647(a)yahoo.com Regression SHA1: 1632b8e7a419ebf256c4a356a58d505ef918f2fe Distribution: Slackware Introduced in wine-7.3 with commit 1632b8e7a419ebf256c4a356a58d505ef918f2fe, the C&C Generals game engine does not draw ground textures. The ground (or water) area is black. Reverting to wine-7.2, or applying this commit as a reverse-patch on wine-7.4 will fix the issue. The commit was found by bisecting the git tree. This symptom appears in older bug reports but the fixes there do not appear to work now. Tested on two platforms, but both were Intel i915 graphics. If necessary, I can get access to an Nvidia platform. To reproduce: 1. A free demo is available for download to run the game: https://www.moddb.com/downloads/start/111369 (https://www.moddb.com/games/cc-generals/downloads/command-conquer-generals-…) 2. Install in 32-bit prefix. 3. Run with `wine start generals.exe -nologo` and the game engine will be seen running behind the main menu. The ground will be blank if the bug is present. Verified to affect: https://appdb.winehq.org/objectManager.php?sClass=version&iId=4881 https://appdb.winehq.org/objectManager.php?sClass=version&iId=35407 Likely also: https://appdb.winehq.org/objectManager.php?sClass=version&iId=1717 -- 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 24

[Bug 45098] New: FrostPunk: multiple graphical glitches
by wine-bugs＠winehq.org 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=45098 Bug ID: 45098 Summary: FrostPunk: multiple graphical glitches Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)embed.me.uk Distribution: --- Created attachment 61268 --> https://bugs.winehq.org/attachment.cgi?id=61268 FrostPunk log With patch posted in https://bugs.winehq.org/show_bug.cgi?id=45080 the game sucessfully starts however there are severe graphical glitches which render it unplayable. Log attached. -- 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 15

[Bug 2155] Failure of SetFocus, SetActiveWindow and SetForegroundWindow
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=2155 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- 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 0

[Bug 45388] New: user32: edit fails on Traditional Chinese and Korean locales
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=45388 Bug ID: 45388 Summary: user32:edit fails on Traditional Chinese and Korean locales Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:edit fails with the following errors on Traditional Chinese and Korean locales: edit.c:1489: Test failed: 0: got 1, 1 edit.c:1510: Test failed: 0: got 1, 1 edit.c:1524: Test failed: 0: got 1, 1 edit.c:1538: Test failed: 0: got 1, 1 See: * Source matching the above https://source.winehq.org/git/wine.git/?a=blob;f=dlls/user32/tests/edit.c;h… * user32:edit WineTest failures https://test.winehq.org/data/tests/user32:edit.html The errors can be reproduced on the newtb-wvistau64-zh-cn TestBot VM, and also happen on fg-win7u64-1spie9-ko. -- 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 52771] New: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52771 Bug ID: 52771 Summary: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The way Wine creates the window for console applications breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win. https://test.winehq.org/data/patterns.html#comctl32:button https://test.winehq.org/data/patterns.html#dinput:keyboard https://test.winehq.org/data/patterns.html#user32:dialog https://test.winehq.org/data/patterns.html#user32:input https://test.winehq.org/data/patterns.html#user32:monitor https://test.winehq.org/data/patterns.html#user32:win These all started failing in Wine on 2022-03-17 with the commit below (also referenced in bug 52761): commit f034084d49b354811096524d472ae5172ac1cebf Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Thu Mar 17 08:27:28 2022 +0100 kernelbase: Handle corner case in CreateProcess. In CreateProcess, if: - parent isn't attached to a console - CreateProcess's flag isn't set with DETACHED_PROCESS nor CREATE_NEW_CONSOLE - child is a CUI program then a console must be allocated for the child. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52048 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The way the TestBot starts the tests in Wine is this [1]: testagentd (Unix, no terminal) \- shell script (sh Unix, no terminal) \- WineTest.pl (perl Unix, no terminal) \- ./wine TestLauncher (Windows CUI, no console) \- unit test (Windows CUI) -> creates a console \- unit test can recurse upon itself (CUI) I will now try to summarize the current understanding of the issue from the wine-devel discussion [2], using the above figure as a reference: 1. testagentd is a daemon so it does not have an associated terminal. 2. When ./wine does not have a terminal it does not create a console window, even when starting a console application. This is so wine can be used for background (batch) tasks without requiring a X session or popping up windows all over the place. 3. But when a Windows application calls CreateProcess() without DETACHED_PROCESS, a console does get created. This is what happens when TestLauncher starts a unit test. 4. While the console object is created synchronously in the wineserver process, the actual window is created asynchronously (by wineconsole). This causes it to pop up while the unit test as already started, which confuses the tests that check the window hierarchy, the focus, etc. There are two ways the above differ from Windows: 1. I believe Windows creates both the console object and the matching window synchronously. So even if the console was created when starting the test unit there should be no failure. 2. On Windows the shell script is replaced by a batch script which triggers the console creation. So the console creation happens a bit earlier which could also mask any window creation delay. The reason why f034084d49b3 made a difference is that before Wine was not creating console windows. [1] More details on the different ways the TestBot starts the tests: https://www.winehq.org/pipermail/wine-devel/2022-April/212550.html [2] March: https://www.winehq.org/pipermail/wine-devel/2022-March/212330.html April: https://www.winehq.org/pipermail/wine-devel/2022-April/212513.html -- 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 14

[Bug 52149] New: user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52149 Bug ID: 52149 Summary: user32:dialog fails in test_DialogBoxParam() on current Windows 10 21H1 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 fails in test_DialogBoxParam() on current Windows 10 21H1: dialog.c:1854: Test failed: got 1407 https://test.winehq.org/data/patterns.html#user32:dialog So instead of failing with an error code of 0, the call below fails with ERROR_CANNOT_FIND_WND_CLASS... which makes sense? ret = DialogBoxParamA(GetModuleHandleA(NULL), "TEST_DIALOG_INVALID_CLASS", 0, DestroyDlgWinProc, 0); It's interesting to note that this failure did not happen on the initial Windows 10 21H1 test configurations (2021-08-23). As far as I can tell it's only after KB5006670 was applied (on 2021-10-21) that the test started failing. Unfortunately this is a cumulative update so it may not help narrow down the cause very much. -- 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