December 2022 - Wine-Bugs - list.winehq.org

[Bug 53252] New: d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10 1909+
by WineHQ Bugzilla Dec. 3, 2022

Dec. 3, 2022

https://bugs.winehq.org/show_bug.cgi?id=53252 Bug ID: 53252 Summary: d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10 1909+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d10core:d3d10core - test_occlusion_query() sometimes fails on Windows 10 1909+: d3d10core.c:4665: Test failed: Got unexpected query result 0x0000000000000000. https://test.winehq.org/data/patterns.html#d3d10core:d3d10core These failures only seem to happen on with Windows' basic 'VGA' driver (whether it's on top of QEmu's VGA or QXL GPU). They are also rare enough to cause false positives. -- 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 53465] New: conhost.exe:tty - test_tty_output() sometimes fails on Windows 10
by WineHQ Bugzilla Dec. 3, 2022

Dec. 3, 2022

https://bugs.winehq.org/show_bug.cgi?id=53465 Bug ID: 53465 Summary: conhost.exe:tty - test_tty_output() sometimes fails on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com conhost.exe:tty - test_tty_output() sometimes fails on Windows 10. There are only three known failures spread across two similar failure modes: * 2022-07-27 w10pro64-pt-BR * 2022-07-27 w10pro64-mx-MX (mixed locale) tty.c:1051: Test failed: avail = 3 tty.c:1051: Test failed: expected empty buffer, got "\x1b[m" tty.c:1058: Test failed: 0: expected "\x1b[9;4H" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1059: Test failed: 0: expected "5" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1060: Test failed: 0: expected "\x1b[4;3H" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1061: Test failed: 0: expected "\x1b[?25h" got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1062: Test failed: expected empty buffer, got "\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" * 2022-07-29 w10pro64-pt-BR tty.c:1055: Test failed: expected hide cursor escape tty.c:1057: Test failed: 0: expected "\x1b[30m" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1058: Test failed: 0: expected "\x1b[9;4H" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1059: Test failed: 0: expected "5" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1060: Test failed: 0: expected "\x1b[4;3H" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1061: Test failed: 0: expected "\x1b[?25h" got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" tty.c:1062: Test failed: expected empty buffer, got "\x1b[25l\x1b[30m\x1b[9;4H5\x1b[4;3H\x1b[?25h" -- 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 54059] New: user32:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=54059 Bug ID: 54059 Summary: user32:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:input - test_GetMouseMovePointsEx() sometimes fails on Windows 10+: input.c:1647: Test failed: expected to get 62 mouse move points but got 64 input.c:1649: Test failed: expected cursor position to be 30x30 but got 150 150 See https://test.winehq.org/data/patterns.html#user32:input This impacts Windows 10 from 1809 to Windows 11 but it seems it can also happen on Windows 7 (though in practice not on the TestBot VMs?). -- 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 1

