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

[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

[Bug 51415] New: Windows PC Health Check requires msvcp_win.dll
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51415 Bug ID: 51415 Summary: Windows PC Health Check requires msvcp_win.dll Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcp 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: 0164:err:module:import_dll Library msvcp_win.dll (which is needed by L"C:\\users\\alex\\AppData\\Local\\PCHealthCheck\\PCHealthClient.dll") not found This DLL appears to be yet another copy of the Microsoft C++ runtime. $ 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 5

[Bug 51834] New: EMF DC emits invalid EMF when calling StretchDiBits with info->bmiHeader.biSizeImage = 0
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51834 Bug ID: 51834 Summary: EMF DC emits invalid EMF when calling StretchDiBits with info->bmiHeader.biSizeImage = 0 Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: jacek(a)codeweavers.com, zzhang(a)codeweavers.com Distribution: --- BITMAPINFOHEADER allows setting biSizeImage to zero when biCompression is BI_RGB. However, the Wine EMF DC does not handle this case and takes the biSizeImage value as-is. This results in an invalid Enhanced Metafile output. -- 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 51733] New: CreateProcess does not properly set the current directory of the new process.
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51733 Bug ID: 51733 Summary: CreateProcess does not properly set the current directory of the new process. Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: johnfound(a)asm32.info Distribution: --- Regression. The current directory of the new process, created with CreateProcessW is always set to "/" (z:\) instead of the current directory of the parent process. I am testing with the following call: The last version that works properly is WINE 6.12 -- 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 49181] New: msvcrt_test.exe: missing entry point _point_get_sbh_threshold
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=49181 Bug ID: 49181 Summary: msvcrt_test.exe: missing entry point _point_get_sbh_threshold Product: Wine Version: 5.8 Hardware: arm OS: Windows Status: NEW Keywords: download, testcase Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 49179 Similar to 49180, when running winetest.exe on armv7/surface rt, msvcrt_test.exe throws an error dialog: The procedure entry point _get_sbh_threshold could not be located in the dynamic link library C:\Users\User\AppData\Local\Temp\wct\msvcrt_test.exe -- 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 50985] New: ns_name_skip is glibc specific, causes failure to build on musl
by WineHQ Bugzilla 03 Dec '21

03 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=50985 Bug ID: 50985 Summary: ns_name_skip is glibc specific, causes failure to build on musl Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dnsapi Assignee: wine-bugs(a)winehq.org Reporter: abenson+winehq(a)gmail.com Distribution: --- 6.6 introduced a reliance on glibc-specific calls in dlls/dnsapi/libresolv.c in commit 5f44c46164a5c0c50fffdf6cda9980a74079e1ac. Specifically, musl does not implement ns_name_skip, and the library fails at link time. -- 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