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

[Bug 52559] New: kernel32:resource times out since 2021-12-29 at two win10 testbot systems.
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52559 Bug ID: 52559 Summary: kernel32:resource times out since 2021-12-29 at two win10 testbot systems. Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- I wondered because the windows test patterns showed timeouts for the kernel32:resource [1] since some days. I tried a run with verbose timestamps and got [2]. There it shows gaps of ~6 seconds, and it looks like the delay originates from an execution of EndUpdateResourceA [3]. Unfortunately there are a lot calls for this function and therefore the test times out. Searching the net led me to the autohotkey forums where this function was associated with windows defender. Is windows defender active at these VMs? [1] https://test.winehq.org/data/tests/kernel32:resource.html [2] https://testbot.winehq.org/JobDetails.pl?Key=108231&f201=exe32.report#k201 [3] https://source.winehq.org/git/wine.git/blob/781277de62822c2bac23dc892a99665… -- 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 52856] New: kernel32:process fails when Wine has no Unix terminal
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52856 Bug ID: 52856 Summary: kernel32:process fails when Wine has no Unix terminal Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:console fails on the TestBot Wine machines: process.c:1552: Test failed: Opening ConIn process.c:1553: Test failed: Opening ConOut process.c:1556: Test failed: Getting sb info process.c:1557: Test failed: Getting console in mode process.c:1558: Test failed: Getting console out mode process.c:212: 5 failures in child process process.c:1569: Test failed: Getting sb info process.c:1570: Test failed: Getting console in mode process.c:1571: Test failed: Getting console out mode process.c:1582: Test failed: GetLastError: expecting 87 got 12 process.c:1592: Test failed: GetLastError: expecting 87 got 12 process.c:1621: Test failed: Console:SizeX expected 30870, but got 0 process.c:1622: Test failed: Console:SizeY expected 31489, but got 0 process.c:1623: Test failed: Console:CursorX expected 32644, but got 0 process.c:1624: Test failed: Console:CursorY expected 94, but got 0 process.c:1625: Test failed: Console:Attributes expected 0, but got 1 process.c:1626: Test failed: Console:winLeft expected 0, but got 1 process.c:1627: Test failed: Console:winTop expected 4294964424, but got 0 process.c:1628: Test failed: Console:winRight expected 49, but got 0 process.c:1629: Test failed: Console:winBottom expected 30870, but got 0 process.c:1630: Test failed: Console:maxWinWidth expected 31489, but got 0 process.c:1631: Test failed: Console:maxWinHeight expected 11256, but got 0 process.c:1634: Test failed: Console:InputMode expected 0, but got 1 process.c:1635: Test failed: Console:OutputMode expected 7211040, but got 0 process.c:1639: Test failed: Wrong console CP (expected 1252 got 0/0) process.c:1640: Test failed: Wrong console-SB CP (expected 1252 got 0/0) process.c:1645: Test failed: Wrong console mode process.c:1646: Test failed: Wrong console-SB mode https://test.winehq.org/data/patterns.html#kernel32:process The reason is that the TestBot starts Wine from a daemon process which does not have an associated xterm / Konsole / GNOME terminal. This causes Wine to have to allocate a Wine console and that's when things go wrong. A bisect shows that the TestBot is only impacted by this bug since the commit below: commit eff83cd4e00e8ccd4daad05bdd6d76e77664ddd1 Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Mon Apr 11 15:05:09 2022 +0200 kernelbase: Provide a pseudo console environment for initial CUI processes not tied to a Unix tty. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52771 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52761 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52743 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> But as the commit entry shows this commit also fixed a lot of other issues in the TestBot results (not least of which is getting the wow64 WineTest results in an acceptable shape for test.winehq.org) Also this issue has happened before as evidenced by bugs 25284 and 28220. However those bugs are very old (~2014) so the issue may have been fixed and reappeared (the TestBot has not used a Unix terminal to run the Wine tests since at least 2018-06 (date on local-testagentd.service) and probably 2017 or more (f1d368722b65 tools commit)). Bug 28220 does have a more recent and interesting comment by Esme with regards to handle inheritance: https://bugs.winehq.org/show_bug.cgi?id=28220#c3 -- 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 52079] New: oleacc:main crashes randomly on Windows 10 1709+
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52079 Bug ID: 52079 Summary: oleacc:main crashes randomly on Windows 10 1709+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com oleacc:main crashes randomly on Windows 10 1709+ in both 32- and 64-bit: main.c:1041: Test failed: V_VT(&v) = 0 main.c:1048: Test failed: V_VT(&v) = 0 main.c:1049: Test failed: V_DISPATCH(&v) = 0000000000000000 main.c:1049: this is the last test seen before the exception 1050:main: unhandled exception c0000005 at 0000000000401597 oleacc:main:1050 done (-1073741819) in 0s Test failed: crash (c0000005) https://test.winehq.org/data/patterns.html#oleacc:main Unsurprisingly a bisect shows that the tests started failing with the commit that introduced the test: commit 1a3db363c6b4065af532a8db1e6309be753b1781 Author: Connor McAdams <cmcadams(a)codeweavers.com> Date: Mon Sep 20 18:03:31 2021 +0200 oleacc: Add Client_get_accFocus tests. Signed-off-by: Connor McAdams <cmcadams(a)codeweavers.com> Signed-off-by: Piotr Caban <piotr(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> At the time the crash happened after line 1037 which points to line 1039 as a likely culprit: 1032 /* Set focus to each child window. */ 1033 SetFocus(btn); 1034 hr = IAccessible_get_accFocus(acc, &v); 1035 ok(hr == S_OK, "hr %#x\n", hr); 1036 ok(V_VT(&v) == VT_DISPATCH, "V_VT(&v) = %d\n", V_VT(&v)); 1037 ok(V_DISPATCH(&v) != NULL, "V_DISPATCH(&v) = %p\n", V_DISPATCH(&v)); 1038 1039 hr = IDispatch_QueryInterface(V_DISPATCH(&v), &IID_IOleWindow, (void**)&ow); 1040 ok(hr == S_OK, "got %x\n", hr); That call has been moved to _check_acc_hwnd() and so the crash now happens in the first QueryInterface() call in that function: hr = IUnknown_QueryInterface(unk, &IID_IOleWindow, (void**)&ow); called from check_acc_hwnd((IUnknown*)V_DISPATCH(&v), btn); -- 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 51407] New: kernel32:time's test_GetCalendarInfo() fails in Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51407 Bug ID: 51407 Summary: kernel32:time's test_GetCalendarInfo() fails in Hindi Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 70263 --> https://bugs.winehq.org/attachment.cgi?id=70263 Broken fix and traces Three GetCalendarInfo() checks fail in Hindi: https://test.winehq.org/data/patterns.html#kernel32:time time.c:728: Test failed: GetCalendarInfoA failed err 87 time.c:731: Test failed: GetCalendarInfoA failed err 87 time.c:738: Test failed: got 0, expected 7 The immediate cause for the failure is that Hindi is one of the few languages for which NLS_IsUnicodeOnlyLcid() returns true. In turn this causes the ANSI GetCalendarInfoA() to return ERROR_INVALID_PARAMETER. The last failure just reflects the fact that the two calls to GetCalendarInfoA() should not have failed. Only Hindi fails and only in Wine. But before declaring this a Wine bug we need to look at Windows. * For some reason probably related to SetWinLocale [1] the system locale of w10pro64_hi is still English. * This causes both the ANSI and Unicode GetCalendarInfo() to return English names (Monday). * Manually setting the system locale to Hindi is possible on Windows 10 2004. What's interesting is the disabled and checked-by-default checkbox in that dialog: [X] Beta: Use Unicode UTF-8 for worldwide language support * And indeed doing that and running the test again results in GetCalendarInfoA() returning UTF-8 strings on Windows! time.c:730: ret=19 sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0" सोमवार time.c:735: ret2=19 sdayname1="\xe0\xa4\xb8\xe0\xa5\x8b\xe0\xa4\xae\xe0\xa4\xb5\xe0\xa4\xbe\xe0\xa4\xb0" सोमवार time.c:742: ret2=19 sdayname1=L"\0938\094b\092e\0935\093e\0930" * The beta moniker strongly suggests that this is a new option. Indeed selecting Hindi as the system locale was not possible in Windows 8.1 for instance. * This is probably also why SetWinLocale has trouble setting the system locale to Hindi. So the Windows behavior can be summarized as such: * Return localized values for non-Unicode-only locales. * In older Windows versions setting the system locale to a Unicode-only locale is impossible. * In newer Windows versions setting the system locale to a Unicode-only locale is possible and then it uses UTF-8. Commenting out the Hindi line in NLS_IsUnicodeOnlyLcid() fixes the failures in Wine (see attached patch). But this fix is wrong because it causes GetCalendarInfoA() to return question marks instead of intelligible strings. (it also impacts many APIs but that's probably ok based on the Windows behavior) So Wine should do one of the following: 1. Stick to a 'safe' system locale when $LANG is set to a Unicode-only locale. Typically this would be English. 2. Or use UTF-8 when the system locale is a Unicode-only locale. Option 2 would actually make a lot of sense on Unix systems but it is also more likely to break Windows applications. So option 1 may be the safer (and simpler?) option (for now). [1] https://source.winehq.org/git/tools.git/blob/HEAD:/testbot/bin/SetWinLocale… -- 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 52904] New: kernel32:locale breaks oleaut32:varformat on Wine in the French locale
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52904 Bug ID: 52904 Summary: kernel32:locale breaks oleaut32:varformat on Wine in the French locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:locale breaks oleaut32:varformat on Wine in the French locale: varformat.c:642: Test failed: Unexpected hr 0x80020005 for L"0,000 EUR" varformat.c:649: Test failed: Unexpected hr 0x80020005 for L"0,000 EUR" https://test.winehq.org/data/patterns.html#oleaut32:varformat When starting from a clean wineprefix one would normally get "0,000 €" for this test. But if one runs kernel32:locale before the Euro symbol is replaced with "EUR" which is then not recognized as a currency symbol. A bisect shows that the failures started with this commit: commit 78a33f968461fa3a01d3eec837b4c24f353bc00b Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Tue Mar 29 22:12:25 2022 +0200 kernelbase: Reimplement SetLocaleInfoW(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The commit modifies both kernel32 and kernel32:locale, and both parts of the patch are needed to reproduce the 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 52858] New: kernel32:file fails in Windows 8.1 on the cw-rx460 machine
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52858 Bug ID: 52858 Summary: kernel32:file fails in Windows 8.1 on the cw-rx460 machine 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:file and msvcp140:msvcp140 fail on the cw-rx460 machine: file.c:905: Test failed: Unexpected error 87. file.c:910: Test failed: Unexpected error 87. https://test.winehq.org/data/patterns.html#kernel32:file These are new tests so unsurprisingly the failures are caused by the commit that introduced them: commit 02faaea93b78d5d53976b2955bef7beffa780d02 Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Mon Apr 11 21:44:36 2022 +0300 kernelbase: Reset last error on success in CopyFileExW(). Signed-off-by: Paul Gofman <pgofman(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> It's unclear why the test only fails on this configuration. Also note that msvcp140:msvcp140 fails in a very similar way in the exact same test configuration: see bug 52857. -- 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 52867] New: System.Globalization.CultureInfo.GetCultureInfo fails for 'en' value
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52867 Bug ID: 52867 Summary: System.Globalization.CultureInfo.GetCultureInfo fails for 'en' value Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 72261 --> https://bugs.winehq.org/attachment.cgi?id=72261 stacktrace (filing under ntdll, as that where relevant files were before the commit series that most likely broke it) After upgrading to 7.6, still occurring in 7.7, a regression was made - the last published dnSpy version had been running relatively well in its basic functionality (I'm actually not any good with it), other than minor display glitches; now it stacktraces immediately. I believe the stacktrace makes it clear what happens and why I suspect that locale commit series are at fault here. That release of dnSpy embeds its mono environment, so it's not a wine-mono problem. -- 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 43208] New: Assassin's Creed IV - Black Flag Hangs tightly
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=43208 Bug ID: 43208 Summary: Assassin's Creed IV - Black Flag Hangs tightly Product: Wine-staging Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tall89(a)mail.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When you switch to the Big Inagua location, the game hangs tight, you have to do Cntrl + Atl + Delete to remove the task, then the game closes, then you receive an error message, the program ACBF.exe has a serious error, the application will be closed, we apologize for the inconvenience WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg ------ Program AC4BFSP.exe ------ err:winsock:WSAIoctl -> SIO_ADDRESS_LIST_CHANGE request failed with status 0x2733 err:winedevice:async_create_driver failed to create driver L"ps6ajtsb": c0000135 err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 192.168.0.102:5353 16 aspire89-P55A-UD4.local. AAAA FE80:0000:0000:0000:0A12:F0CA:1A84:437A" err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: ProbeCount 2; will deregister 4 aspire89-P55A-UD4.local. Addr 192.168.0.102" err:eventlog:ReportEventW L"Local Hostname aspire89-P55A-UD4.local already in use; will try aspire89-P55A-UD4-2.local instead" err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Received from 192.168.0.102:5353 25 102.0.168.192.in-addr.arpa. PTR aspire89-P55A-UD4.local." err:eventlog:ReportEventW L"mDNSCoreReceiveResponse: Unexpected conflict discarding 27 102.0.168.192.in-addr.arpa. PTR aspire89-P55A-UD4-2.local." err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> has not been linked, or is not a program object.". err:d3d:wined3d_debug_callback 0x721acb8: "GL_INVALID_OPERATION error generated. <program> object is not successfully linked, or is not a program object.". wine: Unhandled page fault on read access to 0x00000063 at address 0x8cfb7f (thread 0047), starting debugger... wine: Unhandled page fault at address 0x7bc5d590 (thread 0012), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 168") (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger -- 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 14

