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

[Bug 52005] New: wmvcore:wmvcore crashes in Wine on cw-gtx560
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=52005 Bug ID: 52005 Summary: wmvcore:wmvcore crashes in Wine on cw-gtx560 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- wmvcore:wmvcore now crashes in Wine on cw-gtx560: https://test.winehq.org/data/patterns.html#wmvcore:wmvcore wmvcore.c:603: Test marked todo: Got hr 0x80004001. nouveau: kernel rejected pushbuf: No such device nouveau: ch4: krec 0 pushes 1 bufs 10 relocs 0 nouveau: ch4: buf 00000000 00000002 00000004 00000004 00000000 nouveau: ch4: buf 00000001 00000006 00000004 00000000 00000004 nouveau: ch4: buf 00000002 0000001e 00000004 00000004 00000000 nouveau: ch4: buf 00000003 00000020 00000002 00000000 00000002 nouveau: ch4: buf 00000004 00000021 00000004 00000004 00000000 nouveau: ch4: buf 00000005 0000001f 00000002 00000000 00000002 nouveau: ch4: buf 00000006 00000023 00000004 00000004 00000000 nouveau: ch4: buf 00000007 00000022 00000002 00000000 00000002 nouveau: ch4: buf 00000008 00000025 00000004 00000004 00000000 nouveau: ch4: buf 00000009 00000024 00000002 00000000 00000002 nouveau: ch4: psh 00000000 0000001f44 00000020a4 nouveau: 0x200140c5 nouveau: 0x00000100 nouveau: 0x20054088 nouveau: 0x00000030 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x00000001 nouveau: 0x00000000 nouveau: 0x200240c3 nouveau: 0x00000000 nouveau: 0x01a5c000 nouveau: 0x2002408e nouveau: 0x00000000 nouveau: 0x01a58000 nouveau: 0x200240d3 nouveau: 0x00000000 nouveau: 0x00000000 nouveau: 0x200240c7 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x200140c0 nouveau: 0x00100010 nouveau: 0x200140c5 nouveau: 0x00000100 nouveau: 0x20054088 nouveau: 0x00000030 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x00000001 nouveau: 0x00000000 nouveau: 0x200240c3 nouveau: 0x00000000 nouveau: 0x01a64000 nouveau: 0x2002408e nouveau: 0x00000000 nouveau: 0x01a60000 nouveau: 0x200240d3 nouveau: 0x00000000 nouveau: 0x00000000 nouveau: 0x200240c7 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x200140c0 nouveau: 0x00100010 nouveau: 0x200140c5 nouveau: 0x00000100 nouveau: 0x20054088 nouveau: 0x00000030 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x00000001 nouveau: 0x00000000 nouveau: 0x200240c3 nouveau: 0x00000000 nouveau: 0x01a6c000 nouveau: 0x2002408e nouveau: 0x00000000 nouveau: 0x01a68000 nouveau: 0x200240d3 nouveau: 0x00000000 nouveau: 0x00000000 nouveau: 0x200240c7 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x200140c0 nouveau: 0x00100010 nouveau: 0x200140c5 nouveau: 0x00000100 nouveau: 0x20054088 nouveau: 0x00000030 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x00000001 nouveau: 0x00000000 nouveau: 0x200240c3 nouveau: 0x00000000 nouveau: 0x01a74000 nouveau: 0x2002408e nouveau: 0x00000000 nouveau: 0x01a70000 nouveau: 0x200240d3 nouveau: 0x00000000 nouveau: 0x00000000 nouveau: 0x200240c7 nouveau: 0x00000100 nouveau: 0x00000040 nouveau: 0x200140c0 nouveau: 0x00100010 wmvcore: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed. 01b8:trace:seh:dispatch_exception code=80000101 flags=1 addr=F7F8E559 ip=f7f8e559 tid=01b8 01b8:warn:seh:dispatch_exception EXCEPTION_WINE_ASSERTION exception (code=80000101) raised The crash is clearly related to the nouveau driver, probably because GStreamer uses hardware decoding. This explains why the crash only happens on cw-gtx560 since that's the TestBot's only NVidia machine. Note also that the crash did not happen before the commit below: commit 87e4c289e46701c6f582e95c330eefb6fc5ec68a Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Mon Oct 25 18:52:13 2021 -0500 winegstreamer: Implement IWMProfile::GetStreamCount(). Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Unfortunately there is no backtrace but adding traces helps reconstruct a partial call stack: In test_sync_reader_streaming(): tests/wmvcore.c:605: hr = IWMSyncReader_Close(reader); /* first call */ wm_syncreader.c:64: return wm_reader_close(&reader->reader); wm_reader.c:1508: wg_parser_disconnect(reader->wg_parser); -- 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

