December 2021 - Wine-bugs - list.winehq.org

[Bug 52068] New: hid:device times out randomly in test_get_input_report()
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52068 Bug ID: 52068 Summary: hid:device times out randomly in test_get_input_report() Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- hid:device times out randomly (>10% of the time) in test_get_input_report(): device.c:406: HidD_GetInputRpeort tests on device :L"Wine HID mouse" hid:device:05cc done (258) in 120s https://test.winehq.org/data/patterns.html#hid:device So far this only happened in the pure 32-bit builds but it does impact various machines (cw-gtx560, cw-rx460, some debiant2 configurations and fg-deb64). A bisect shows that the timeouts started with this commit: commit fca0f18d0857d6aee67c6ef652c31c6810292270 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Fri Nov 19 09:39:39 2021 +0100 winebus.sys: Avoid unnecessary scaling of effect parameter values. 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 51895] New: ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51895 Bug ID: 51895 Summary: ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ucrtbase Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ucrtbase:misc fma(inf, 0, 0) 'succeeds' unexpectedly on some machines: misc.c:799: Test failed: fma(inf, 0.000000, 0.000000) got errno -1 misc.c:799: Test failed: fma(0.000000, inf, 0.000000) got errno -1 misc.c:799: Test failed: fma(inf, 1.000000, -inf) got errno -1 misc.c:799: Test failed: fma(-inf, 1.000000, inf) got errno -1 misc.c:799: Test failed: fma(1.000000, inf, -inf) got errno -1 misc.c:799: Test failed: fma(1.000000, -inf, inf) got errno -1 https://test.winehq.org/data/patterns.html#ucrtbase:misc Additional tests seem to indicate this is related to the CPU features: * The test succeeds on all TestBot VMs, and they also all return _get_FMA3_enabled() = 0. * The test fails on fgtb-w10pro64 (i7-4790K) where _get_FMA3_enabled() returns 1. * Paul Gofman reported getting this failure on a modern AMD processor where _get_FMA3_enabled() presumably returns 1 too. Yet: * The documentation says _get_FMA3_enabled() is about transcendental functions. fma() is not one of them. * _get_FMA3_enabled() is only available in 64-bit code but the failures happen on both 32- and 64-bit code. So it does look like this is related to the fma() implementation (x87/SSE2/other?) picked by the ucrtbase library as opposed to library version issues. But the details are murky and there may be some other common factor. The MSDN documentation does say that fma(inf,0,0) should return NaN, which it does. The documentation is less clear on errno which is what we test. https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/fma-fmaf-f… So maybe applications cannot rely on errno being set (particularly on modern processors) and this particular test should be removed. -- 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 51490] New: dinput:device has a random failure in overlapped_format_tests() on Windows 8.1
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51490 Bug ID: 51490 Summary: dinput:device has a random failure in overlapped_format_tests() on Windows 8.1 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput:device has a random failure on the w8 VM: https://test.winehq.org/data/patterns.html#dinput:device device.c:374: Test failed: keydown for D did not register It sort of looks like a race condition though the pump_messages() call should take care of that. The failing test (and all of overlapped_format_tests()) was added by the following commit. commit d10887b8f56792ebcca717ccc28a289f7bcaf107 Author: Arkadiusz Hiler <ahiler(a)codeweavers.com> AuthorDate: Thu Jul 8 13:03:21 2021 +0300 dinput: Don't add 'default value 0' entries to the data transform. This helps when dealing with the quirky c_dfDIJoystick2 format, which defines all the sliders as overlapping, i.e. rglSlider[2], rglVSlider[2], rglASlider[2] and rglFSlider[2] all share the same offset. With the Linux backends, if the device exposes enough axes (e.g. some HOTAS) we end up using rglSlider. Let's make sure we don't unnecessarily override the values there. Signed-off-by: Arkadiusz Hiler <ahiler(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 4

