October 2023 - Wine-bugs - list.winehq.org

[Bug 55658] New: psapi:psapi_main - test_EnumProcessModules*() fails on macOS
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55658 Bug ID: 55658 Summary: psapi:psapi_main - test_EnumProcessModules*() fails on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - test_EnumProcessModules*() fails on macOS: psapi_main.c:156: Test failed: got 0, error 5 psapi_main.c:158: Test failed: expected non-NULL module psapi_main.c:162: Test failed: got error 5 psapi_main.c:163: Test failed: got PÛ psapi_main.c:166: Test failed: got error 5 psapi_main.c:167: Test failed: got psapi_main.c:170: Test failed: got error 5 psapi_main.c:183: Test failed: got error 5 psapi_main.c:184: Test failed: third DLL in wow64 should be one of wow*.dll () psapi_main.c:239: Test failed: pcs-6432: 1: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 2: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 0: didn't succeed 5 psapi_main.c:239: Test failed: pcs-6432: 3: didn't succeed 5 psapi_main.c:507: Test failed: pcs-6432: expecting 32bit modules psapi_main.c:510: Test marked todo: pcs-6432: expecting 64bit modules psapi_main.c:345: Test failed: pcs-6432: 1: got error 5 psapi_main.c:346: Test failed: pcs-6432: 1: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 1: got error 5 psapi_main.c:349: Test failed: pcs-6432: 1: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 1: got error 5 psapi_main.c:353: Test failed: pcs-6432: 1: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 1: got entry point 0000000000000000 psapi_main.c:345: Test failed: pcs-6432: 0: got error 5 psapi_main.c:346: Test failed: pcs-6432: 0: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 0: got error 5 psapi_main.c:349: Test failed: pcs-6432: 0: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 0: got error 5 psapi_main.c:353: Test failed: pcs-6432: 0: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 0: got entry point 0000000000000000 psapi_main.c:345: Test failed: pcs-6432: 3: got error 5 psapi_main.c:346: Test failed: pcs-6432: 3: expecting msinfo32.exe but got psapi_main.c:348: Test failed: pcs-6432: 3: got error 5 psapi_main.c:349: Test failed: pcs-6432: 3: expecting C:\windows\syswow64\msinfo32.exe but got psapi_main.c:352: Test failed: pcs-6432: 3: got error 5 psapi_main.c:353: Test failed: pcs-6432: 3: expected 00000000DEADBEEF, got 0000000178010008 psapi_main.c:355: Test failed: pcs-6432: 3: got entry point 0000000000000000 psapi_main.c:529: Test succeeded inside todo block: pcs-6432: Wrong count 0 in C:\windows\syswow64 See https://test.winehq.org/data/patterns.html#psapi:psapi_main This set of failures started on 2023-09-14 and only happens on macOS (see Remi's rbernon-macos-* cloud test machines). -- 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 6

[Bug 55674] New: 64-bit wineserver/wine-preloader hangs on macOS 14.
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55674 Bug ID: 55674 Summary: 64-bit wineserver/wine-preloader hangs on macOS 14. Product: Wine Version: 8.16 Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jactry92(a)gmail.com This is a regression introduced by a81c53504ae32715e6e91bd020fdebd5bef20d48. Before this commit, I can run Notepad++ with a WOW64 build on macOS 14. But now, I can't even start `winecfg` and create a wineprefix. I don't reproduce this issue with 64-bit Wine on Linux, so this is a Mac-specific 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 5

