- wine-gitlab - winehq.org

[PATCH 0/2] MR1712: windows.devices.enumeration/tests: Make test handlers structure static.
by Paul Gofman (＠gofman) 06 Dec '22

06 Dec '22

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54085 Fixes test randomly crashing on Win10 Testbot machines. I think the test added by me after (test_DeviceAccessInformation) this one is just getting hit by the consequences of test_DeviceInformation. I guess what is happening here is that sometimes Windows accesses the handlers (maybe releases) after test_DeviceInformation() is exited already and the test interface implementation (which implements reference counting but uses structure on stack) accesses the popped stack data. It is the second patch which seems to actually fix the test crash. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1712

2 2

[PATCH 0/3] MR1707: winegstreamer: Implement IMediaObject_GetOutputType for WMV decoder.
by Ziqing Hui (＠zhui) 06 Dec '22

06 Dec '22

In this patch set, GetOutputType() currently fails for NV11 and the following RGB types because MFCalculateImageSize() fails for them. I'll fix MFCalculateImageSize() for them recently (but not in this patch set). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1707

3 9

[PATCH 0/1] MR985: mshtml/tests: Mark tests failing randomly on Windows as flaky.
by Francois Gouget (＠fgouget) 06 Dec '22

06 Dec '22

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/985

4 3

[PATCH 0/1] MR1709: mshtml/tests: Accept rare unknown error in ReportResult.
by Gabriel Ivăncescu (＠insn) 06 Dec '22

06 Dec '22

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/1709

3 2

[PATCH 0/1] MR1711: wldap32/tests: Skip paged search tests when the server can't be reached.
by Hans Leidekker (＠hans) 06 Dec '22

06 Dec '22

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54075 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1711

2 1

[PATCH 0/1] MR1703: opengl32: Use default calling convention for WGL driver entry points.
by Jacek Caban (＠jacek) 06 Dec '22

06 Dec '22

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/1703

4 3

Re: [PATCH v12 0/6] MR42: vkd3d-shader/hlsl: Some fixes.
by Francisco Casas (＠fcasas) 06 Dec '22

06 Dec '22

On Mon Dec 5 13:15:09 2022 +0000, Giovanni Mascellani wrote: > I just noticed that the the PE shader runner fails an assertion when > running this test inside Wine, using `VKD3D_TEST_PLATFORM=windows` and > native `d3dcompiler`: > ``` > Assertion failed: root_signature_desc.NumParameters <= > ARRAY_SIZE(root_params), file ../vkd3d/tests/shader_runner_d3d12.c, line 227 > ``` > @fcasas, could you have a look? That assertion happens when the `root_params` array, declared at the beginning of `d3d12_runner_create_root_signature()` is not big enough to hold all the resources in the shader. The solution is increasing the size of the array. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/42#note_18835

1 0

[PATCH 0/1] MR1700: wldap32: Define LDAP_NEEDS_PROTOTYPES.
by Jacek Caban (＠jacek) 06 Dec '22

06 Dec '22

Fixes -Wstrict-prototypes warnings in clang builds. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1700

3 2

[PATCH 0/2] MR1698: win32u: Fixes for some regressions with 16-bit applications
by Sven Baars (＠sbaars) 06 Dec '22

06 Dec '22

This fixes the regressions mentioned in the following bugs Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53568 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=53646 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1698

4 4

[PATCH 0/1] MR1688: ddraw: Sync draw textures even for hardware device.
by Paul Gofman (＠gofman) 06 Dec '22

06 Dec '22

Fixes a regression introduced by commit d2d9f713df7932aac4b137ec3bf647d5da7faaef. Fixes black screen in Exceed - Gun Bullet Children. The check in d3d_device_sync_surfaces() assumes that separate draw textures may be created and successfully bound for software device only. This turns out to be not always the case. The case which the game hits is that it creates a surface with DDSCAPS_TEXTURE | DDSCAPS_3DDEVICE, DDSCAPS2_TEXTUREMANAGE. Such surface creation is valid and the resulting surface is bindable as render target of a software device (we have a test for that). Such a texture effectively falls into the case when a separate draw texture is created and that looks correct. However this surface, while cannot be used as a render target on hardware device, can still be used as a texture. So for a general case syncing surfaces for software devices only is wrong (it still looks right for syncing render targets). Just always traversing all the bound textures in d3d_device_sync_surfaces() looks like a waste, while accurately tracking when there are bound textures requiring sync is possible while looks like an unnecessary complication. So triggering the sync by the fact a texture requiring a sync was ever bound (which is in fact not so common case) looks like a reasonable compromise to me. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1688

7 7

2025

2024

2023

2022

wine-gitlab