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.
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.
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.
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.