[Bug 51460] New: oleaut32:vartest has a todo because Wine uses an outdated currency symbol for Swiss Francs
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=51460 Bug ID: 51460 Summary: oleaut32:vartest has a todo because Wine uses an outdated currency symbol for Swiss Francs Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Wine uses uses "SFr." as the currency symbol for Swiss francs instead of "CHF". According to Wikipedia: "The use of SFr. for Swiss Franc and fr.sv. are outdated" and are not recognized as correct by the "Secrétariat d'État à l'économie". https://en.wikipedia.org/wiki/Swiss_franc This forces the use of a todo in oleaut32:vartest: lcid = MAKELCID(MAKELANGID(LANG_FRENCH,SUBLANG_FRENCH_SWISS),SORT_DEFAULT); WCONVERT(L"3CHF", NUMPRS_CURRENCY|NUMPRS_USE_ALL); todo_wine EXPECT(1,NUMPRS_CURRENCY|NUMPRS_USE_ALL,NUMPRS_CURRENCY,4,0,0); And it may cause oleaut32:varformat to fail when run in a Swiss locale. The "SFr." currency symbol comes from nls/(de|fr|it)s.nls which are generated from Unicode tables by tools/make_unicode so it's not clear how to fix them. -- 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 52864] New: windows.media.speech:speech has a refcount failure on all Windows 10 versions
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52864 Bug ID: 52864 Summary: windows.media.speech:speech has a refcount failure on all Windows 10 versions 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 fails on all Windows 10 versions: speech.c:968: Test failed: Unexpected refcount 2, expected 1 https://test.winehq.org/data/patterns.html#windows.media.speech:speech This failure is present on all Windows 10 versions except the 1809 and 1909 ones, but probably just because these turn out not to have speech support for English for some reason. So they just skip the test: speech.c:877: SpeechRecognizer default language L"en-US". speech.c:1110: Tests skipped: Could not init SpeechRecognizer with default language! Unsurprisingly a bisect shows that the failures started with the commit that introduced this new test: commit 4926bb148b049f1b60e57091f4aa87a3957aa69e Author: Bernhard Kölbl <besentv(a)gmail.com> Date: Wed Apr 6 18:28:41 2022 +0200 windows.media.speech: Add tests for IAsyncOperation. Signed-off-by: Bernhard Kölbl <besentv(a)gmail.com> Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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