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

[Bug 18635] New: Menu bar is hidden in Adobe Lightroom 2.3
by wine-bugs＠winehq.org May 6, 2022

May 6, 2022

http://bugs.winehq.org/show_bug.cgi?id=18635 Summary: Menu bar is hidden in Adobe Lightroom 2.3 Product: Wine Version: 1.1.22 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thomas+wine(a)stromberg.org With the Adobe Lightroom 2.3 demo, the menu bar titles (File, etc.) do not display. If you click on the area that they should be, the menu does appear however. Lightroom 2.3 can be downloaded from https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_lightroom (free Adobe login required) I'm not sure where to go about tracing the issue down to, but I did notice the following calls that show that it is calling DrawMenuBar(). 0009:Call user32.GetMenu(0002003c) ret=60030cbe 0009:Ret user32.GetMenu() retval=000000f0 ret=60030cbe 0009:Call user32.GetMenuBarInfo(0002003c,fffffffd,00000000,0032e1a4) ret=60030cec fixme:menu:GetMenuBarInfo (0x2003c,0xfffffffd,0x00000000,0x32e1a4) 0009:Ret user32.GetMenuBarInfo() retval=00000000 ret=60030cec 0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030beb 0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030beb 0009:Call user32.GetSystemMenu(0002003c,00000000) ret=60030c06 0009:Ret user32.GetSystemMenu() retval=00000280 ret=60030c06 0009:Call user32.GetMenuItemInfoW(00000280,0000f060,00000000,0032e08c) ret=60030c22 0009:Ret user32.GetMenuItemInfoW() retval=00000001 ret=60030c22 0009:Call user32.DrawMenuBar(0002003c) ret=6008d171 -- 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 21

[Bug 52967] New: gdi32:font - test_text_metrics() fails on Windows with en-AE-u8 and plain Hindi
by WineHQ Bugzilla May 6, 2022

May 6, 2022

https://bugs.winehq.org/show_bug.cgi?id=52967 Bug ID: 52967 Summary: gdi32:font - test_text_metrics() fails on Windows with en-AE-u8 and plain Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - test_text_metrics() has a set of failures on Windows that only happen with the English Arab Emirates + UTF-8 locale (en-AE-u8), and in Hindi but without UTF-8 (hi): font.c:3441: Test failed: BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: @BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: @BIZ UDGothic: expected family 30 got 26. panose 2-11-4-0-... font.c:3441: Test failed: BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3441: Test failed: BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3441: Test failed: @BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3441: Test failed: @BIZ UDMincho Medium: expected family 30 got 16. panose 2-2-5-0-... font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho N-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho N-B got ff65 expected 1f font.c:3441: Test failed: UD Digi Kyokasho N-B: expected family 30 got 16. panose 2-2-7-0-... font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho N-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho N-B got ff65 expected 1f font.c:3441: Test failed: @UD Digi Kyokasho N-B: expected family 30 got 16. panose 2-2-7-0-... font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NP-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NP-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NP-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NP-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NK-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NK-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NK-B got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NK-B got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho N-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho N-R got ff65 expected 1f font.c:3441: Test failed: UD Digi Kyokasho N-R: expected family 30 got 16. panose 2-2-4-0-... font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho N-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho N-R got ff65 expected 1f font.c:3441: Test failed: @UD Digi Kyokasho N-R: expected family 30 got 16. panose 2-2-4-0-... font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NP-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NP-R got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NP-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NP-R got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for UD Digi Kyokasho NK-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for UD Digi Kyokasho NK-R got ff65 expected 1f font.c:3993: Test failed: A: tmDefaultChar for @UD Digi Kyokasho NK-R got a5 expected 1f font.c:4015: Test failed: W: tmDefaultChar for @UD Digi Kyokasho NK-R got ff65 expected 1f https://test.winehq.org/data/patterns.html#gdi32:font So it's not UTF-8 that causes the failures (still fails in Hindi). It seems to be something that English Arab Emirates and Hindi have in common and that goes away in Hindi + 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 1

[Bug 52960] New: Damavand is being more CPU-intensive than DXVK
by WineHQ Bugzilla May 6, 2022

May 6, 2022