[Bug 52075] New: dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52075 Bug ID: 52075 Summary: dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dinput8:device, dinput8:dinput and dinput8:hid cannot run on Windows 7 anymore because they now need GetOverlappedResultEx() which is not available. https://test.winehq.org/data/patterns.html#dinput8:device https://test.winehq.org/data/patterns.html#dinput8:dinput https://test.winehq.org/data/patterns.html#dinput8:hid Before that the tests could run on Windows 7 and even succeeded. The call to GetOverlappedResultEx() was introduced in the commit below: commit 3f110402f6a503d7c312694092e25fc48737c980 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Wed Nov 17 11:51:48 2021 +0100 dinput8/tests: Add some HID device gain report tests. 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 7

[Bug 52077] New: Windows PC Health Check crashes on unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFeatureStateChangeNotification
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=52077 Bug ID: 52077 Summary: Windows PC Health Check crashes on unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFea tureStateChangeNotification Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Steps to reproduce: 1. Run `winecfg` and set the Windows version to Windows 10. 2. Run `wine msiexec /i WindowsPCHealthCheckSetup.msi` and click through the installer. 3. When the installer finishes and the app tries to start, you will see: wine: Call from 000000007B01230E to unimplemented function api-ms-win-core-featurestaging-l1-1-0.dll.SubscribeFeatureStateChangeNotification, aborting $ sha256sum WindowsPCHealthCheckSetup.msi 45c82e40ed0e27db7c55e0554512631b8f175b06d9b2d2cf58db52b18f0913fa -- 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 51557] New: GetSystemFirmwareTable fails to return SMBIOS on Apple Silicon Macs
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51557 Bug ID: 51557 Summary: GetSystemFirmwareTable fails to return SMBIOS on Apple Silicon Macs Product: Wine Version: 6.14 Hardware: aarch64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com The macOS implementation of GetSystemFirmwareTable() retrieves the system's actual SMBIOS table using IOKit. This fails on Apple Silicon/ARM64 Macs, since they don't have an SMBIOS table. This breaks any applications that depend on getting an SMBIOS table (like the Rockstar Games Launcher) or that look for the HKLM/Hardware/Description/System/BIOS registry keys. I think the fix will be to use the SMBIOS table creation functions used by Linux currently, with strings and data (serial number, UUID, etc) coming from IOKit if possible. -- 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 51971] New: postgresql-9.3 installer needs scrrun:folder_CreateTextFile implementation
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51971 Bug ID: 51971 Summary: postgresql-9.3 installer needs scrrun:folder_CreateTextFile implementation Product: Wine Version: 6.20 Hardware: x86-64 URL: https://web.archive.org/web/20211009084355if_/https:// get.enterprisedb.com/postgresql/postgresql-9.3.25-1-wi ndows-x64.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: sloper42(a)yahoo.com Distribution: --- This is followup from https://bugs.winehq.org/show_bug.cgi?id=51911 Test with postgresql-9.3 installer from [1]. It runs a script during installation similar to https://github.com/three-plus-three/tpt_env_amd64/blob/master/postgresql/in… that reports non-critical error to main install, script itself terminates. This part ' Execute a command Function DoCmd(strCmd) Dim objBatchFile Set objBatchFile = objTempFolder.CreateTextFile(strBatchFile, True) objBatchFile.WriteLine "@ECHO OFF" ... leads to fixme:scrrun:folder_CreateTextFile (0000000000075E90)->(L"rad36105.tx" ffffffff 0 000000000064EF60): stub [1] https://www.enterprisedb.com/postgresql-tutorial-resources-training?cid=340 -- 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 48119] New: The tests sometimes trigger "critical section is not acquired" errors
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=48119 Bug ID: 48119 Summary: The tests sometimes trigger "critical section is not acquired" errors Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The logs of most test runs, WineTest and others, contain critical section errors complaining that the critical section was not acquired before being released. Most are caused by the following two tests: msvcp120:msvcp120 intentionally triggers one such error in test_threads__Mtx(). It's easy to identify because it follows a bunch of CreateSymbolicLinkA() fixmes: 0044:fixme:file:CreateSymbolicLinkA ("tr2_test_dir/f1_symlink" "tr2_test_dir/f1" 0): stub 0044:fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: beef 0044:err:ntdll:RtlLeaveCriticalSection section 0x622088 is not acquired ntdll:rtl intentionally triggers two such errors in test_RtlLeaveCriticalSection(). They stand alone but would typically follow a bunch of RtlGetCompressionWorkSpaceSize fixmes from previous tests: https://testbot.winehq.org/JobDetails.pl?Key=60096 0009:err:ntdll:RtlLeaveCriticalSection section 0x7bfd88 is not acquired 0009:err:ntdll:RtlLeaveCriticalSection section 0x7bfd88 is not acquired But there are other logs that contain this error with no identified source. For instance in task 60103/4/2 (wow64) which is for an unrelated patch and only runs kernel32 tests which do not normally trigger this error: https://testbot.winehq.org/JobDetails.pl?Key=60103#k402 [...] Extracting: Done (1 of 1) Running tests 003e:err:ntdll:RtlLeaveCriticalSection section 0x14c80 is not acquired 002e:fixme:console:GetConsoleProcessList ((nil),0): stub [...] Or task 59774/4/1 (win32) which only ran comctl32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59774#k401 Or task 59426/1/1 (wow32) which only ran user32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59426 Or task 59176/3/1 (wow32/wow64?) which, again, only ran user32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59176#k301 Or task 59042/1/1 (wow32/wow64?) which, again, only ran user32 tests: https://testbot.winehq.org/JobDetails.pl?Key=59042#k101 -- 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 25193] New: Dasher does not operate correctly
by wine-bugs＠winehq.org 03 Dec '21