[Bug 54041] New: wmvcore:wmvcore - test_sync_reader_types() sometimes crashes in Wine
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54041 Bug ID: 54041 Summary: wmvcore:wmvcore - test_sync_reader_types() sometimes crashes in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- wmvcore:wmvcore - test_sync_reader_types() sometimes crashes in Wine: wmvcore.c:1511: Test marked todo: Stream 0: Got output number 0. wmvcore.c:1576: Test marked todo: Stream 0: Got hr 0. wmvcore.c:1666: Test marked todo: Stream 0: Format 0: Got hr 0xc00d0041. wmvcore.c:1666: Test marked todo: Stream 0: Format 1: Got hr 0xc00d0041. wmvcore.c:1666: Test marked todo: Stream 0: Format 2: Got hr 0xc00d0041. wmvcore.c:1617: Test failed: Stream 0: Format 3: Got hr 0x8007000e. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00410d09). [...useless backtrace...] See https://test.winehq.org/data/patterns.html#wmvcore:wmvcore Where: 0xc00d0041 == NS_E_INCOMPATIBLE_FORMAT 0x8007000e == E_OUTOFMEMORY There are only three known instances of this crash: * 2022-11-10 on debian11-win32-zh-CN This is the first known instance which means it never happened in the previous 5.5 months. * 2022-11-14 on debian11-win32 for MR!1350 * 2022-11-29 on latestmaster (Linux Mint 21, en-GB) So this may be caused by a Wine patch that got committed some time in late October or early November. -- 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 54039] New: wmvcore:wmvcore - test_async_reader_streaming() sometimes times out in Wine
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54039 Bug ID: 54039 Summary: wmvcore:wmvcore - test_async_reader_streaming() sometimes times out in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmp&wmvcore Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- wmvcore:wmvcore - test_async_reader_streaming() sometimes times out in Wine: wmvcore.c:3009: Test failed: Wait timed out. See https://test.winehq.org/data/patterns.html#wmvcore:wmvcore Note that the wait on that line is just 1 second. Maybe the processing got delayed a bit and increasing the timeout would be a reasonable fix? The first instance of this failure is on 2022-09-16 and there has been about 3 instances per month since; and none in the 3 preceding months. Also the TestBot started running two VMs per host around 2022-10-25 (and certainly after 2022-10-02). So any processing delay cannot be attributed to this TestBot configuration change. So this may be related to Wine / test changes (like 453b0a92dbe4 which changes test_async_reader_streaming() 3 days before the first 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 1