https://bugs.winehq.org/show_bug.cgi?id=52960 Bug ID: 52960 Summary: Damavand is being more CPU-intensive than DXVK Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Hi, I remarked on my laptop (Ryzen 5800H + Navi 6700M) that Damavand is more CPU-intensive than DXVK. I did a test with 3 games where i mesured the CPU temperature during 90 secondes. I attached all logs for Witcher 3, A Plague Tales Innocence & Control. For Control & Witcher 3, you can see that with Damavand, the temperature is higher between 10 and 20 degrees celcius. For "A Plague Tale Innocence", the difference is between 5 and 10 degrees celcius. These mesures were done with sensors -> "while true; do sensors | grep 'Tctl' >> APlagueTale_DXVK.txt; sleep 1; done" I'll try on my desktop (Ryzen 5600X + Navi 6700XT) if i have the same 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 10

[Bug 52949] New: gdi32:font - test_GetCharABCWidths() fails on Windows in Korean and Chinese
by WineHQ Bugzilla May 2, 2022

May 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=52949 Bug ID: 52949 Summary: gdi32:font - test_GetCharABCWidths() fails on Windows in Korean and Chinese Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - test_GetCharABCWidths() fails on Windows in Korean and Chinese: (see w10pro64-ko and w10pro64-zh-CN) font.c:1238: Test failed: GetCharABCWidthsA 100 - 100 should have failed font.c:1238: Test failed: GetCharABCWidthsA ffff - ffff should have failed font.c:1244: Test failed: GetCharABCWidthsA ff should match. codepage = 0 font.c:1244: Test failed: GetCharABCWidthsA ff should match. codepage = 129 https://test.winehq.org/data/patterns.html#gdi32:font Note that Japanese does not get these failures. -- 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 52947] New: gdi32:font - "Small Fonts" has unexpected {First,Break}Char on Windows in Arabic
by WineHQ Bugzilla May 2, 2022

May 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=52947 Bug ID: 52947 Summary: gdi32:font - "Small Fonts" has unexpected {First,Break}Char on Windows in Arabic Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - "Small Fonts" has unexpected {First,Break}Char on Windows in Arabic, resulting in failures: font.c:996: Test failed: Small Fonts(12): tm.tmFirstChar = 00 font.c:1002: Test failed: Small Fonts(12): tm.tmBreakChar = 00 font.c:996: Test failed: Small Fonts(13): tm.tmFirstChar = 00 font.c:1002: Test failed: Small Fonts(13): tm.tmBreakChar = 00 font.c:1189: Test failed: GetCharABCWidthsW should have failed https://test.winehq.org/data/patterns.html#gdi32:font Maybe this can happen in other locales, but among those that are tested this only happens with the Arabic one (w10pro64-ar). In particular the Hebrew locale (w10pro64-he) does not have this 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 1

[Bug 52946] New: gdi32:font - test_bitmap_font_metrics() fails on Windows in the Greek & Japanese system locales
by WineHQ Bugzilla May 2, 2022

May 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=52946 Bug ID: 52946 Summary: gdi32:font - test_bitmap_font_metrics() fails on Windows in the Greek & Japanese system locales Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com gdi32:font - test_bitmap_font_metrics() fails on Windows in the Japanese and Greek system locales: Greek [w7u-el]: font.c:993: Test failed: Small Fonts(3): tm.tmInternalLeading 1 != 0 font.c:995: Test failed: Small Fonts(3): tm.tmAveCharWidth 2 != 1 font.c:1008: Test failed: Small Fonts(8): tm.tmMaxCharWidth 8 != 7 Japanese and Mixed locale (Japanese system locale) [w10pro64-ja w10pro64-mx-MX]: font.c:993: Test failed: Small Fonts(12): tm.tmInternalLeading 0 != 2 font.c:995: Test failed: Small Fonts(12): tm.tmAveCharWidth 7 != 5 font.c:993: Test failed: Small Fonts(13): tm.tmInternalLeading 0 != 2 font.c:995: Test failed: Small Fonts(13): tm.tmAveCharWidth 8 != 6 font.c:1189: Test failed: GetCharABCWidthsW should have failed https://test.winehq.org/data/patterns.html#gdi32:font So these failures entirely come down to the system locale, but only a few of them, and this can happen on any Windows version. -- 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 52902] New: gdi32:font has specific failures on Windows 10 with the UTF-8 codepage
by WineHQ Bugzilla May 2, 2022