03 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=25193 Summary: Dasher does not operate correctly Product: Wine Version: 1.3.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: physicspirate(a)yahoo.ca Greetings, I've attempted to run Dasher(http://appdb.winehq.org/objectManager.php?sClass=version&iId=21982&i… and it does not appear to be loading or functioning correctly. I've attached a screenshot of what happens after loading. There is a gray box up top, and it appears to be non responsive. There also seems to be some problems with the networking as I have a high speed connection, and their servers tell me my latency is too high. If I run the same program on windows it runs like a dream. -- 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 13

[Bug 51307] New: msvcp140:msvcp140 fails on msvcp140 >= 14.25
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51307 Bug ID: 51307 Summary: msvcp140:msvcp140 fails on msvcp140 >= 14.25 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com On cw-rx460 machines that have either Radeon 21.3.2 or 21.4.1 the 64-bit msvcp140:msvcp140 test fails: https://test.winehq.org/data/patterns.html#msvcp140:msvcp140 msvcp140.c:1257: Test failed: ret = 37, expected 39 msvcp140.c:1258: Test failed: buf = The operation completed successfully.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaThe operation completed successfully. , expected The operation completed successfully. This is probably because the Radeon driver upgrades the 64-bit msvcp140.dll. Currently we have: Radeon msvcp140 cw-rx460-1507 19.11.3 14.14.26429.4 cw-rx460-1709 19.11.3 14.14.26429.4 cw-rx460-1809 19.11.3 14.14.26429.4 cw-rx460-1909 21.4.1 14.25.28508.3 cw-rx460-2009 21.4.1 14.25.28508.3 Also: w1064v1507 - - w1064v1607 - 14.0.23026.0 w1064v1709 - 14.0.23026.0 w1064v1809 - 14.0.23026.0 w1064v1909 - 14.0.23026.0 w10pro64 (2004) - 14.0.23026.0 w1064 (2009) - 14.0.23026.0 Note that the 14.0.23026.0 version comes from the "Visual C++ 2015 redistributables" package [1]. So all Radeon drivers actually install a newer version. But according to Chocolatey there are quite a few even newer versions, the current latest being 14.29.30037. But there does not seem to be any microsoft.com download URLs for it :-( https://community.chocolatey.org/packages/vcredist140#versionhistory [1] https://wiki.winehq.org/Wine_TestBot_VMs#msvcp140.2C_msvcr140.2C_ucrtbase -- 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