[Bug 55708] New: cpython 3.12.0 fails to run on wine
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55708 Bug ID: 55708 Summary: cpython 3.12.0 fails to run on wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: propsys Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)bochs.info Distribution: --- cpython 3.12.0 (released today) fails to run in wine on Linux, due to a new module _wmi which depends on VariantToString. This is stubbed in wine's propsys.dll: "Unimplemented function propsys.dll.VariantToString called at address ..." It's unclear if anything else is broken, because the process halts here. -- 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 55241] New: The 64-bit winmm:capture & winmm:wave crash on Windows 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55241 Bug ID: 55241 Summary: The 64-bit winmm:capture & winmm:wave crash on Windows 8 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit winmm:capture & winmm:wave crash on Windows 8: capture.c:171: this is the last test seen before the exception 07d0:capture: unhandled exception c0000005 at 00007FFDC66DCF38 wave.c:686: this is the last test seen before the exception 0b14:wave: unhandled exception c0000005 at 00007FFDC66DCF38 See https://test.winehq.org/data/patterns.html#winmm:capture https://test.winehq.org/data/patterns.html#winmm:wave This started with the GitLab CI's switch to Debian 12 (bookworm) for the build system: * The winmm_test.exe binary produced by the TestBot's Debian 11-based build VM produces no failures when run on Windows while GitLab CI's binary for the same Wine version produces this set of failures. * And the TestBot runs the official WineTest builds on its Windows VMs which is why the failures appeared on 2023-07-10 which corresponds to this commit: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. Now the question is whether the new build environment revealed a preexisting bug in Wine, or if the new build environment itself is broken, or if the bug is elsewhere such as in the MinGW compiler. This is also likely the same issue as bug 55240. -- 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 54069] New: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54069 Bug ID: 54069 Summary: ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ddraw:ddraw7 - test_texture_wrong_caps() sometimes fails on Windows 8+. ddraw7.c:18954: Test failed: Got unexpected color 0x00000040. and ddraw7.c:18972: Test failed: Got unexpected color 0x00ff00ff. See https://test.winehq.org/data/patterns.html#ddraw:ddraw7 Notes: * There is no evidence of this happening on Windows 11. * This seems to only happen with Microsoft's "Microsoft Basic Display Adapter" driver: the "-1qxl" and "-2qxl" (dual-monitor) configuration use the "Red Hat QXL controller" driver and are are not affected. Neither are the AMD / NVIDIA PCI passthrough configurations. * The 0x00000040 result mostly happens on Windows 8 to Windows 10 1607 but it also happened a couple of times on Windows 10 21H2. Meanwhile the 0x00ff00ff result seems to only happen on Windows 10 2004+. * ddraw:ddraw1, ddraw:ddraw2 and ddraw:ddraw4 have a similar test function but don't have this failure. -- 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 43185] New: "Battle Bugs" game in unresponsive once game starts
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43185 Bug ID: 43185 Summary: "Battle Bugs" game in unresponsive once game starts Product: Wine Version: 2.9 Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: matt(a)nightrealms.com Distribution: --- Created attachment 58457 --> https://bugs.winehq.org/attachment.cgi?id=58457 Wine output from before starting the game When playing the free game "Battle Bugs" (https://ldjam.com/events/ludum-dare/38/battle-bugs) on 64 bit Linux, the game start screen loads just fine, and pressing an indicated key starts the game just fine, but once the game starts nothing is moving and the game doesn't respond to any keys. Got the same results with both versions of the executable, and both WINEARCH unspecified or set to win32 -- 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 6

[Bug 55211] New: Print file not truncated when printing to file in FrameMaker 8
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55211 Bug ID: 55211 Summary: Print file not truncated when printing to file in FrameMaker 8 Product: Wine Version: 8.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- A existing print file ist not truncated when printing to the same file again. So when printing a smaller document to the print file which was generated for a larger file, the resultung file contains garbage at its end. This happens in Framemaker 8 and may happen in other apps too. To reproduce - Install Framemaker from the given URL - Print the attached Document Large.fm to a file (select print to file in the printer dialog). Check the size of the generated file. - Print the attached Document Small.fm to the same file generated in the previous step. Check again the size of the file - its the same. Depending on the used Postscript interpreter reading the file fails because of the garbage at the files end. This is simple to see when using different documents as descibed above. When printing existing documents again after (even small) changes the resulting print file may be garbage without notice. -- 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 13

