wine-bugs May 2022

wine-bugs@winehq.org

1 participants
3544 discussions

[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 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 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 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

[Bug 52861] New: kernel32:locale fails on Windows 10 1709
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52861 Bug ID: 52861 Summary: kernel32:locale fails 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:locale fails on Windows 10 1709: locale.c:4216: Test failed: failed 0 https://test.winehq.org/data/patterns.html#kernel32:locale This impacts all the Windows 1709 machines but no other Windows version. This is also a new test which was introduced by the commit below: commit b5561c8bba9a613c53ae4669c4adb7450e5f458d Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Wed Mar 23 11:02:57 2022 +0100 ntdll: Support UTF-8 codepage in RtlInitCodePageTable(). 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

[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 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 52857] New: msvcp140:msvcp140 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=52857 Bug ID: 52857 Summary: msvcp140:msvcp140 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: msvcp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msvcp140:msvcp140 fails in Windows 8.1 on the cw-rx460 machine msvcp140.c:1617: Test failed: Got unexpected err 87. msvcp140.c:1622: Test failed: Got unexpected err 87. https://test.winehq.org/data/patterns.html#msvcp140:msvcp140 These are new tests so unsurprisingly the failures are caused by the commit that introduced them: commit d72d596070eb28fd5f747fb6120d36f66ff93bec Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Mon Apr 11 21:44:35 2022 +0300 msvcp140: Implement _Copy_file(). Signed-off-by: Paul Gofman <pgofman(a)codeweavers.com> Signed-off-by: Piotr Caban <piotr(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The fact that only this specific Windows 8.1 configuration fails makes sense because it is the only one to have msvcp140 and it is a relatively old version: it is installed by the Radeon driver. However: * The w7u VM does have (a much newer) msvcp140 and has no failure. * The w1064v1607 VM has the same msvcp140 version and has no failure either. Furthermore kernel32:file also fails in the same way in the same configuration and shouldn't depend on msvcp140. So it's possible the issue is not related to msvcp140 at all. Here is a summary of the msvcp140 versions on the Windows 7, 8.1 and older Windows 10 machines: Win Machine msvcp140 win7 w7u 14.29.30037.0 win7 w7pro64 missing (at least for 64-bit) win81 cw-gtx560 missing win81 cw-rx460 14.0.23026.0 win81 w8 missing win81 w864 missing win1507 cw-gtx560 missing win1507 cw-rx460 missing win1507 w1064v1507 missing win1607 w1064v1607 14.0.23026.0 -- 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 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 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs May 2022