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

[Bug 52828] New: Incorrect instruments in MIDI playback over ALSA
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52828 Bug ID: 52828 Summary: Incorrect instruments in MIDI playback over ALSA Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark(a)darkok.xyz Distribution: --- Created attachment 72216 --> https://bugs.winehq.org/attachment.cgi?id=72216 MIDI file that is played noticably wrong Starting from Wine 7.5, some MIDIs aren't played back properly as they have the incorrect instruments, at least when I've tried playing them using aplaymidi on a VST using SAVIHost. Downloads: https://www.hermannseib.com/programs/savihostx64.zip https://cdn.roland.com/assets/media/zip/scva_win_trial.zip Steps to reproduce: 1. Execute "winetricks mfc90" to get a required DLL 2. Extract scva_win_trial.zip and install the Roland Sound Canvas VA VST 3. Extract savihostx64.zip, and move savihost.exe to "C:\Program Files\Roland\Sound Canvas VA" 4. Rename savihost.exe to "Sound Canvas VA.exe" 5. Run the renamed executable 6. Go to Devices>MIDI, and set Input Port 1 to "Midi Through Port-0" 7. Run "aplaymidi -p 14:0 smr_101.mid" to start playing the MIDI 8. In the VST, click "PART", and the correct instruments should be Vibraphone for the first three, and "KICK&SNARE" for the 11th. However, starting from Wine 7.5, these instruments are incorrectly set to "Piano 1" for the first three, and "Syn. Strings 1" for the 11th. -- 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 52866] New: vbscript:run fails in Wine in Arabic and Hebrew
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52866 Bug ID: 52866 Summary: vbscript:run fails in Wine in Arabic and Hebrew Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- vbscript:run fails in Wine in Arabic and Hebrew: run.c:1888: Test failed: unexpected call OnScriptError run.c:2933: Test failed: expected global_success_d run.c:2934: Test failed: expected global_success_i run.c:2936: Test failed: parse_script failed: 800a000d run.c:1204: Test failed: api.vbs: L"Err.number = 13" run.c:1204: Test failed: api.vbs: L"Err.number = 13" run.c:1874: Error in line 1162: 0 L"Type mismatch" run.c:1888: Test failed: unexpected call OnScriptError run.c:2933: Test failed: expected global_success_d run.c:2934: Test failed: expected global_success_i run.c:2936: Test failed: parse_script failed: 800a000d https://test.winehq.org/data/patterns.html#vbscript:run Incidentally these are our two right-to-left test locales so this may be related. A bisect shows that the failures started with this commit: commit ba43e4cfca97a9bba3e6575af82acbf011685862 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Mar 29 22:11:32 2022 +0200 kernelbase: Reimplement number formatting values in GetLocaleInfoW/Ex using the locale.nls data. 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 8

[Bug 48048] New: urlmon:protocol - The ftp test fail on Vista to Windows 8
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=48048 Bug ID: 48048 Summary: urlmon:protocol - The ftp test fail on Vista to Windows 8 Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: urlmon Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The ftp protocol test in urlmon:protocol fails frequently on Windows from Vista to Windows 8: protocol.c:1188: Test failed: hrResult = 800c0006, expected E_PENDING or S_OK protocol.c:1193: Test failed: dwError = 12111, expected ERROR_SUCCESS protocol.c:3656: Test failed: wait timed out urlmon:protocol:0700 done (258) in 120s Test failed: timed out Note: 800c0006 is INET_E_OBJECT_NOT_FOUND See https://test.winehq.org/data/tests/urlmon:protocol.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 5

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

06 May '22

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 06 May '22

06 May '22

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 02 May '22

02 May '22

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 02 May '22

02 May '22

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 02 May '22

02 May '22

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 02 May '22

02 May '22

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 02 May '22

02 May '22

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