- Wine-Devel - list.winehq.org

Wine related spam
by Fabian Maurer July 18, 2022

July 18, 2022

I already told you to not spam random people with wine related mails. Seriously, I'll put you on my instant-delete list and just ignore everything in the future if you don't stop. @Others How do you deal with stuff like this? Just filter it out immediately? Regards, Fabian Maurer On Montag, 18. Juli 2022 10:20:21 CEST you wrote: > Some info from Wine 7.13

2 1

Re: [PATCH v4 2/3] riched20: Add font fallback support.
by Marvin July 18, 2022

July 18, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119249 Your paranoid android. === w10pro64_ar (64 bit report) === riched20: editor.c:5469: Test failed: test paste: strcmp = 1, text='testing paste

1 0

Re: [PATCH v5 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin July 18, 2022

July 18, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119242 Your paranoid android. === w1064_tsign (64 bit report) === user32: win.c:10947: Test failed: pos = 014a015e === w10pro64 (64 bit report) === user32: win.c:10947: Test failed: pos = 014a015e === debian11 (32 bit Hindi:India report) === user32: win.c:8998: Test failed: Unexpected event was delivered

1 0

Re: [PATCH v5 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin July 18, 2022

July 18, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119241 Your paranoid android. === w10pro64_ar (64 bit report) === user32: win.c:4641: Test failed: hwnd 000000000005025C/000000000005025C message 0200 win.c:4643: Test failed: wparam 0 win.c:4654: Test failed: hwnd 000000000005025C/000000000005025C message 0203 win.c:4658: Test failed: message 0202 available === w10pro64_ja (64 bit report) === user32: win.c:10957: Test failed: msg.message = 1e

1 0

Re: [PATCH 2/2] urlmon/tests: Trace why the test file creation failed.
by Marvin July 18, 2022

July 18, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119218 Your paranoid android. === w7u_2qxl (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1324 url.c:1492: Test failed: wrong thread 1324 === w7u_adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2172 url.c:1492: Test failed: wrong thread 2172 === w7u_el (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2216 url.c:1466: Test failed: progress 32: status = 200 === w8 (32 bit report) === urlmon: url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 2780 url.c:1492: Test failed: wrong thread 2780 === w8adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2804 url.c:1492: Test failed: wrong thread 2804 === w864 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1204 url.c:1466: Test failed: progress 64: status = 302 url.c:1466: Test failed: progress 3: status = 302 === w1064v1507 (32 bit report) === urlmon: url.c:1462: Test failed: progress 3: hres = 1, expected 0 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (32 bit report) === urlmon: url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7740 url.c:1492: Test failed: wrong thread 7740 === w1064 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7412 url.c:1492: Test failed: wrong thread 7412 url.c:1466: Test failed: progress 64: status = 302 === w1064_tsign (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 8140 url.c:1492: Test failed: wrong thread 8140 url.c:1466: Test failed: progress 64: status = 302 === w10pro64 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7752 url.c:1492: Test failed: wrong thread 7752 === w864 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1466: Test failed: progress 64: status = 200 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 url.c:1640: Test failed: unexpected call OnProgress_FINDINGRESOURCE === w1064v1809 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7512 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7512 === w1064 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7324 url.c:1492: Test failed: wrong thread 7324 url.c:1466: Test failed: progress 64: status = 302 === w1064_2qxl (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7804 url.c:1492: Test failed: wrong thread 7804 url.c:1466: Test failed: progress 64: status = 302 === w1064_adm (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7324 url.c:1466: Test failed: progress 64: status = 302 url.c:1492: Test failed: wrong thread 7324 === w1064_tsign (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 6996 url.c:1492: Test failed: wrong thread 6996 === w10pro64 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7652 url.c:1492: Test failed: wrong thread 7652 === w10pro64_en_AE_u8 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5892 url.c:1492: Test failed: wrong thread 5892 === w10pro64_ar (64 bit report) === urlmon: url.c:1492: Test failed: url.c:1662: Test failed: unexpected call OnProgress_REDIRECTING url.c:1492: Test failed: wrong thread 8292 === w10pro64_ja (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3088 url.c:1466: Test failed: progress 64: status = 302 url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 3088 === w10pro64_zh_CN (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4540 url.c:1492: Test failed: wrong thread 4540

1 0

Re: [PATCH 4/5] urlmon/tests: Fix the spelling of a trace() message.
by Marvin July 18, 2022

July 18, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119211 Your paranoid android. === w7u_2qxl (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1276 url.c:1492: Test failed: wrong thread 1124 === w7u_adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2196 url.c:1492: Test failed: wrong thread 2200 === w7u_el (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2212 url.c:1492: Test failed: wrong thread 2256 === w8 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2896 url.c:1492: Test failed: wrong thread 2896 === w8adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2512 url.c:1492: Test failed: url.c:1796: Test failed: wrong thread 2512 === w864 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2708 url.c:1492: Test failed: wrong thread 2708 url.c:1466: Test failed: progress 64: status = 200 === w1064v1507 (32 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (32 bit report) === urlmon: url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7732 url.c:1492: Test failed: wrong thread 7732 url.c:1466: Test failed: progress 64: status = 200 === w1064 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7380 url.c:1492: Test failed: wrong thread 7380 url.c:1466: Test failed: progress 64: status = 302 === w1064_tsign (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7684 url.c:1492: Test failed: wrong thread 7684 url.c:1466: Test failed: progress 64: status = 302 === w10pro64 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7752 url.c:1492: Test failed: wrong thread 7752 === w864 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1796: Test failed: unexpected code 64 url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 3032 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 3: status = 200 url.c:1466: Test failed: progress 32: status = 200 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7576 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7576 === w1064 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7304 url.c:1466: Test failed: progress 64: status = 302 === w1064_2qxl (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7708 url.c:1466: Test failed: progress 64: status = 302 url.c:1492: Test failed: wrong thread 7708 === w1064_adm (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5924 url.c:1492: Test failed: wrong thread 5924 === w1064_tsign (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4076 url.c:1462: Test failed: progress 3: hres = 1, expected 0 url.c:1466: Test failed: progress 32: status = 200 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1492: Test failed: wrong thread 4076 url.c:1466: Test failed: progress 64: status = 200 === w10pro64 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7668 url.c:1492: Test failed: wrong thread 7668 === w10pro64_en_AE_u8 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2848 url.c:1492: Test failed: wrong thread 2848 === w10pro64_ar (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5872 url.c:1492: Test failed: wrong thread 5872 === w10pro64_ja (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4472 url.c:1492: Test failed: wrong thread 4472 url.c:1466: Test failed: progress 64: status = 302 === w10pro64_zh_CN (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 8316 url.c:1492: Test failed: wrong thread 8316

1 0

'wrc' weirdness
by Gisle Vanem July 17, 2022

July 17, 2022

Hello again list. I'm still struggling with understanding the build of Wine on Win-10 using MSVC or clang-cl. E.g. the 'wrc' program behaves rather different from MSVC's 'rc'. When for example using 'wrc' to build 'attrib.exe', the output of 'attrib.exe /?' looks like this: ATTRIB - Displays or changes file attributes. Syntax: ATTRIB [+R | -R] [+A | -A ] [+S | -S] [+H | -H] [drive:][path][filename] [/S [/D]] Where: + Sets an attribute. ---------------- All lines are doubled up (?!). But using 'rc', there is this issue: ATTRIB - Displays or changes file attributes. Syntax: ATTRIB [+R | -R] [+A | -A ] [+S | -S] [+H | -H] [drive:][path][filename] \ [/S [/D]] \Where: \ + Sets an attribute. \ - Clears an attribute. -------------- The extra '\' at each line (!?). I've tried converting 'attrib.rc' to Unix/DOS line-endings to no avail. And BTW, I used: wrc -D__WINESRC__ -I../../include --output objdir/attrib.res attrib.rc to compile it. What is going on with this, please? -- --gv

2 4

[PATCH v3 1/2] qedit/tests: Test adding a reference to the sample from ISampleGrabberCB::SampleCB().
by Zebediah Figura July 16, 2022

July 16, 2022

From: Brendan McGrath <brendan(a)redmandi.com> Unravel Two adds a reference to the IMediaSample during its callback. This patch adds a test that checks if an application does do this, that it can free it later and the reference count will finish at zero. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51616 Signed-off-by: Brendan McGrath <brendan(a)redmandi.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> --- v3: Some stylistic fixups; make commit messages a bit more specific. dlls/qedit/tests/mediadet.c | 28 +++++++++++++++++++++++----- 1 file changed, 23 insertions(+), 5 deletions(-) diff --git a/dlls/qedit/tests/mediadet.c b/dlls/qedit/tests/mediadet.c index 3202baca924..6e7017f865c 100644 --- a/dlls/qedit/tests/mediadet.c +++ b/dlls/qedit/tests/mediadet.c @@ -866,6 +866,17 @@ static void test_put_filter(void) ok(!ref, "Got outstanding refcount %ld.\n", ref); } +struct test_sample +{ + IMediaSample sample; + LONG refcount; +}; + +static struct test_sample *impl_from_IMediaSample(IMediaSample *iface) +{ + return CONTAINING_RECORD(iface, struct test_sample, sample); +} + static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, void **ppvObject) { @@ -874,12 +885,14 @@ static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, static ULONG WINAPI ms_AddRef(IMediaSample *iface) { - return 2; + struct test_sample *sample = impl_from_IMediaSample(iface); + return InterlockedIncrement(&sample->refcount); } static ULONG WINAPI ms_Release(IMediaSample *iface) { - return 1; + struct test_sample *sample = impl_from_IMediaSample(iface); + return InterlockedDecrement(&sample->refcount); } static HRESULT WINAPI ms_GetPointer(IMediaSample *iface, BYTE **ppBuffer) @@ -989,7 +1002,7 @@ static const IMediaSampleVtbl my_sample_vt = { ms_SetMediaTime }; -static IMediaSample my_sample = { &my_sample_vt }; +static struct test_sample my_sample = { {&my_sample_vt}, 0 }; static BOOL samplecb_called = FALSE; @@ -1012,8 +1025,9 @@ static ULONG WINAPI sgcb_Release(ISampleGrabberCB *iface) static HRESULT WINAPI sgcb_SampleCB(ISampleGrabberCB *iface, double SampleTime, IMediaSample *pSample) { - ok(pSample == &my_sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); + ok(pSample == &my_sample.sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); samplecb_called = TRUE; + IMediaSample_AddRef(pSample); return E_NOTIMPL; } @@ -1043,6 +1057,7 @@ static void test_samplegrabber(void) IEnumPins *pins; HRESULT hr; FILTER_STATE fstate; + ULONG refcount; /* Invalid RIID */ hr = CoCreateInstance(&CLSID_SampleGrabber, NULL, CLSCTX_INPROC_SERVER, &IID_IClassFactory, @@ -1074,10 +1089,13 @@ static void test_samplegrabber(void) hr = IPin_QueryInterface(pin, &IID_IMemInputPin, (void**)&inpin); ok(hr == S_OK, "Got hr %#lx.\n", hr); - hr = IMemInputPin_Receive(inpin, &my_sample); + hr = IMemInputPin_Receive(inpin, &my_sample.sample); ok(hr == S_OK, "Got hr %#lx.\n", hr); ok(samplecb_called == TRUE, "SampleCB should have been called\n"); + refcount = IUnknown_Release(&my_sample.sample); + todo_wine ok(!refcount, "Got unexpected refcount %ld.\n", refcount); + IMemInputPin_Release(inpin); IPin_Release(pin); -- 2.36.1

3 4

Re: [PATCH v3 3/5] dlls/msvcrt: fix and cleanup undecoration of templatized functions and methods
by Marvin July 16, 2022

July 16, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. 1 TestBot errors prevented a full analysis of your patch. If the test caused the operating system (e.g. Windows) to crash or reboot you will probably have to modify it to avoid that. Other issues should be reported to the TestBot administrators. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119173 Your paranoid android. === build (build log) === WineRunBuild.pl:error: An error occurred while waiting for the build to complete: network read timed out (wait2:ListSize:0/4) WineRunBuild.pl:error: BotError: The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died)

1 0

Wine staging 7.13 release
by Alistair Leslie-Hughes July 16, 2022

July 16, 2022

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.13 (543 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Added: * None Updated: * None Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0