wine-bugs

wine-bugs@winehq.org

1 participants
158780 discussions

[Bug 54046] New: wiaservc:wia sometimes times out on Windows 10 21H1 & 22H2
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54046 Bug ID: 54046 Summary: wiaservc:wia sometimes times out on Windows 10 21H1 & 22H2 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wia Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wiaservc:wia sometimes times out on Windows 10 21H1 & 22H2: wiaservc:wia:1204 done (258) in 120s See https://test.winehq.org/data/patterns.html#wiaservc:wia This failure is pretty rare and since there is no trace whatsoever it's unclear where the timeout occurs. Normally the test runs in "0 seconds" so it's not a speed issue. Note: On Windows 11 it crashes instead of timing out. These two issues may well be related (memory corruption?). -- 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 47874] New: kernel32:debugger sometimes fails getting EXCEPTION_DEBUG_EVENT
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=47874 Bug ID: 47874 Summary: kernel32:debugger sometimes fails getting EXCEPTION_DEBUG_EVENT Product: Wine Version: 4.17 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:debugger sometimes gets the following failure: debugger.c:1424: Test failed: dwDebugEventCode = 1 https://test.winehq.org/data/tests/kernel32:debugger.html This value seems to correspond to EXCEPTION_DEBUG_EVENT. This failure has been seen on the wxppro and w2003std TestBot VMs and on the fg-win7u64 family of VMware VMs. It also happened on the cw1-hd6800-t64 Windows 8.1 real hardware machine (which also means it happens in both 32 and 64 bit tests). However it never happened on the Windows 10 VMs so it may be a bug in older Windows versions. -- 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 54021] New: Microsoft Report Builder: crashes on startup
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54021 Bug ID: 54021 Summary: Microsoft Report Builder: crashes on startup Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mohd.akram(a)outlook.com Distribution: --- Created attachment 73590 --> https://bugs.winehq.org/attachment.cgi?id=73590 log of running `wine MSReportBuilder.exe` I get a System.NullReferenceException exception when running Microsoft Report Builder (log attached). It is free to download from https://www.microsoft.com/en-us/download/details.aspx?id=53613. -- 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 54044] New: quartz:memallocator - test_sample_properties() often gets an unexpected sample start on Windows 11
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54044 Bug ID: 54044 Summary: quartz:memallocator - test_sample_properties() often gets an unexpected sample start on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com quartz:memallocator - test_sample_properties() often gets an unexpected sample start on Windows 11: memallocator.c:476: Test failed: Got sample start 7dd8e0. memallocator.c:643: Test failed: Got sample start 7dd8e0. See https://test.winehq.org/data/patterns.html#quartz:memallocator -- 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 52005] New: wmvcore:wmvcore crashes in Wine on cw-gtx560
by WineHQ Bugzilla 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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@PC:~$ env WINEPREFIX="/home/joe/.wine" wine-stable C:\\PROG\~FBU\\TRAC\~EK1\\PDF_\~VHK\\PDFXEdit.exe 010c:err:ole:CoUninitialize Mismatched CoUninitialize joe@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 01 Dec '22

01 Dec '22

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 01 Dec '22

01 Dec '22

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

[Bug 53513] New: wininet:ftp regularly gets timeouts
by WineHQ Bugzilla 30 Nov '22

30 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53513 Bug ID: 53513 Summary: wininet:ftp regularly gets timeouts Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wininet:ftp regularly gets timeouts. The error happens in various places leading to somewhat different error message sequences: ftp.c:302: Test failed: Expected ERROR_INTERNET_EXTENDED_ERROR, got 12002 ftp.c:373: 0 550 new_directory_deadbeef: Permission denied ftp.c:373: 0 550 non_existent_file_deadbeef: Operation not permitted ftp.c:478: Test failed: Expected ERROR_FTP_TRANSFER_IN_PROGRESS, got 12002 or ftp.c:263: Test failed: Expected FtpGetFileA to succeed ftp.c:264: Test failed: Local file should have been created ftp.c:282: Test failed: Expected ERROR_INTERNET_EXTENDED_ERROR, got 12002 ftp.c:373: 0 550 new_directory_deadbeef: Permission denied ftp.c:373: 0 550 non_existent_file_deadbeef: Operation not permitted ftp.c:878: Test failed: Expected ERROR_INTERNET_EXTENDED_ERROR, got 12002 ftp.c:886: Test failed: Expected ERROR_NO_MORE_FILES, got 12002 or ftp.c:801: Test failed: Expected FtpFindFirstFileA to pass ftp.c:806: Test failed: Expected FtpFindFirstFileA to fail ftp.c:807: Test failed: Expected ERROR_FTP_TRANSFER_IN_PROGRESS, got 0 ftp.c:864: Test failed: Expected ERROR_FTP_TRANSFER_IN_PROGRESS, got 12002 https://test.winehq.org/data/patterns.html#wininet:ftp Where 12002 == ERROR_INTERNET_TIMEOUT. These failures started some time between 2022-07-15 and 2022-07-29 and impact all Windows versions while the test did not change since 2022-03-09. So it is possible that this is a caused by a configuration change in server the test connects to: ftp.winehq.org & www.winehq.org. -- 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 26978] New: tokenadmin.exe crash : Unimplemented function winscard.dll.SCardListReadersA
by wine-bugs＠winehq.org 30 Nov '22