[Bug 53474] New: Change in memory handling gives crash in Framemaker 8
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=53474 Bug ID: 53474 Summary: Change in memory handling gives crash in Framemaker 8 Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- The following commit commit a4966b6690b31c4884d07a8a745017adb6363834 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Thu Jun 9 14:13:53 2022 +0200 kernelbase: Cleanup and simplify (Global|Local)ReAlloc. Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> dlls/kernel32/heap.c | 22 ++++++++- dlls/kernel32/tests/heap.c | 15 ------- dlls/kernelbase/memory.c | 108 +++++++++++++++------------------------------ 3 files changed, 56 insertions(+), 89 deletions(-) leads to a crash in Framemaker 8. Reverting the patch on top of wine-7.14 solves the problem. To reproduce (simplest way): - Start Framemaker and create a new document - Open the print dialog (Ctrl-P) - Select another printer (lower part of the dialog) - Framemaker crashes with an internal error Framemaker generates a log file (which is IMHO useless but attached anyway) I can provide a demo version of framemaker if this would help. -- 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 54006] New: d3d8:device - test_reset() sometimes crashes on Windows 8+
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=54006 Bug ID: 54006 Summary: d3d8:device - test_reset() sometimes crashes 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 d3d8:device - test_reset() sometimes crashes. There are a few failure modes that look like they are related: device.c:1967: Test failed: Failed to reset device, hr 0x88760873. device.c:1967: this is the last test seen before the exception 163c:device: unhandled exception c0000005 at 74D3CC42 and device.c:2022: Test failed: Reset failed, hr 0x88760873. device.c:2024: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:2029: Test failed: GetBackBuffer failed, hr 0x8876086c. device.c:2031: Test failed: Got hr 0. device.c:2033: Test failed: Got hr 0. device.c:2033: this is the last test seen before the exception 0b00:device: unhandled exception c0000005 at 0043032C and device.c:1747: Test failed: Reset failed, hr 0x88760873. device.c:1749: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1761: Test failed: D3DVIEWPORT->Width = 400. device.c:1762: Test failed: D3DVIEWPORT->Height = 300. device.c:1764: this is the last test seen before the exception 03c0:device: unhandled exception c0000005 at 743FA86E and device.c:1807: Test failed: Reset failed, hr 0x80070057. device.c:1809: Test failed: TestCooperativeLevel failed, hr 0x88760869. device.c:1835: Test failed: D3DVIEWPORT->Width = 500, expected 200. device.c:1837: Test failed: D3DVIEWPORT->Height = 400, expected 150. device.c:1840: this is the last test seen before the exception 09d8:device: unhandled exception c0000005 at 7448946E See https://test.winehq.org/data/patterns.html#d3d8:device Where: 0x88760873 == ??? 0x88760869 == D3DERR_DEVICENOTRESET 0x80070057 == E_INVALIDARG -- 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 53685] New: ntdll:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=53685 Bug ID: 53685 Summary: ntdll:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds 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:rtl is broken on Windows 10 1809+ in the GitLab WineTest builds: rtl.c:2790: Running test 1 (compressed_size=10, uncompressed_size=8, status=0x00000000) rtl.c:2790: this is the last test seen before the exception 1538:rtl: unhandled exception c0000005 at 005532C0 https://test.winehq.org/data/patterns.html#ntdll:rtl The failures started on 2022-07-26 which is when the WineTest builds switched from the old build system to GitLab. A test with winetest-889fe64d9f2e.exe (built on 2022-07-25) confirms that this test still succeeds when using binaries from the old build system. -- 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 53663] New: Subnautica Below Zero permanently loses focus if the active window changes
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=53663 Bug ID: 53663 Summary: Subnautica Below Zero permanently loses focus if the active window changes Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Distribution: --- In the game Subnautica: Below Zero (version 45391), when playing in windowed mode, if the game window loses focus, the game will no longer accept mouse/keyboard input even after the window regains focus again. If the game is set to pause when in the background, it remains paused even after the window regains focus. This bug also occurs with stable Wine (7.0), but it does not occur with Proton 7.0.4 (the game properly accepts input again and unpauses when the window regains focus). -- 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 43812] New: Divinity Original Sin 2 some parts display white ingame
by wine-bugs＠winehq.org Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=43812 Bug ID: 43812 Summary: Divinity Original Sin 2 some parts display white ingame Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: holzminister(a)t-online.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59354 --> https://bugs.winehq.org/attachment.cgi?id=59354 log from terminal I play Divinity Original Sin 2 with the workaround described in bug https://bugs.winehq.org/show_bug.cgi?id=43660 ("winetricks xact"). With this the game works quiet well. But there is one small but annoying bug for that kinda game. When you try to read books or other papers you find ingame they only show up white and empty. Also the buff icons of the unitframes are plain white. (See screenshots). -- 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 9

[Bug 54053] New: user32:input - test_GetRawInputBuffer() gets spurious WM_INPUT on Windows and Wine
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=54053 Bug ID: 54053 Summary: user32:input - test_GetRawInputBuffer() gets spurious WM_INPUT on Windows and Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:input - test_GetRawInputBuffer() gets spurious WM_INPUT messages on Windows and Wine: * 2022-12-01 on w7u_el (32-bit) for MR!1619 input.c:2406: Test failed: Spurious WM_INPUT messages * 2022-11-11 on w1064 (64-bit) input.c:2404: Test failed: Spurious WM_INPUT messages * 2022-08-29 on debiant (wow64) input.c:2404: Test failed: Spurious WM_INPUT messages See https://test.winehq.org/data/patterns.html#user32:input All in all there has been 12 instances on Windows (7 to 10) and 6 on Wine in the past 6 months. -- 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 1

[Bug 54051] New: winhttp:notification gets unexpected 'reconnections' on Windows 10 1507
by WineHQ Bugzilla Dec. 2, 2022

Dec. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=54051 Bug ID: 54051 Summary: winhttp:notification gets unexpected 'reconnections' on Windows 10 1507 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com winhttp:notification gets unexpected 'reconnections' on Windows 10 1507: notification.c:117: Test failed: 1555: expected status 0x10 got 0x1 notification.c:1701: Test failed: data too short notification.c:117: Test failed: 1555: expected status 0x10 got 0x2 notification.c:117: Test failed: 1555: expected status 0x10 got 0x4 notification.c:117: Test failed: 1555: expected status 0x10 got 0x4 notification.c:117: Test failed: 1555: expected status 0x10 got 0x8 notification.c:117: Test failed: 1584: expected status 0x20000 got 0x200000 winhttp:notification:0e58 done (258) in 120s 527B See https://test.winehq.org/data/patterns.html#winhttp:notification Where: 0x1 == WINHTTP_CALLBACK_STATUS_RESOLVING_NAME 0x2 == WINHTTP_CALLBACK_STATUS_NAME_RESOLVED 0x4 == WINHTTP_CALLBACK_STATUS_CONNECTING_TO_SERVER 0x8 == WINHTTP_CALLBACK_STATUS_CONNECTED_TO_SERVER 0x10 == WINHTTP_CALLBACK_STATUS_SENDING_REQUEST 0x20000 == WINHTTP_CALLBACK_STATUS_HEADERS_AVAILABLE 0x200000 == WINHTTP_CALLBACK_STATUS_REQUEST_ERROR While the reconnection messages are specific to Windows 10 1507, the request error (0x200000) is not. The timeout is probably related to the latter and may be a separate issue. Note also that winhttp:notification gets timeouts in many other cases. -- 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 1