[Bug 55273] New: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55273 Bug ID: 55273 Summary: ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:wow64 - The 64-bit test_cpu_area() gets bad offsets on Windows 10 1607 & 1709: wow64.c:783: Test failed: 0:0: wrong offset 4 wow64.c:783: Test failed: 0:1: wrong offset 6 wow64.c:783: Test failed: 0:2: wrong offset 4 wow64.c:783: Test failed: 0:3: wrong offset 6 wow64.c:783: Test failed: 0:4: wrong offset 4 wow64.c:783: Test failed: 0:5: wrong offset 6 wow64.c:783: Test failed: 0:6: wrong offset 4 wow64.c:783: Test failed: 0:7: wrong offset 6 wow64.c:783: Test failed: 1:0: wrong offset 16 wow64.c:783: Test failed: 1:1: wrong offset 14 wow64.c:783: Test failed: 1:2: wrong offset 12 wow64.c:783: Test failed: 1:3: wrong offset 10 wow64.c:783: Test failed: 1:4: wrong offset 8 wow64.c:783: Test failed: 1:5: wrong offset 6 wow64.c:783: Test failed: 1:6: wrong offset 4 wow64.c:783: Test failed: 1:7: wrong offset 18 wow64.c:783: Test failed: 2:0: wrong offset 8 wow64.c:783: Test failed: 2:1: wrong offset 6 wow64.c:783: Test failed: 2:2: wrong offset 4 wow64.c:783: Test failed: 2:3: wrong offset 10 wow64.c:783: Test failed: 2:4: wrong offset 8 wow64.c:783: Test failed: 2:5: wrong offset 6 wow64.c:783: Test failed: 2:6: wrong offset 4 wow64.c:783: Test failed: 2:7: wrong offset 10 wow64.c:783: Test failed: 3:0: wrong offset 16 wow64.c:783: Test failed: 3:1: wrong offset 14 wow64.c:783: Test failed: 3:2: wrong offset 12 wow64.c:783: Test failed: 3:3: wrong offset 10 wow64.c:783: Test failed: 3:4: wrong offset 8 wow64.c:783: Test failed: 3:5: wrong offset 6 wow64.c:783: Test failed: 3:6: wrong offset 4 wow64.c:783: Test failed: 3:7: wrong offset 18 See https://test.winehq.org/data/patterns.html#ntdll:wow64 The failures started with GitLab CI's switch to Debian 12 for the WineTest builds which are used in the WineTest nightlies. However they also happen with binaries built on Debian 11 so in this case it is just a coincidence. See also bug 55272 for ntdll:exception crashes that started at the same time on the same set of machines. -- 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 55528] New: Vitis 2020.1 can't find its libraries (cmd.exe bug with nested one-line if statement that sets PATH)
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55528 Bug ID: 55528 Summary: Vitis 2020.1 can't find its libraries (cmd.exe bug with nested one-line if statement that sets PATH) Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75087 --> https://bugs.winehq.org/attachment.cgi?id=75087 Terminal output Steps to reproduce: 1. Run `tar -xvf Xilinx_Unified_2020.1_0602_1208.tar.gz` 2. Run `wine Xilinx_Unified_2020.1_0602_1208/xsetup.exe` 3. When the installer complains that it can't connect to the internet, click Ignore 4. Run `XIL_PA_NO_REDIST_CHECK=1 wine 'C:\Xilinx\Vitis\2020.1\bin\vitis.bat'` The following errors are printed to the terminal: Syntax error Can't recognize ')' as an internal or external command, or batch script. 0138:err:module:import_dll Library libboost_filesystem.dll (which is needed by L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe") not found 0138:err:module:import_dll Library libboost_program_options.dll (which is needed by L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe") not found 0138:err:module:import_dll Library librdi_common.dll (which is needed by L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe") not found 0138:err:module:LdrInitializeThunk Importing dlls for L"C:\\Xilinx\\Vitis\\2020.1\\bin\\unwrapped\\win64.o\\rdi_vitis.exe" failed, status c0000135 I was able to narrow down the problem to code in loader.bat that looks similar to this (this is a minimal example, these aren't the real variable names): set FOO=1 if %FOO% == 1 ( if %FOO% == 1 set PATH=C:\Xilinx\Vitis\2020.1\lib\win64.o;%PATH% if %FOO% == 1 ( echo %PATH% ) ) I don't know why Wine thinks that there is a syntax error in this code. There must be a bug in the command parser that is triggered by a nested one-line if statement that sets a variable. Registration is required to download Vitis. $ sha256sum Xilinx_Unified_2020.1_0602_1208.tar.gz a9e0f81a61eca260c4453ab93a8d17eac31956dd54d0d5fd74dc8b4f2727e3eb -- 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 55631] New: ntdll:file - test_file_rename_information fails on Windows 10 1607 and older
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55631 Bug ID: 55631 Summary: ntdll:file - test_file_rename_information fails on Windows 10 1607 and older Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:file - test_file_rename_information fails on Windows 10 1607 and older: file.c:1550: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1552: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1555: Test failed: file should not exist file.c:1558: Test failed: file should exist file.c:1565: Test failed: FileName expected L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F4E.tmp", got L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F4D.tmp" file.c:1594: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1624: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1626: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1629: Test failed: file should not exist file.c:1661: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1696: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:1731: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1733: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1736: Test failed: file should not exist file.c:1739: Test failed: file should exist file.c:1746: Test failed: FileName expected L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F68.tmp", got L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F57.tmp" file.c:1783: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:1827: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1865: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:1899: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:1901: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:1904: Test failed: file should not exist file.c:1940: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:1979: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2017: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2058: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2093: Test failed: res expected STATUS_OBJECT_NAME_COLLISION, got c0000003 file.c:2127: Test failed: res expected STATUS_ACCESS_DENIED, got c0000003 file.c:2161: Test failed: io.Status expected STATUS_SUCCESS, got deadbeef file.c:2163: Test failed: res expected STATUS_SUCCESS, got c0000003 file.c:2166: Test failed: file should not exist file.c:2169: Test failed: file should exist file.c:2176: Test failed: FileName expected L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F8D.tmp", got L"\\Users\\winetest\\AppData\\Local\\Temp\\foo5F8C.tmp" file.c:2203: Test failed: got io status 0xdeadbeef file.c:2205: Test failed: got status c0000003 See https://test.winehq.org/data/patterns.html#ntdll:file Where 0xc0000003 == STATUS_INVALID_INFO_CLASS These failures are systematic and started happening on 2023-09-19. A bisect shows that they started with the commit below: commit 67479f8c2fc03c2043b8414bc063e671e36fdbda Author: Joel Holdsworth <joel(a)airwebreathe.org.uk> Date: Fri Sep 15 17:49:52 2023 +0100 ntdll/tests: Test both FileRenameInformation and FileRenameInformationEx in test_file_rename_information. Signed-off-by: Joel Holdsworth <joel(a)airwebreathe.org.uk> -- 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