[Bug 54038] New: user32:win - test_window_info() sometimes gets an unexpected window status on Windows
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54038 Bug ID: 54038 Summary: user32:win - test_window_info() sometimes gets an unexpected window status on Windows 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:win - test_window_info() sometimes gets an unexpected window status on Windows: win.c:1237: Test failed: wrong dwWindowStatus: 0000 != 0001 active 004A021A fg 00010122 in hook HCBT_MINMAX See https://test.winehq.org/data/patterns.html#user32:win This happens mostly on w7u-* and w11pro64-amd but also happened once on fgtb-w10pro64. -- 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 54001] New: user32:win - test_mdi() sometimes fails on Windows 8 and Windows 10 1607
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54001 Bug ID: 54001 Summary: user32:win - test_mdi() sometimes fails on Windows 8 and Windows 10 1607 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:win - test_mdi() sometimes fails on Windows 8 and Windows 10 1607: win.c:2688: Test failed: style 0x200000: expected !100 win.c:2688: Test failed: style 0x300000: expected !100 See https://test.winehq.org/data/patterns.html#user32:win More precisely: * This failure mode happened systematically on w1064v1607 from 2022-08-24 to 2022-11-17 but there is no record of it ever happening outside that range. * The w1064v1607 snapshot has been updated on 2022-11-20. While that may seem to rule out the snapshot update as the cause for the change in behavior it is possible that the successful 2022-11-18 results were (backlogged and) run on the new 2022-11-20 snapshot. * It's not clear what could have happened on 2022-08-24 to cause the failure to start happening. * This failure mode also happened on the w864 VM on the following dates: - 2022-06-03 w864-64 (twice) - 2022-11-18 w8adm (32-bit) - 2022-11-22 w8adm (32-bit) - 2022-11-23 w8adm (32-bit) and w864-32 The w864 snapshot was last updated on 2022-06-06. Because these failures are rare on Windows 8 they have caused some TestBot 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 54022] New: d3d11:d3d11 - test_clear_buffer_unordered_access_view() fails on w11pro64_nv
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54022 Bug ID: 54022 Summary: d3d11:d3d11 - test_clear_buffer_unordered_access_view() fails on w11pro64_nv 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 d3d11:d3d11 - test_clear_buffer_unordered_access_view() fails on w11pro64_nv: d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. ... d3d11.c:16646: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080 at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f. d3d11.c:16647: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080 at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f. d3d11.c:16648: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080 at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f. d3d11.c:16653: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080 at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f. d3d11.c:16654: Test failed: Got 0xffffffff, expected 0x7f7e7d7c or 0x80808080 at 128, uvec4 0xffffff7c, 0xffffff7d, 0xffffff7e, 0xffffff7f. d3d11.c:16655: Test failed: Got 0xffffffff, expected 0xfefefefe or 0x80808080 at 128, uvec4 0xfefefefe, 0xfefefefe, 0xfefefefe, 0xfefefefe. See https://test.winehq.org/data/patterns.html#d3d11:d3d11 Note: w11pro64_nv is the TestBot's NVIDIA RTX3050 PCI passthrough Windows 11 21H2 VM. The plain QXL (QEmu), and AMD PCI passthrough test configurations have d3d11:d3d11 failures too but in other test functions. -- 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 54036] New: user32:msg - test_paint_messages() sometimes gets an invalid WM_NCPAINT wParam in Wine (GitLab CI)
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54036 Bug ID: 54036 Summary: user32:msg - test_paint_messages() sometimes gets an invalid WM_NCPAINT wParam in Wine (GitLab CI) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:msg - test_paint_messages() sometimes gets an invalid WM_NCPAINT wParam in Wine: msg.c:8472: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1 got 0x52040090 msg.c:8497: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1 got 0x270400a1 msg.c:8527: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1 got 0x58040096 msg.c:8540: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1 got 0x3304009d msg.c:8554: Test failed: InvalidateErase: 0: in msg 0x0085 expecting wParam 0x1 got 0x6f040090 Where 0x85 == WM_NCPAINT See https://test.winehq.org/data/patterns.html#user32:msg Strangely enough this only happens in the GitLab CI Wine environment. As such it has impacted multiple MRs (e.g. MR!1342 MR!1341 MR!1326). This is also very similar to bug 53129 except that: * Bug 53129 has extra "region" test failures that don't happen here. * The places where the failures occur in test_paint_messages() seem a bit different. * This only happens in Wine whereas bug 53129 only happens on Windows 7. -- 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 54029] New: PDF-XChange Editor - Error [System]: Call not implemented
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54029 Bug ID: 54029 Summary: PDF-XChange Editor - Error [System]: Call not implemented Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: klasse(a)partyheld.de Distribution: --- Created attachment 73597 --> https://bugs.winehq.org/attachment.cgi?id=73597 Screenshot of the error message Upon closing of the PDF-XChange Editor, the attached error message appears. When the PDF-XChange Editor is started from the terminal, "010c:err:ole:CoUninitialize Mismatched CoUninitialize" appears upon closure of the Editor as follows: joe(a)PC:~$ env WINEPREFIX="/home/joe/.wine" wine-stable C:\\PROG\~FBU\\TRAC\~EK1\\PDF_\~VHK\\PDFXEdit.exe 010c:err:ole:CoUninitialize Mismatched CoUninitialize joe(a)PC:~$ Other than that, PDF-XChange Editor appears to work normally. (Only a brief trial was done.) The default Ubuntu Mate 22.10 installation of Wine is used: wine-7.0 (Ubuntu 7.0~repack-8) PDF-XChange Editor: Version: 9.5, build 365.0 [ ] (Nov 28 2022; 16:25:46) The issue did not appear with the previous Ubuntu Mate version (22.04) and the previously used PDF-XChange Editor version 9.5, build 361.0. -- 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 51219] New: Deferring EC_COMPLETE introduced two new quartz:filtergraph failures
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=51219 Bug ID: 51219 Summary: Deferring EC_COMPLETE introduced two new quartz:filtergraph failures Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Deferring EC_COMPLETE in strmbase introduced two new quartz:filtergraph failures: https://test.winehq.org/data/patterns.html#quartz:filtergraph filtergraph.c:515: Test failed: didn't get EOS filtergraph.c:519: Test failed: expected 1243c8, got 0 The commit that introduced this change is: commit 82b86d470488ae266d3ccd46ae4a6750ff3e79eb Author: Anton Baskanov <baskanov(a)gmail.com> AuthorDate: Wed May 26 23:46:43 2021 +0700 strmbase: Defer EC_COMPLETE until the renderer is running. Signed-off-by: Anton Baskanov <baskanov(a)gmail.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Note: * On cw-gtx560 and cw-rx460 only the 64-bit tests are impacted. This is because these machines are missing the gstreamer1.0-plugins-bad:i386 due an incompatibility with the :amd64 package in Debian 10. In turn this causes a skip (L"test.mpg": codec not supported) which avoids the failure. * The TestBot's debiant2 VM is on Debian Testing where it was possible to install both the 32- and 64-bit versions of tgstreamer1.0-plugins-bad so that both 32- and 64-bit versions of Wine are failing. -- 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 54033] New: user32:msg - The test_scrollwindowex() is sometimes empty, missing WM_PAINT on w7u
by WineHQ Bugzilla Dec. 1, 2022