30 Nov '22

http://bugs.winehq.org/show_bug.cgi?id=26978 Summary: tokenadmin.exe crash : Unimplemented function winscard.dll.SCardListReadersA Product: Wine Version: 1.3.18 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34407) --> (http://bugs.winehq.org/attachment.cgi?id=34407) LOG: tokenadmin.exe crash tokenadmin.exe is a smart card reader manager from ICBC online bank. 1. donwload http://www.icbc.com.cn/icbc/html/download/dkq/SafeSign_ICBC_Per.exe 2. install SafeSign_ICBC_Per.exe with wine $ LANG=en_US.utf8 wine SafeSign_ICBC_Per.exe 3. run tokenadmin.exe $ cd $WINEPREFIX/"drive_c/Program Files/ICBCEbankTools/G&D/Management Utility" $ wine tokenadmin.exe see LOG: tokenadmin.exe crash -- 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 14

[Bug 53963] New: d3d8:device & d3d9:device sometimes break threading and WineTest
by WineHQ Bugzilla 30 Nov '22

30 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53963 Bug ID: 53963 Summary: d3d8:device & d3d9:device sometimes break threading and WineTest Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d8:device & d3d9:device sometimes break threading, causing all the tests that follow to get stuck. The typical symptom is a series of tests returning 258: d3d9:d3d9ex:080c done (0) in 43s 9467B d3d9:device start dlls/d3d9/tests/device.c d3d9:device:0278 done (258) in 120s 0B d3d9:stateblock start dlls/d3d9/tests/stateblock.c d3d9:stateblock:0288 done (258) in 120s 0B d3d9:visual start dlls/d3d9/tests/visual.c d3d9:visual:0290 done (258) in 120s 0B See https://test.winehq.org/data/patterns.html When this happens all the tests that follow get stuck which makes it impossible to run the full WineTest suite, hence the lack of WineTest results on some machines in the patterns page above. Notes: * This can also happen in d3d8:device. Consequently the first test that gets stuck is either d3d8:stateblock or d3d9:stateblock. * winedbg also gets stuck as soon as it displays the prompt :-( * This only impacts dual-screen configurations. This is why this breaks the debian11 and debiant (dual-screen) VMs but not debian11b and fgtbdebian11 (single-screen). Note that in the run above there is no d3d9:device trace which means it did not run right but there is no other indication of what is wrong. Fortunately on one run d3d9:device produced a proper crash dump implicating RtlCreateUserThread() which would make sense given the symptoms: d3d9:device start dlls/d3d9/tests/device.c device.c:780: Test marked todo: Test 0: Got unexpected FVF 0, expected 0x2. device.c:780: Test marked todo: Test 1: Got unexpected FVF 0, expected 0x4. device.c:1119: Tests skipped: Multisampling not supported for D3DFMT_X8R8G8B8, skipping test. device.c:4821: Test failed: Received unexpected WM_SIZE message. device.c:2852: Test failed: Failed to create a D3D object. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00434da7). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00434da7 ESP:0071f7b0 EBP:0071f868 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000000 EBX:00000000 ECX:0071f750 EDX:00000000 ESI:005a0068 EDI:0071f824 Stack dump: 0x0071f7b0: 00000000 004de71c 004df984 00cf0000 0x0071f7c0: 00000064 00000064 000000a0 000000a0 0x0071f7d0: 00000000 00000000 00000000 00000000 0x0071f7e0: 00000000 00000002 00000012 005a0068 0x0071f7f0: 688e32f0 00001897 00000000 00000000 0x0071f800: 00000000 004df9fc 00000000 00000007 Backtrace: =>0 0x00434da7 in d3d9_test (+0x34da7) (0x0071f868) 1 0x00459367 in d3d9_test (+0x59367) (0x0071fde8) 2 0x004d8151 in d3d9_test (+0xd8151) (0x0071fee8) 3 0x004d7b3f in d3d9_test (+0xd7b3f) (0x0071ff30) 4 0x7b62a1f0 in kernel32 (+0x2a1f0) (0x0071ff48) 5 0x7bc5d727 in ntdll (+0x5d727) (0x0071ff5c) 6 0x7bc5df50 RtlCreateUserThread(entry=004D7AC0, arg=7FFD1000) [Z:\home\winetest\tools\testbot\var\wine\dlls\ntdll\thread.c:306] in ntdll (0x0071ffec) 0x00434da7 d3d9_test+0x34da7: movl 0x0(%ebx),%eax And on stderr: 0658:err:d3d:wined3d_adapter_create_output Failed to initialise output L"\\\\.\\DISPLAY1", hr 0x80070057. wine: Unhandled page fault on read access to 00000000 at address 00434DA7 (thread 0658), starting debugger... The million dollar question: how to reproduce the failure? * First you need a dual-screen test configuration. * The crash is not systematic. It can be necessary to run the test 4 - 8 maybe 10 times to get a crash. It's hard to tell. * After some runs d3d9:device gets an underflow in GenerateRampFromGamma() and crashes from that. I don't have a log of that crash but I remember that the gamma was around 0.00003 (plus or minus a few zeroes). So it is likely that the test does not restore the gamma correctly, resulting in it running with this nonsensically low gamma value after a while. Regardless, this seems to prevent d3d*:device from crashing in the way we want which means after a few runs it may be necessary to restart the X server :-( * Also sometimes, again after running the tests a number of times, one of the screens 'disappears' (virt-viewer says something like 'connecting to display' or it will show a single abnormally wide desktop) and then the issue cannot be reproduced anymore. This also requires restarting the X server :-( This failure started on 2022-11-17 but because it is such a pain to reproduce and even more to bisect I was not able to pinpoint the commit causing it. However Rémi points out that it first appeared in the following merge request: https://gitlab.winehq.org/wine/wine/-/merge_requests/1399 And when that got merged into Wine all hell broke loose: all debian11 test runs started timing out. It's not clear how it's related to threading though. Also it only touches programs/explorer so it's strange that it would cause threading issues in d3d9:device. So it's possible it only triggers a preexisting bug somehow. -- 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 51153] New: A winegstreamer change caused a new quartz:filtergraph failure in Wine
by WineHQ Bugzilla 30 Nov '22