May 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=52902 Bug ID: 52902 Summary: gdi32:font has specific failures on Windows 10 with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The following gdi32:font failures are specific to UTF-8 on Windows 10: --- test_RealizationInfo(): font.c:4356: Test failed: info[0] = 103 for the system font --- test_GetCharacterPlacement(): font.c:4998: Test failed: Unexpected first glyph L":" font.c:5012: Test failed: GetCharacterPlacementA returned different result: 1048638 vs 1048637 font.c:5016: Test failed: GetCharacterPlacementA returned different result: 1048638 vs 1048637 font.c:5023: Test failed: GetCharacterPlacementA returned different result: 1048638 vs 1048637 font.c:5025: Test failed: Unexpected first glyph L":" --- test_GetCharWidthInfo(): font.c:7396: Test failed: expected 0, got -8 font.c:7397: Test failed: expected 0, got -9 font.c:7398: Test failed: expected 0, got 1 https://test.winehq.org/data/patterns.html#gdi32:font They can be reproduced on w10pro64-hi-u8. Note that w10pro64-hi which uses the Hindi locale too but not UTF-8 (so the system locale is English) has its own set of totally unrelated failures. -- 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 52945] New: kernel32:sync - test_condvars_base() fails randomly on Windows 10 1709+
by WineHQ Bugzilla May 2, 2022

May 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=52945 Bug ID: 52945 Summary: kernel32:sync - test_condvars_base() fails randomly on Windows 10 1709+ 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:sync's test_condvars_base() fails randomly on Windows 10 1709+: sync.c:1859: Test failed: SleepConditionVariableCS should still return TRUE on crit unlock delay https://test.winehq.org/data/patterns.html#kernel32:sync Based on the current test results the failure happens roughly 11% of the time and may happen twice in a run about 0.8% of the time. It happens on both bare metal (cw-gtx560, cw-rx460) and in VMs so it's not a QEmu issue. Yet I have not been able to reproduce the failure so far, even when looping on test_condvars_base() 1000 times. I also tried to see if some other test was the trigger but that did not work out either. Back in the day I tentatively noted that the failures may have started on 2021-09-13 (cw-gtx560 1809) or 2021-10-01 (all others); but I was obviously never able to pinpoint it and given how elusive the failure is, you should take that with a pinch of salt. -- 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 51365] New: wininet:http causes urlmon:protocol to time out
by WineHQ Bugzilla May 1, 2022

May 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=51365 Bug ID: 51365 Summary: wininet:http causes urlmon:protocol to time out Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com If wininet:http is run before urlmon:url the latter will time out as follows: protocol.c:348: Test failed: unexpected call OnResponse protocol.c:839: Test failed: unexpected call ReportProgress_MIMETYPEAVAILABLE protocol.c:1101: Test failed: unexpected call ReportData protocol.c:3437: Test failed: wait timed out protocol.c:3439: Test failed: expected Switch protocol.c:3560: Testing http protocol (redirected, disable auto redirect)... protocol.c:469: QueryService(IID_IGetBindHandle) protocol.c:475: QueryService(IID_IWindowForBindingUI) protocol.c:1178: Test failed: unexpected call ReportResult protocol.c:1186: Test failed: hrResult = 800c0014, expected: 00000000 urlmon:protocol:0bd0 done (258) in 120s (0x800c0014 = INET_E_REDIRECT_FAILED) The timeout actually happens in test_http_protocol_url() on line 3437: ok( WaitForSingleObject(event_complete, 90000) == WAIT_OBJECT_0, "wait timed out\n" ); This actually happens on machines that use the wt-daily.bat script [1] because that script first runs the 32-bit tests (including wininet:http) and then the 64-bit tests and, obviously, no configuration 'reset' happens in between. Specifically this causes failures in the 64-bit urlmon:protocol results on cw-gtx560 and cw-rx460: https://test.winehq.org/data/patterns.html#urlmon:protocol [1] https://github.com/fgouget/wt-daily/blob/master/wt-daily.bat.template#L138 -- 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 46330] New: [Feature Request] Enable winelib on ppc64el
by wine-bugs＠winehq.org May 1, 2022

May 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=46330 Bug ID: 46330 Summary: [Feature Request] Enable winelib on ppc64el Product: Wine Version: unspecified Hardware: Other OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: tpearson(a)raptorengineering.com Distribution: --- With the resurgence in POWER hardware support and interest centering around the POWER8/POWER9 chips, it would be great to get winelib support for the ppc64el architecture. This would allow Windows open source applications to be used on these powerful machines (e.g. FEMM, SQLYog, etc.). -- 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