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

[Bug 51312] New: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460)
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=51312 Bug ID: 51312 Summary: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460) Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dxgi:dxgi gets failures of the form: https://test.winehq.org/data/patterns.html#dxgi:dxgi dxgi.c:1460: Test failed: Mode 3: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 22: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 55: Modes should have been sorted, refresh rate 59.940060 < 75.000000. * These failures happen on all available Windows versions (8.1 to 10 2009). * They also happen regardless of the Radeon driver version: 19.11.3 to 21.4.1. * They don't happen on machines with any other GPU (cw-gtx560 and QEmu VMs). * They also happen systematically so are not probably caused by a threading issue. * So this really looks like a Radeon-specific behavior. The failing test was introduced by the following commit: commit eb2028fa90c41d3b7b8b4f924cd86059c5ba1e0d Author: Andrew Eikum <aeikum(a)codeweavers.com> AuthorDate: Mon Oct 28 16:59:18 2019 +0330 dxgi: Sort reported output modes. Sekiro: Shadows Die Twice depends on this for its mode switching. Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Does the application crash on Windows machines with an AMD GPU? Or does the Radeon driver return the wrong order only on some GPUs? If the application does not crash maybe our order specification is a bit too strict? Given that an application depends on this we probably want Wine to respect the ordering. Just add a broken()? -- 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 50368] New: DragonAge Origins Launcher doesn't toggle music status
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=50368 Bug ID: 50368 Summary: DragonAge Origins Launcher doesn't toggle music status Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: ArchLinux Until recently the Dragon Age Origins Launcher didn't work at all becouse bug #44185 that was recently fixed. However now, the laucnehr start, it play correctly the music but the toggle button to disable/enable the music doesn't work. This is the flow of what seems the issue: 0164:trace:mci:mciSendStringW (L"pause all", 0074EE48, 100, 00000000) 0164:trace:mci:mciSendStringW verb=L"pause" on dev=L"all"; offset=4 0164:trace:mci:mciSendStringW [-1, MCI_PAUSE, 00000000, 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000] 0164:fixme:mci:MCI_SendCommand unhandled MCI_ALL_DEVICE_ID 0164:trace:mci:mciSendStringW => 117 wine isn't handling correctly the MCI_ALL_DEVICE_ID case in cases others then closing the device. This affect just the launcher (the game should work properly if not regressed recently, still didn't try) so low priority, but other programs may be affected. -- 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 51217] New: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51217 Bug ID: 51217 Summary: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info Product: Wine Version: 6.8 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 has a failure on w1064v1607 (Windows 10 64-bit version 1607 running the 32-bit tests): https://test.winehq.org/data/patterns.html#ntdll:info info.c:3024: Test failed: wrong result 0 This is a check of the RtlWow64IsWowGuestMachineSupported() result. The commit that introduced this check is: commit 4f8ede8e7665328a2a3ccd303875e239bf443512 Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Thu Apr 29 17:15:15 2021 +0200 ntdll: Implement RtlWow64IsWowGuestMachineSupported(). 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 4

[Bug 51078] New: mshtml:events hangs on Windows 10 1709
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51078 Bug ID: 51078 Summary: mshtml:events hangs on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 69941 --> https://bugs.winehq.org/attachment.cgi?id=69941 Patch to more reliably reproduce the hang mshtml:events sometimes hangs on Windows 10 1709: http://winetest.dolphin/data/patterns.html#mshtml:events For some reason this only happens on Windows 1709 (the reports say this is mshtml 11.0.16299.309). The test proceeds all the way to the end but then does not exit because the mshtml component still has threads running: VSyncHelper Internet Explorer_Hidden MSCTFIME UI Commenting out the test_focus() run gets rid of the hangs. Also running the test with WINETEST_INTERACTIVE=1 greatly increases the probability of getting a hang. I attached a patch that does that and can be used to reproduce the hang on the TestBot's w1064v1709 VM. So this is clearly related to focus. -- 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 39659] New: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop
by wine-bugs＠winehq.org 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=39659 Bug ID: 39659 Summary: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop Product: Wine Version: 1.8-rc1 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Created attachment 52866 --> https://bugs.winehq.org/attachment.cgi?id=52866 log of test failure Test report: https://test.winehq.org/data/1d19eb15d4abfdd14dccc5ac05b83c0ee1a1ace1/win8_… Message tests calling SetFocus() on a button fail on my Windows 8 machine, because they get a WM_CANCELMODE message they weren't expecting. I have no idea what's special about my setup. It doesn't matter if I run the test stand-alone or with the full test suite, or if I run it as a dedicated user with a default configuration. -- 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 5

