wine-bugs October 2023

wine-bugs@winehq.org

1 participants
3027 discussions

[Bug 54744] New: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=54744 Bug ID: 54744 Summary: explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com explorerframe:taskbarlist - test_ITaskbarList() sometimes gets E_NOTIMPL on Windows: taskbarlist.c:61: Test failed: Got hr 0x80004001. taskbarlist.c:66: Test failed: Got hr 0x80004001. See https://test.winehq.org/data/patterns.html#explorerframe:taskbarlist Where 0x80004001 == E_NOTIMPL On average this happens about once every other month on recent Windows 10 versions: * 2022-08-31 on w1064-tsign-64 (21h2) * 2022-11-14 on w1064-tsign-32 (21h2) * 2023-01-10 on fgtb-w10pro64-rx550-64 (22h2) * 2023-02-06 on w10pro64-rx550-64 (22h2) * 2023-03-27 on w10pro64-ar-64 (21h1) -- 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 43017] New: Unreal Tournament 2004/UT2004.exe crashes due to " intel_do_flush_locked failed: Cannot allocate memory"
by wine-bugs＠winehq.org 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=43017 Bug ID: 43017 Summary: Unreal Tournament 2004/UT2004.exe crashes due to "intel_do_flush_locked failed: Cannot allocate memory" Product: Wine Version: 2.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: krichter(a)posteo.de Distribution: --- Unreal Tournament 2004/UT2004.exe crashes due to `intel_do_flush_locked failed: Cannot allocate memory` the debug output of PlayOnLinux reads ``` [05/12/17 23:55:35] - Running wine-2.7 UT2004.exe (Working directory : /home/richter/.PlayOnLinux/wineprefix/UnrealT2004/drive_c/Program Files/Unreal Tournament 2004/System) err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: cannot open shared object file: No such file or directory err:winedevice:async_create_driver failed to create driver L"WineBus": c0000142 fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32e540,0x32e53c): stub fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS) err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:create_server class {96749377-3391-11d2-9ee3-00c04f797396} not registered err:ole:CoGetClassObject no class object {96749377-3391-11d2-9ee3-00c04f797396} could be created for context 0x7 fixme:win:EnumDisplayDevicesW ((null),0,0x32bc98,0x00000000), stub! fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1. err:xvidmode:ComputeGammaFromRamp low-biased gamma ramp (3604), rejected fixme:imm:ImmReleaseContext (0x1007c, 0x2165e0): stub fixme:hnetcfg:fw_profile_get_FirewallEnabled 0x6404c88, 0x32ccc4 err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1042267284)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1082643741)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129305379)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1017464658)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106373278)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1061644189)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103102115)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102202262)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127878391)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1133393126)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064431753)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056334452)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1103590910)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1128011843)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1012511863)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1129177136)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064579615)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107545964)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127492263)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1131588260)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1009667614)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1064940315)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1102388947)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1107645235)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127352012)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1106599611)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065065837)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1056114040)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1104285584)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1127422744)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=-1029644321)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1126051816)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_OPERATION in glUniform(location=1065075311)". err:d3d:wined3d_debug_callback 0x6369a18: "GL_INVALID_ENUM in glClampColorARB(clamp)". intel_do_flush_locked failed: Cannot allocate memory ``` -- 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 8

[Bug 55733] New: ntdll:file - test_file_rename_information_ex() fails on Windows 10 1607 & 1709
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55733 Bug ID: 55733 Summary: ntdll:file - test_file_rename_information_ex() fails 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:file - test_file_rename_information_ex() fails on Windows 10 1607 & 1709: file.c:2263: Test failed: res expected STATUS_SUCCESS, got c00000bb file.c:2265: Test failed: file should not exist See https://test.winehq.org/data/patterns.html#ntdll:file These failures are systematic and started on 2023-10-05. A bisect confirms they happen starting with the commit that added them: commit 07e40a6f9f70338d9810d50b606696b7be984d98 Author: Joel Holdsworth <joel(a)airwebreathe.org.uk> AuthorDate: Wed Sep 20 11:34:09 2023 +0100 ntdll/tests: Add tests for FILE_RENAME_IGNORE_READONLY_ATTRIBUTE. 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

[Bug 55648] New: ntdll:wow64 - test_peb_teb() crashes on macOS
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55648 Bug ID: 55648 Summary: ntdll:wow64 - test_peb_teb() crashes on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:wow64 - test_peb_teb() crashes on macOS: wow64.c:712: Test failed: RtlWow64GetSharedInfoProcess failed c0000022 wow64.c:716: Test failed: wrong page size cccccccc wow64.c:718: Test failed: wrong flags cccccccc wow64.c:720: Test failed: wrong machine cccc / 8664 wow64.c:722: Test failed: wrong machine cccc wow64.c:748: Test failed: DuplicateHandle failed 6 wow64.c:751: Test failed: NtMapViewOfSection failed c0000008 wow64.c:752: Test failed: unexpected size 0 wow64.c:764: Test failed: got 0 handle wow64.c:765: Test failed: got NULL data wow64.c:772: Test failed: NtMapViewOfSection failed c0000008 wow64.c:774: Test failed: invalid handle Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x000001400cc20e). See https://test.winehq.org/data/patterns.html#ntdll:wow64 The crashes started happening on 2023-09-14 (a day with no ntdll commit) and only happen 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 3

[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

[Bug 55627] New: secur32:negotiate & secur32:ntlm crash from a NULL dereference on macOS
by WineHQ Bugzilla 13 Oct '23

13 Oct '23

https://bugs.winehq.org/show_bug.cgi?id=55627 Bug ID: 55627 Summary: secur32:negotiate & secur32:ntlm crash from a NULL dereference on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com secur32:negotiate & secur32:ntlm crash from a NULL dereference on macOS: Unhandled exception: page fault on read access to 0x0000000000000008 in 64-bit code (0x0000017004f9ed). See https://test.winehq.org/data/patterns.html#secur32:negotiate https://test.winehq.org/data/patterns.html#secur32:ntlm Initially this looked like the same issue as secur32:secur32 (bug 55555), i.e. a missing libkrb5 library. But changes were made for that library and that test no longer crashes on macOS so this must be another issue. Also other secur32 test units don't crash. -- 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 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 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 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

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 October 2023