30 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=51153 Bug ID: 51153 Summary: A winegstreamer change caused a new quartz:filtergraph failure in Wine Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- quartz:filtergraph started failing in Wine on 2021-04-26: http://winetest.dolphin/data/patterns.html#quartz:filtergraph filtergraph.c:440: Test failed: GetState() failed: 40237 Strangely this failure only happens on the TestBot's debiant2 VM. A bisect showed this failure to be caused by the patch below: commit d7fecebe93938bf1ef2349ac74413e28d6b8e153 Author: Anton Baskanov <baskanov(a)gmail.com> Date: Mon Apr 26 09:51:24 2021 +0700 winegstreamer: Allow setting the stop position to the stream duration. Since we no longer stop the GStreamer pipeline, it does not reset the stop position for us. Fixes a hang during intro video playback in RC Cars. Signed-off-by: Anton Baskanov <baskanov(a)gmail.com> Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> See also: https://www.winehq.org/pipermail/wine-devel/2021-April/185904.html -- 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 9

[Bug 53998] New: vbscript tests fail in englisch UTF8 locale
by WineHQ Bugzilla 30 Nov '22

30 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53998 Bug ID: 53998 Summary: vbscript tests fail in englisch UTF8 locale Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: sloper42(a)yahoo.com Distribution: --- After #52872 was fixed, we get now test failures. === w10pro64_en_AE_u8 (64 bit report) === vbscript: run.c:1206: Test failed: api.vbs: L"Err.number = 0" run.c:1206: Test failed: api.vbs: L"Err.description = " run.c:1206: Test failed: api.vbs: L"Err.number = 0" This happens because chr(-1) now succeeds in utf8 locale. We need to fix the tests. -- 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 54018] New: kernel32:fiber has many failures on Windows 11
by WineHQ Bugzilla 30 Nov '22

30 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=54018 Bug ID: 54018 Summary: kernel32:fiber has many failures on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernel32:fiber has many failures on Windows 11 21H2: fiber.c:338: Test failed: Got nonzero FlsListHead. fiber.c:339: Test failed: Got unexpected FlsHighIndex 1701. fiber.c:359: Test failed: Got unexpected size 000000C4. fiber.c:377: Test failed: Got unexpected unknown FFFFFFFF, i 0, j 5. fiber.c:380: Test failed: Got unexpected callback 00000000, i 0, j 5. [...] fiber.c:359: Test failed: Got unexpected size 00000304. [...many many more failures on lines 359, 377 and 380...] fiber.c:395: Test failed: Got unexpected status 0. fiber.c:400: Test failed: Got unexpected status 0xc000000d. fiber.c:401: Test failed: Got unexpected callback call count 0. fiber.c:406: Test failed: Got unexpected callback 00457190. fiber.c:425: Test failed: Got unexpected status 0xc00000a0. fiber.c:453: Test failed: Got unexpected size 0000002C. [...many more failures on line 453...] See https://test.winehq.org/data/patterns.html#kernel32:fiber -- 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 54017] New: dwmapi:dwmapi - test_DwmGetCompositionTimingInfo() fails on AMD GPUs
by WineHQ Bugzilla 30 Nov '22