Dec. 1, 2022

https://bugs.winehq.org/show_bug.cgi?id=54033 Bug ID: 54033 Summary: user32:msg - The test_scrollwindowex() is sometimes empty, missing WM_PAINT on w7u 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:msg - The test_scrollwindowex() is sometimes empty, missing WM_PAINT on w7u: msg.c:11943: Test failed: ScrollWindowEx: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:11943: Failed sequence ScrollWindowEx: msg.c:11943: 0: expected: msg 000f - actual: nothing msg.c:11954: Test failed: ScrollWindowEx: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:11954: Failed sequence ScrollWindowEx: msg.c:11954: 0: expected: msg 000f - actual: nothing msg.c:11964: Failed sequence ScrollWindowEx: msg.c:11968: Test failed: ScrollWindowEx: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:11968: Failed sequence ScrollWindowEx: msg.c:11968: 0: expected: msg 000f - actual: nothing msg.c:11978: Test failed: ScrollWindow: 0: the msg sequence is not complete: expected 000f - actual 0000 msg.c:11978: Failed sequence ScrollWindow: msg.c:11978: 0: expected: msg 000f - actual: nothing See https://test.winehq.org/data/patterns.html#user32:msg This failure goes back to at least 2022-06-06. It happens (almost?) systematically on w7u-2qxl (dual-monitor) but also happens, more rarely, on the other (single-monitor) w7u configurations (which is when it causes false positives). There is no record of this failure happening on w7pro64 however. -- 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