[Bug 30875] New: Unable to deselect character blocks in BMFont
by wine-bugs＠winehq.org 12 May '22

12 May '22

http://bugs.winehq.org/show_bug.cgi?id=30875 Bug #: 30875 Summary: Unable to deselect character blocks in BMFont Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dav75uk(a)yahoo.co.uk Classification: Unclassified Run BMFont (http://www.angelcode.com/products/bmfont/) and click on some of the checkboxes to the right to select characters to be included. It is not possible to uncheck the checkboxes. Workaround is to unselect one of the characters (click on a character in that range) which changes the full checked box to a part check box. The part check box can be unselected. -- 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 7

[Bug 52911] New: ole32:moniker fails on Windows in the UTF-8 codepage
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52911 Bug ID: 52911 Summary: ole32:moniker fails on Windows in the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ole32:moniker fails on Windows in the UTF-8 codepage: moniker.c:2189: Test failed: IsEqual failed with error 0x000001 [...] https://test.winehq.org/data/patterns.html#ole32:moniker So the failures happen because moniker1 and moniker2 are always different. Adding a call to winetest_push_context() shows that the failures all happen for string 2 which ole32:moniker uses to skip tests on code pages where there are round-trip issues: {0xc0, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, 0xc8, 0xc9, 0xca, 0xcb, 0xcc, 0xcd, 0xce, 0xcf, 0xd0, 0}, [...] skip("string 2 doesn't round trip in codepage %u\n", GetACP() ); So it looks like the skip fails to trigger for the UTF-8 codepage (or that we should do something else to make the UTF-8 case work). -- 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 52935] New: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52935 Bug ID: 52935 Summary: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:tab's test_tab(-1&-3) fails on Windows with the UTF-8 codepage: tab.c:591: Testing with default MinWidth tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] tab.c:593: Testing with MinWidth set to -3 tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] https://test.winehq.org/data/patterns.html#comctl32:tab Hindi + UTF-8 is the only locale where this test fails on Windows at this time. In particular there is no failure on the standard Hindi locale (English system locale) so this appears to be specific to UTF-8. -- 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 52939] New: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52939 Bug ID: 52939 Summary: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions 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 Created attachment 72312 --> https://bugs.winehq.org/attachment.cgi?id=72312 Loop on test_RegNotifyChangeKeyValue() to reproduce the event failures advapi32:registry's test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions: registry.c:3471: Test failed: expected ERROR_SUCCESS, got 6 registry.c:3599: Test failed: expected WAIT_OBJECT_0, got 258 https://test.winehq.org/data/patterns.html#advapi32:registry The failure is pretty rare so it is likely to cause false positives. The attached patch makes it possible to systematically reproduce the issue, at least on my test VM. With the 10000 loops I get 4 to 5 cases with the failure (so a rate of 0.05%) and a test run still takes under 8 seconds. -- 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 52925] New: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc)
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52925 Bug ID: 52925 Summary: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc) Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com usp10:usp10's wgDefault check in test_ScriptGetFontProperties() fails on some bitmap fonts in a number of locales: * Arabic usp10.c:2591: Test failed: bitmap font System wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 0126, tmDefaultChar 0085 * Hebrew usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 01ac, tmDefaultChar 0080 * Hindi + UTF-8 (no failure for plain Hindi) usp10.c:2591: Test failed: bitmap font System wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Courier wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 00fd, tmDefaultChar 0081 usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 00fd, tmDefaultChar 0080 * Japanese usp10.c:2591: Test failed: bitmap font FixedSys wgDefault 00f0, tmDefaultChar 00a0 usp10.c:2591: Test failed: bitmap font @FixedSys wgDefault 00f0, tmDefaultChar 00a0 * Chinese usp10.c:2591: Test failed: bitmap font System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Fixedsys wgDefault 00ac, tmDefaultChar 0080 https://test.winehq.org/data/patterns.html#usp10:usp10 In each case we get the expected value on Windows with a number of fonts but there are some exceptions that cause the failures. For a given locale the exceptions all have the same wgDefault value which means there is probably some logic to it. So we either need to come up with a better way to find the expected wgDefault value, or to radically loosen the test, or to restrict the test to some 'safe' fonts, or to remove the test entirely. -- 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