30 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=54017 Bug ID: 54017 Summary: dwmapi:dwmapi - test_DwmGetCompositionTimingInfo() fails on AMD GPUs Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dwmapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dwmapi:dwmapi - test_DwmGetCompositionTimingInfo() fails on (PCI passthrough) AMD and NVIDIA VMs: * the TestBot's Windows 11 NVIDIA RTX3050 VM * the TestBot's Windows 11 AMD RX6600 VM * my Windows 10 22H2 AMD RX550 VM RTX3050 + HDMI/DisplayPort dongle: dwmapi.c:81: Test failed: Got wrong monitor refresh period 28b07. RX6600 + HDMI/DisplayPort dongle: dwmapi.c:81: Test failed: Got wrong monitor refresh period 28b20. RX550 + HDMI screen: dwmapi.c:81: Test failed: Got wrong monitor refresh period 28bb1. See https://test.winehq.org/data/patterns.html#dwmapi:dwmapi Note that this test succeeds on both of the TestBot's plain QEmu w11pro64 test configuration (virtual QXL GPU). This test has two other failures that also impact QXL (see bug 54016). -- 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 53265] New: mmdevapi:capture - test_capture() has timing-related failures on Windows
by WineHQ Bugzilla 29 Nov '22

29 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53265 Bug ID: 53265 Summary: mmdevapi:capture - test_capture() has timing-related failures on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mmdevapi:capture - test_capture() has timing-related failures on Windows: capture.c:282: Test failed: Position 1719 last 896 frames 448 https://test.winehq.org/data/patterns.html#mmdevapi:capture The failures happen randomly but frequently on Windows 8 to Windows 10 1809. However, because the message includes a duration, it is prone to cause false positives (see also bug 53126 for a similar failure in mmdevapi:render). Furthermore mmdevapi:capture has other systematic failures on Windows 10 1909+ that probably just mask this one (see bug 53264). So one should assume that this timing-related failure impacts all Windows 10 versions. -- 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 53433] New: mmdevapi:capture - test_capture() sometimes fails after resuming capture
by WineHQ Bugzilla 29 Nov '22

29 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53433 Bug ID: 53433 Summary: mmdevapi:capture - test_capture() sometimes fails after resuming capture Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mmdevapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mmdevapi:capture - test_capture() sometimes fails after resuming capture: capture.c:301: Cont'ed position 2103 pad 21548 flags 0, amount of frames locked: 448 capture.c:325: Restart position 2615 pad 21100 flags 1, amount of frames locked: 448 capture.c:330: Test failed: Position 2615 expected 2551 capture.c:331: Test failed: flags 1 https://test.winehq.org/data/patterns.html#mmdevapi:capture As of today there are 3 known instances of these failures (2022-06-28, 2022-07-11, 2022-07-28) and all 3 happened on Windows 8. Also are independent from the failures in bug 53265. -- 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 53281] New: d3d9:d3d9ex - test_wndproc() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8+
by WineHQ Bugzilla 29 Nov '22

29 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53281 Bug ID: 53281 Summary: d3d9:d3d9ex - test_wndproc() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8+ 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 d3d9:d3d9ex - test_wndproc() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8+: d3d9ex.c:3117: Test failed: Received WM_WINDOWPOSCHANGED but did not expect it, i=0. (also happens with i=1) https://test.winehq.org/data/patterns.html#ddraw:ddraw1 Note that a similar failure seems to happen with KDE in Wine but there is more than one WM_WINDOWPOSCHANGED message so it may be different (see fg-deb64). -- 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 53979] New: d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_WINDOWPOSCHANGING message in Wine
by WineHQ Bugzilla 29 Nov '22

29 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=53979 Bug ID: 53979 Summary: d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_WINDOWPOSCHANGING message in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_WINDOWPOSCHANGING message in Wine: d3d9ex.c:3115: Test failed: Expected message 0x46 for window 0x1, but didn't receive it, i=1. See https://test.winehq.org/data/patterns.html#d3d9:d3d9ex This seems to be mostly happening on my desktop (Intel + KDE), but it also happened on the debian11 VM in MR!1538 (unrelated heap refactoring). So it's not specific to KDE and can indeed happen 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 2

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