- wine-devel - winehq.org

TestBot News - MR false positives analysis
by Francois Gouget 19 Oct '23

19 Oct '23

I have been reviewing the TestBot and GitLab CI test results for the merged MRs. While doing that I updated the TestBot's known failures list (https://testbot.winehq.org/FailuresList.pl) in order to drive down the false positive rate. Incidentally I also collected the list of test units causing false positives, so I'll start with that. Specifically, here are the bugs to fix to help the GitLab CI: * Bug 53433 - mmdevapi:capture - impacted 18 MRs * Bug 54064 - ntdll:threadpool - impacted 15 MRs * Bug 54078 - ntdll:pipe - impacted 11 MRs * Bug 54140 - mmdevapi:render - impacted 5 MRs * Bug 54005 - ole32:clipboard - impacted 5 MRs * Bug 54037 - user32:msg - impacted 5 MRs * Bug 54074 - ws2_32:sock - impacted 5 MRs I classified the TestBot / GitLab CI results as follows: * False positive Cases where the CI system incorrectly claimed the MR introduces new failures. This is typically the case when the failures that are already present in nightly WineTest results. * Bad merge MRs that break a test and got merged anyway. * Collateral Damage from a bad merge The false positives (aka collateral damage) caused by one of the bad merges above. * Outside interference This identifies false positives that are not random and intrinsic to the test but that result from change outside the Wine infrastructure, for instance certificates that expire, or configuration changes to servers that break the tests that depend on it. Of those the only ones that a CI can really avoid are the first type, aka "False positive". So I calculated the corresponding weekly rate: Adjusted False Positive rate Week | TestBot | GitLab CI 2022-11-14 | 21.9% | 8.3% 2022-11-21 | 8.0% | 21.6% 2022-11-28 | 14.7% | 28.4% 2022-12-05 | 8.5% | 24.5% 2022-12-12 | 0.0% | 20.0% Note that the TestBot's 8% rate for the 11-21 week is not representative because Wine was broken that week (collateral damage) which prevented the tests from running in Wine, and thus from contributing real "false positives". Also the 12-12 week is still incomplete obviously. Even so I think his shows the TestBot is improving. Here's a list of the incidents for the weeks above: * 11-14 An external certificate revocation issue caused crypt32:cert to fail systematically. This impacted 14 merge requests and was fixed in MR1360. * 11-17 MR!1399 got merged despite the TestBot detecting that it prevented 32-bit Wine tests from running to completion. This impacted 39 merge requests. I could have reduced that number if I had been faster to reconfigure the TestBot to stop running the full 32-bit Wine test suite. This was fixed in MR!1524. * 11-17 MR!1398 got merged despite the TestBot detecting that it broke ntoskrnl.exe:ntoskrnl on Windows 7. This was fixed in MR!1803. * 11-22 MR!1495 got merged despite the TestBot detecting that it broke vbscript:run on Windows *. I don't have a record of the impacted MRs or of when it was fixed. * 11-23 The b00a831d direct commit broke kernel32:process in Wine. This got fixed since. * 12-07 MR!1732 got merged despite the TestBot detecting that it broke taskschd:scheduler on Windows *. I immediately added a known failure entry and no MR got impacted. This was fixed in MR!1736. If not filtering out the failures caused by these incidents, the false positive rate is: Raw False Positive rate Week | TestBot | GitLab CI 2022-11-14 | 52.1% | 27.1% 2022-11-21 | 50.0% | 29.5% 2022-11-28 | 20.0% | 33.7% 2022-12-05 | 19.1% | 57.4% 2022-12-12 | 0.0% | 20.0% I think that also shows that the TestBot is improving. I have attached the raw data I collected and shell snippets to extract various statistics (failures-mr.txt) as well as a spreadsheet import (failures.xls). -- Francois Gouget <fgouget(a)codeweavers.com>

1 5

Wine staging 8.18 release
by Alistair Leslie-Hughes 14 Oct '23

14 Oct '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.18 (496 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * dmime: Implement IDirectMusicSegment8 Download. * dmime: Play a sound in IDirectMusicPerformance8 PlaySegmentEx * d3dx9: D3DXLoadMeshHierarchyFromXInMemory support empty mesh. * include: Always define hton/ntoh macros. Added: * [39876] d3dx9: D3DXLoadMeshHierarchyFromXInMemory return a dummy ID3DXAnimationController. Updated: * vkd3d-latest to latest. * msxml3-FreeThreadedXMLHTTP60 * odbc-remove-unixodbc 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Wine staging 8.17 release
by Alistair Leslie-Hughes 30 Sep '23

30 Sep '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.17 (494 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * systeminfo: add basic functionality. Added: * [39876] d3dx9: D3DXLoadMeshHierarchyFromXInMemory return a dummy ID3DXAnimationController. Updated: * vkd3d-latest to latest. * user32-recursive-activation 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

TestBot News
by Francois Gouget 27 Sep '23

27 Sep '23

* GitLab bridge The bridge to add the TestBot failures as comments on GitLab is broken. It seems like it happened near the end of August. So be sure to look at the wine-gitlab mailing list to not miss issues in your merge requests. * VM changes debian11, debian11b and debiant now have UsePPosition in their fvwm configuration. See the full fvwm configuration below: https://wiki.winehq.org/Wine_TestBot_VMs#Unix_configuration These VMs also got an update to the latest packages. Also there is an ongoing experiment to figure out the best window manager for the tests. And who knows, maybe we'll event keep more than one? Anyway we currently have: - debian11 fvwm2 - debian11b fvwm2 - debian12 openbox - debiant fvwm3 * Test result changes Thanks to Esme's work, user32:msg now has a lot fewer failures, most notably on Windows 7 and 11: https://test.winehq.org/data/patterns.html#user32:msg d3d9:device also got quite a bit better thanks to Stefan's work: https://test.winehq.org/data/patterns And Alexandre fixed a bunch of stack, pointer and parameter size failures in various tests: https://test.winehq.org/data/patterns.html#kernel32:loader https://test.winehq.org/data/patterns.html#kernel32:thread https://test.winehq.org/data/patterns.html#ntdll:om https://test.winehq.org/data/patterns.html#oleaut32:usrmarshal https://test.winehq.org/data/patterns.html#winmm:capture ... Unfortunately there are other tests that started failing: 09-18 - 55650 dbghelp:dbghelp fails on macOS 09-14 - 55648 ntdll:wow64 - test_peb_teb() crashes on macOS - 55658 psapi:psapi_main - test_EnumProcessModules*() fails on macOS - 55655 user32:dialog - test_IsDialogMessageA_proc() fails in the Hindi locale on Wine - 55656 user32:dialog - test_IsDialogMessage() fails in the hi-u8 and mx-MX locales on Windows (bug 55656) 09-12 - 55649 quartz:vmr9 - test_changed3ddevice() fails on the TestBot's w11pro64-amd & -nv VMs 09-11 - 55637 dmime:dmime - test_performance_pmsg() sometimes fails due to bad timing on Windows and Wine - 55656 ntdll:exception - test_thread_context() fails on macOS 09-08 - 55583 d3d8:device - test_wndproc() often is missing a WM_WINDOWPOSCHANGING in Wine 08-30 - 55569 mshtml:dom - The 32-bit test_attr_collection_attr() crashes on Windows 10 2004+ 08-23 - 55588 mf:mf - test_scheme_resolvers() crashes on Windows 7 -- Francois Gouget <fgouget(a)codeweavers.com>

1 0

Wine staging 8.16 release
by Alistair Leslie-Hughes 16 Sep '23

16 Sep '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.16 (495 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * dnsapi/tests: Add some tests for DNS_TYPE_SRV messages. * dnsapi: Accept name records of exact size at the end of the packet. * dnsapi: Set correct wDataLength for DNS_TYPE_SRV records. Added: * [10729] ddraw: Implement Pick() and GetPickRecords(). Updated: * vkd3d-latest to latest. 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Recent ntdll/unix/signal_x86_64.c changes
by Gerald Pfeifer 15 Sep '23

15 Sep '23

commit ea640f6cece7660ffc853b7d574fbe52af34901a Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Sep 11 11:25:29 2023 +0200 ntdll: Ignore attempts to change segment registers on x86-64. moved the following code +#ifdef DS_sig + DS_sig(sigcontext) = ds64_sel; +#else + __asm__ volatile( "movw %0,%%ds" :: "r" (ds64_sel) ); +#endif +#ifdef ES_sig + ES_sig(sigcontext) = ds64_sel; +#else + __asm__ volatile( "movw %0,%%es" :: "r" (ds64_sel) ); +#endif into static inline void leave_handler( const ucontext_t *sigcontext ) Alas this has "const ucontext_t *sigcontext", so platforms like FreeBSD that define DS_sig will try to do DS_sig(sigcontext) = ds64_sel; which results in GCC rightfully diagnosing: dlls/ntdll/unix/signal_x86_64.c: In function ‘leave_handler’: dlls/ntdll/unix/signal_x86_64.c:822:24: error: assignment of member ‘mc_ds’ in read-only object 822 | DS_sig(sigcontext) = ds64_sel; | ^ I submitted https://gitlab.winehq.org/wine/wine/-/merge_requests/3845 which restores the build on FreeBSD and presumably NetBSD, but wonder: Could FreeBSD/NetBSD align with Linux and macOS which d not define DS_sig (and ES_sig) and thus use into different code paths in leave_handler? Gerald

2 1

Wine staging 8.15 release
by Alistair Leslie-Hughes 02 Sep '23

02 Sep '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.15 (496 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None. Added: * None Updated: * vkd3d-latest to latest. * user32-rawinput-mouse * mshtml-TranslateAccelerator 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Upcoming vkd3d 1.9 release
by Henri Verbeet 23 Aug '23

23 Aug '23

Hi all, The targetted release date for vkd3d 1.9 is four weeks from now, on September 20. That means the development branch will become increasingly frozen as we're nearing the release date. If you're an upstream vkd3d developer, please do the following: - Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify all the vkd3d tests pass on your hardware. - Review and improve the documentation. - Apply your best judgment about which patches are appropriate for the current stage of the release process. Note that it's entirely appropriate to queue up more complicated changes for application post 1.9 and ask for review on them, but please either mark those as draft or put some kind of note in the MR description. If you're a downstream user of vkd3d, please test your applications for regressions, and file bug reports if you find any. If you're the maintainer of a Wine module that (indirectly) depends on vkd3d, like e.g. d2d1, d3dx9, d3dcompiler, or any of the core Direct3D modules, that includes making sure the unit tests still pass with the new version. We try our best to avoid regressions, but ultimately we depend on our downstream users to catch anything we may have missed before the final release. The planned release date for the release following vkd3d 1.9 is currently sometime in December. Regards, Henri

1 0

Upcoming vkd3d 1.9 release
by Henri Verbeet 23 Aug '23

23 Aug '23

Hi all, The targetted release date for vkd3d 1.9 is four weeks from now, on September 20. That means the development branch will become increasingly frozen as we're nearing the release date. If you're an upstream vkd3d developer, please do the following: - Keep an eye on Bugzilla for any reported regressions. - Review any API changes since the previous release. - Verify all the vkd3d tests pass on your hardware. - Review and improve the documentation. - Apply your best judgment about which patches are appropriate for the current stage of the release process. Note that it's entirely appropriate to queue up more complicated changes for application post 1.9 and ask for review on them, but please either mark those as draft or put some kind of note in the MR description. If you're a downstream user of vkd3d, please test your applications for regressions, and file bug reports if you find any. If you're the maintainer of a Wine module that (indirectly) depends on vkd3d, like e.g. d2d1, d3dx9, d3dcompiler, or any of the core Direct3D modules, that includes making sure the unit tests still pass with the new version. We try our best to avoid regressions, but ultimately we depend on our downstream users to catch anything we may have missed before the final release. The planned release date for the release following vkd3d 1.9 is currently sometime in December. Regards, Henri

1 0

Wine staging 8.14 release
by Alistair Leslie-Hughes 21 Aug '23

21 Aug '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.14 (496 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * dmime: Store WAVE data when Loading. Added: * None Updated: * vkd3d-latest to latest. * xactengine3_7-PrepareWave * fltmgr.sys-FltBuildDefaultSecurityDescriptor * winex11-CandidateWindowPos * user32-rawinput-mouse * widl-SLTG_Typelib_Support * ntdll-Syscall_Emulation 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

IRC-matrix bridge status?
by Jeff Smith 13 Aug '23

13 Aug '23

I became aware that I had missed a message on IRC. The sender was on matrix and I was on IRC. I haven't seen them there (#winehackers) in days. I suggested the IRC-matrix bridge was down, and was pointed to the following links, which seem likely to be relevant. (I don't know what type of bridge has been in use for this channel since the move to libera.) https://libera.chat/news/matrix-irc-bridge-updates https://libera.chat/news/matrix-bridge-disabled-retrospective Who knows what other messages may have disappeared in the ether. -- Jeff Smith

1 0

Vacations
by Alexandre Julliard 25 Jul '23

25 Jul '23

Folks, I'll be out on vacation for about 3 weeks starting today. I'm still planning to review and commit merge requests, but the timing will be slower and more random than usual. I'll also skip the August 4 release, so Wine 8.14 will be out on August 18. Have fun while I'm gone ;-) -- Alexandre Julliard julliard(a)winehq.org

1 0

Wine-CE 8.13 released
by fanwj＠mail.ustc.edu.cn 23 Jul '23

23 Jul '23

Wine-CE 8.13 released! Address: https://gitlab.com/wine-ce/wine-ce/-/releases/v8.13 Wine-CE (Chimera Edition, Cross-architecture Emulator) is a compatibility layer capable of running Windows applications on Cross-architecture paltform of Linux. It is base on Wine Project and Qemu Project ChangeLog: 1. Add GLES backed for wined3d. 2. Add EGL supported for winex11.drv 3. New 32-bit allocation for wow64

1 0

Wine staging 8.13 release
by Alistair Leslie-Hughes 23 Jul '23

23 Jul '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.13 (504 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None Added: * [55135] d3d12core: Add D3D12GetInterface stub. Updated: * vkd3d-latest to latest. * windows.networking.connectivity-new-dll 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

wine-8.0.2-rc1 Available
by Michael Stefaniuc 09 Jul '23

09 Jul '23

Hello, I have pushed wine-8.0.2-rc1 (98639f1859ba614e7ca8cfbc41fa7e9fcc603240) with tag to https://gitlab.winehq.org/mstefani/wine/-/tree/stable https://people.redhat.com/mstefani/wine/stable/ And created the merge request https://gitlab.winehq.org/wine/wine/-/merge_requests/3168 The merge request is no longer a draft as that confused some reviewers as meaning "not finished". But I still intend to give people at least 1 week time to comment on it. I will just hold off my own approval for the MR. What's new in this release: - Various bug fixes ---------------------------------------------------------------- Bugs fixed in 8.0.2 (total 27): - #11436 Pepakura viewer: err:wgl:X11DRV_wglShareLists Could not share display lists, context already created ! - #35254 Freemake Video Converter 4.1 installer complains about running Freemake processes (builtin 'findstr' stub app always returns "match") - #49964 32-bit dxdiag doesn't support '/64bit' command line switch (launch 64-bit dxdiag) - #51178 The Bat! v9.3.4.12: Missing content in TTreeViews on Windows versions higher than 8 - #52322 wineserver memory leak during HTTPs download (Genshin Impact Launcher, Qt5) - #53073 mfplat: unimplemented function while loading Devil May Cry 1 - #53704 Bible Black ~La Noche de Walpurgis~ won't start - #53781 Multiple apps crash on unimplemented function CFGMGR32.dll.CM_MapCrToWin32Err (Matrix Awakens MegaCity Unreal Engine 5.1 demo, Hogwarts Legacy) - #53794 Sins of the Solar Empire Rebellion (Gog 1.975.1) crashes on unimplemented function concrt140.dll.?_CheckTaskCollection@_UnrealizedChore@details@Concurrency@@IAEXXZ - #53826 Attempting to install / update battle.net fails with Qt error - #53983 Chromium broken sandbox, needs NtQueryInformationProcess with ProcessHandleTable - #54110 CubicSDR crashes on unimplemented function msvcp140.dll.?_Rethrow_future_exception@std@@YAXVexception_ptr@1@@Z - #54618 VARA FM crashes on unimplemented function pdh.dll.PdhVbGetDoubleCounterValue - #54640 Treecomp listviews and possibly other widgets are not drawn - #54675 Chocolatey OpenSSH installer fails - #54687 LibreVR Revive fails to run (CertGetNameStringW with dwType=CERT_NAME_ATTR_TYPE and pvTypePara missing additional fallbacks) - #54702 ldp.exe crashes when attempting to add, delete, modify, or compare an entry without a name - #54724 LDAP bind over SSL to a server and port that do not support SSL hangs forever - #54728 Pro Evolution Soccer 2008 demo takes +- 9 minutes to complete extracting 'Pro Evolution Soccer 2008 DEMO.msi' (disabling 'Light' theme works around) - #54733 Notepad3 crashes on unimplemented function SHLWAPI.dll.StrFormatByteSizeEx - #54799 wininet:internet - test_InternetGetConnectedStateExA() fails in the Japanese and Chinese locales in Wine - #54808 Access violation in ntdll when running Adolix Split and Merge PDF with .NET Framework installed - #54819 DnsQuery_A() mishandles CNAME DNS records - #54882 Conemu fails to start (cannot attach to process) - #54939 Dotted files are shown - but "don't show dotted" files is active - #54960 winhttp:winhttp - test_websocket() fails on Windows and Wine - #55008 wininet:http - test_secure_connection() fails on Windows and Wine ---------------------------------------------------------------- Changes since 8.0.1: Alex Henrie (12): comctl32/treeview: Ignore the lParam to WM_PRINTCLIENT and add tests. wldap32: Handle null DN or null message in ldap_add* and add tests. wldap32: Handle null DN or null message in ldap_modify* and add tests. wldap32: Handle null DN or null attr in ldap_compare* and add tests. wldap32/tests: Use the same context in test_ldap_(add|modify_compare). wldap32: Handle null DN or null message in ldap_delete* and add tests. winex11: Simplify confusing condition and error messages in wglShareLists. opengl32/tests: Make the wglShareLists tests comprehensive. winex11: Allow replacing either context in wglShareLists. kernel32/tests: Check that lpSectionBase != NULL before dereferencing. ntdll: Increment offset by len in build_clr_surrogate_section. winemenubuilder: Skip desktop integration for certain associations. Alexandre Julliard (3): kernelbase: Move to a higher address on 64-bit. ntdll: Fix typo in the check for hidden files. wininet/tests: Update expected WineHQ certificate. Alistair Leslie-Hughes (1): activeds: Free memory on error paths (coverity). Bernhard Übelacker (1): ntoskrnl: Do not leak memory by setting input buffer to NULL. Biswapriyo Nath (2): include: Fix c++ compiler error with msxml2.idl. include: Fix IDirectXVideoDecoderService declaration in dxva2api.idl. Brendan Shanks (7): include/msvcrt: Add __WINE_(DEALLOC|MALLOC) attributes to _strdup and _wcsdup. msvcrt: Fix crash when rethrowing after a non-C++ exception on x86_64. winemac: Fix memory leak in UpdateDisplayDevices. winemac: Refactor constrain_window_frame() to use separate origin and size arguments. winemac: Set the Cocoa window contentMaxSize to the size limits from constrain_window_frame(). winemac: Don't constrain surface dimensions to the onscreen part of a window. winemac: Initialize retina_on to avoid incorrect cached display data in high-res/retina mode. David Kahurani (1): shlwapi: Implement StrFormatByteSizeEx. Eric Pouech (3): winedbg: Don't crash when no search path has been set. evr: Fix incorrect integral computation. winedump: Fix out of bounds access (spotted by GCC13). François Gouget (2): wininet/tests: Dump the state string if it is not as expected. wininet: InternetGetConnectedStateExA() must always null-terminate the state string. Gabriel Ivăncescu (8): mshtml: Fix nsevent leak in create_document_event. mshtml: Fix nsscript leak in bind_event_scripts. mshtml: Fix nsuri leak if create_channelbsc failed. mshtml: Fix nsparser leak if script_elem_from_nsscript failed. mshtml: Fix factory leak in init_nsio. mshtml: Fix nsIFile dir leak in init_xpcom. mshtml: Fix URI leak in NewURI on failure. mshtml: Store minimum compat mode required for events in the ctor table. Hans Leidekker (3): ldap: Return an error when the server doesn't respond to the SSL handshake. ws2_32: Skip non-address records in dns_only_query(). winhttp/tests: Fix a test failure. Jactry Zeng (1): wordpad: Resize buttons of toolbar to make them align with height of the font list combox. Jinoh Kang (2): kernel32/tests: Test for manifest file open share mode in CreateActCtxW. ntdll: Open application manifest files with FILE_SHARE_DELETE. Louis Lenders (1): wine.inf: Add EditionID to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion. Michael Stefaniuc (2): dmsynth: Don't crash when Open() gets a DMUS_PORTPARAMS7. threadpoolwinrt: Forward a Release() to a Release() method. Mohamad Al-Jaf (4): pdh: Implement PdhVbGetDoubleCounterValue(). pdh/tests: Add PdhVbGetDoubleCounterValue() tests. cfgmgr32: Implement CM_MapCrToWin32Err. cfgmgr32/tests: Add CM_MapCrToWin32Err tests. Nikolay Sivov (1): mfplat: Implement MFCreatePathFromURL(). Olivier F. R. Dierick (1): dxdiag: Ignore option /64bit on the commandline. Paul Gofman (2): ntdll: Add stub for NtQueryInformationProcess( ProcessHandleTable ). ntdll: Avoid integer overflow in block_get_subheap(). Piotr Caban (1): localspl: Don't pass original document name to cupsStartDocument. Sven Baars (1): wine.inf: Put the Clients key in the right place. Tim Clem (1): winemac.drv: Force a window in front of its peers if its level is decreased. Torge Matthies (4): ntdll/tests: Add test for file attributes of files with names beginning with a dot. ntdll: Handle hidden file names inside get_file_info instead of after it. ntdll: Only infer hidden attribute from file name if xattr is not present. ntdll: Set xattr in NtCreateFile if inferred and requested attributes don't match. Tyson Whitehead (2): crypt32: Add some CertGetNameStringW fallback cases. crypt32/tests: Test for CertGetNameStringW fallback cases. Vijay Kiran Kamuju (2): msvcr100: Add _UnrealizedChore::_CheckTaskCollection stub. msvcp110: Add std::_Rethrow_future_exception implementation. Zebediah Figura (1): ntdll: Make fd_set_file_info() static. Zhiyi Zhang (4): light.msstyles: Use border fill background for progress parts. light.msstyles: Don't draw a border for progress fill parts. findstr: Add basic functionality. wined3d: Add GPU information for AMD Raphael. Ziqing Hui (1): mfreadwrite: Fix an address of operator typo. bye michael

1 0

Wine staging 8.12 release
by Alistair Leslie-Hughes 09 Jul '23

09 Jul '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.12 (504 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * wined3d: rename shader_extract_from_dxbc to wined3d_shader_extract_from_dxbc Added: * [55205] dinput: Improve keyboard devices scancode support. Updated: * vkd3d-latest to lateset. 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Code guidelines
by Alex Henrie 08 Jul '23

08 Jul '23

Hello everyone, I just finished rewriting the Wine coding guidelines based on feedback at <https://gitlab.winehq.org/wine/wine/-/merge_requests/3059>. Please look it over and let me know if there's anything that I missed or misstated: https://wiki.winehq.org/Submitting_Patches#Code_guidelines https://wiki.winehq.org/Wine_Developer's_Guide/Coding_Practice Thanks to Zeb and Alexandre in particular for the clarifications about style and compatibility. -Alex

1 0

GitLab notification emails stopped
by Alex Henrie 05 Jul '23

05 Jul '23

Hi, There was activity today on multiple merge requests that I was subscribed to, but I didn't get any notification emails. Is it just me, or have they stopped for everyone? -Alex

3 3

GCC 12 use-after-free false positives
by Fabian Maurer 26 Jun '23

26 Jun '23

When using GCC 12, there's two bogus warnings in Wine's code: ../wine-git/dlls/winex11.drv/clipboard.c: In function ‘X11DRV_CLIPBOARD_GetProperty’: ../wine-git/dlls/winex11.drv/clipboard.c:1871:13: error: pointer ‘val’ may be used after ‘realloc’ [-Werror=use-after-free] 1871 | free( val ); | ^~~~~~~~~~~ ../wine-git/dlls/winex11.drv/clipboard.c:1866:17: note: call to ‘realloc’ here 1866 | *data = realloc( val, pos * sizeof(int) + count + 1 ); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There is no real issue here, it's just a false positive. This could be worked around using a temporary void* variable to hold the result from realloc. Is this worth it or would you wait for gcc to fix their warning? Regards, Fabian Maurer

2 1

Wine staging 8.11 release
by Alistair Leslie-Hughes 25 Jun '23

25 Jun '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.11 (502 patches are applied to wine vanilla) vk3d3 has been updated to the 1.8 release. Upstreamed (Either directly from staging or fixed with a similar patch). * None Added: * [22904] Register URL protocol handlers under linux. * PR 3124 - Improve performance of Registry writes. Updated: * vkd3d-latest (1.8) * gdiplus-Performance-Improvements 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Reduced role for me, Wine project organizational structure
by Jeremy White 21 Jun '23

21 Jun '23

Hey folks, As you may have seen, I recently stepped back from my role at CodeWeavers. [1] I'm still around, just in a greatly reduced fashion. I am still deeply invested in the success of Wine and plan to remain on the committee. Also, this is a good excuse to remind folks of the basic organizational structure of the Wine Project, which is described here: https://wiki.winehq.org/Project_Organization Effectively, this is a heads up that I will be a little less engaged. That may leave a bit of a void; as always, constructive help is always welcome. Cheers, Jeremy [1] https://www.codeweavers.com/blog/jwhite/2023/5/19/a-new-chapter-for-codewea…

1 0

Lots of failures in the new WoW 32-bit tests
by Francois Gouget 18 Jun '23

18 Jun '23

So as far as I understand all that's needed to build Wine with the new Windows-on-Windows support is to do: ./configure --enable-archs=i386,x86_64 make But then when I run WineTest I get 60+ failures instead of the usual ~16 on my machine. https://test.winehq.org/queue/err5z_5H/report https://test.winehq.org/queue/errloGNj/report That does not entirely surprise me since this mode has never been tested (neither GitLab nor the TestBot support it). But did I miss something? For instance one failure I get is with devenum:devenum: devenum:devenum start dlls/devenum/tests/devenum.c devenum.c:691: Test failed: Got hr 0x80004005. Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00405a75). The reason for the crash is that wg_transform_create() in main.c returns NULL: if (WINE_UNIX_CALL(unix_wg_transform_create, &params)) return NULL; // <---- we return NULL here without actually calling the implementation in wg_transform.c as far as I can see. Here's the list of test units that fail in one of the runs. Lots of Direct3D (but not all) and multimedia (GStreamer?) tests. Maybe there are some quick gains to be had? (then there's msvcrt:file which gets -2 as a file descriptor) advapi32:security amstream:amstream comctl32:subclass d2d1:d2d1 d3d10core:d3d10core d3d11:d3d11 d3d8:visual d3d9:visual d3dcompiler_43:hlsl_d3d11 d3dcompiler_43:hlsl_d3d9 d3dcompiler_46:hlsl_d3d11 d3dcompiler_46:hlsl_d3d9 d3dcompiler_47:hlsl_d3d11 d3dcompiler_47:hlsl_d3d9 d3dx10_34:d3dx10 d3dx10_35:d3dx10 d3dx10_36:d3dx10 d3dx10_37:d3dx10 d3dx10_38:d3dx10 d3dx10_39:d3dx10 d3dx10_40:d3dx10 d3dx10_41:d3dx10 d3dx10_42:d3dx10 d3dx10_43:d3dx10 d3dx9_36:core d3dx9_36:math d3dx9_36:texture d3dx9_36:volume dbghelp:dbghelp ddraw:d3d ddraw:visual devenum:devenum explorer.exe:explorer gdi32:font iphlpapi:iphlpapi kernel32:debugger kernel32:thread kernel32:virtual mfmediaengine:mfmediaengine mfplay:mfplay mf:mf mf:transform msvcrt:file msvfw32:mciwnd ntdll:info ntdll:virtual ntdll:wow64 opengl32:opengl qasf:asfreader qedit:mediadet quartz:filtergraph quartz:vmr7 quartz:vmr9 riched20:editor user32:class user32:clipboard user32:msg user32:win win32u:win32u wininet:internet winmm:mci wmp:media wmvcore:wmvcore -- Francois Gouget <fgouget(a)codeweavers.com>

2 1

staging: Drop winemenubuilder-Desktop_Icon_Path patch
by Alex Henrie 12 Jun '23

12 Jun '23

Dear Wine Staging maintainers, I would like to drop the Wine Staging patch that changes `wine foo.exe` to `/usr/bin/wine foo.exe` in the .desktop files that winemenubuilder creates.[1] I'm guessing that the wine-devel mailing list is the best forum is for discussing it because the patch has no associated Bugzilla report and merge requests are disabled in the wine-staging repository. This patch isn't very useful in practice because most (if not all) Linux distributions have mutually exclusive packages for Wine and Wine Staging. From the package maintainer's perspective, not supporting the installation of multiple versions of Wine simultaneously makes a lot of sense because only one wineserver can run at a time. Moreover, we don't want to encourage the practice of installing multiple versions of Wine in order to get everything working. Instead, patches should be improved and merged into upstream Wine. Once the bugs are fixed upstream, the user should be free to switch from Wine Staging to mainline Wine without having to edit all of their .desktop files. Also... The patch conflicts with the winemenubuilder protocol associations patch that I'd like to get into Wine Staging,[2] so dropping it means less work to get the other patch in ;-) -Alex [1] https://gitlab.winehq.org/wine/wine-staging/-/blob/adda594159dcafc5dc8db820… [2] https://gitlab.winehq.org/wine/wine/-/merge_requests/2740

1 0

Wine staging 8.10 release
by Alistair Leslie-Hughes 10 Jun '23

10 Jun '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.10 (500 patches are applied to wine vanilla) In the spirit of testing, Wine Staging is now going to carry the latest vk3d3. Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Support ISOLATIONAWARE_MANIFEST_RESOURCE_ID range. * ntdll: Support MEM_COALESCE_PLACEHOLDERS in NtFreeVirtualMemory(). * ntdll: Factor out unmap_view_of_section() function. * ntdll: Support MEM_PRESERVE_PLACEHOLDER in NtUnmapViewOfSectionEx(). Added: * [54034] d3dx9: Improve sprite rendering state handling. * [20732] oleaut32: OleLoadPictureEx - First look for specific icon size if specified. * [54998] dnsapi: DnsQuery(DNS_TYPE_SRV) fails to parse some of the server answers Updated: * vkd3d-latest * winex11-_NET_ACTIVE_WINDOW * msxml3-FreeThreadedXMLHTTP60 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: GCC 12 use-after-free false positives
by Fabian Maurer 10 Jun '23

10 Jun '23

Thanks for your reply, I agree, but seeing how old the issue is, I don't know how fast it will be fixed. I noticed it's not really fixable when compiling with -O2, it behaves differently from -O0. At least I didn't find a reliable way (except for ignoring realloc failure) There is already a bunch of gcc tickets regarding Wuse-after-free issues, see meta bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104075 I think the closest to our case is https://gcc.gnu.org/bugzilla/show_bug.cgi? id=106578 Regards, Fabian Maurer On Samstag, 10. Juni 2023 10:17:39 CEST you wrote: > > Is this worth it or would you wait for gcc to fix their warning? > > I asked my self the very same question... > > given the very low number of warnings from GCC12 (compared to what we > got with GCC11) and their false positive nature, I'd rather pick the > wait and see road > > perhaps opening a GCC ticket could be useful (so we'd know if there's a > chance for a fix or if we'll have to fix it on our side) > > (reminder: if nothing is done, Alexandre will fix it when he upgrades > his compiler as he compiles with -Werror) > > A+

1 0

Wine staging 8.9 release
by Alistair Leslie-Hughes 28 May '23

28 May '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.9 (499 patches are applied to wine vanilla) In the spirit of testing, Wine Staging is now going to carry the latest vk3d3. Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Handle NULL process handle in MapViewOfFile3(). * ntdll: Pass allocation type to map_view(). * ntdll: Support MEM_RESERVE_PLACEHOLDER in NtAllocateVirtualMemoryEx(). * ntdll: Support MEM_REPLACE_PLACEHOLDER in map_view(). * ntdll: Support MEM_REPLACE_PLACEHOLDER in NtAllocateVirtualMemoryEx(). * ntdll: Support MEM_PRESERVE_PLACEHOLDER in NtFreeVirtualMemory(). * ntdll/tests: Add more tests for placeholders. Added: * vkd3d-latest Updated: * ntdll-Placeholders * ntdll-ForceBottomUpAlloc 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: Just testing some mailing list settings
by Jeremy Newman 24 May '23

24 May '23

More testing.. On 5/24/2023 8:38 AM, Jeremy Newman via wine-devel wrote: > >

1 1

Just testing some mailing list settings
by Jeremy Newman 24 May '23

24 May '23

Just ignore this message. I want to see some headers related to DKIM and DMARC. -N

1 0

Upcoming vkd3d 1.8 release
by Henri Verbeet 24 May '23

24 May '23

Hi all, We're planning to release vkd3d 1.8 on June 21, four weeks from now. As we're nearing the release date, it will become increasingly harder to make major code changes. Now is a good time to: - Test applications for any regressions. - Review any API changes since the previous release. - Verify the tests pass on your hardware. - Review and improve the documentation. The planned release date for the release following vkd3d 1.8 is currently late September. Regards, Henri

1 0

Wine-CE 8.8 released, support wow64 mode and x86_64, AArch64, RISCV64 platform
by fanwj＠mail.ustc.edu.cn 21 May '23

21 May '23

Wine-CE (Chimera Edition, Cross-architecture Emulator) is a compatibility layer capable of running Windows applications on Cross-architecture paltform of Linux. It is base on Wine Project and Qemu Project Wine-CE 8.8 released, Support Native Mode and Emulate Mode, It Can be running at x86_64, AArch64, RISCV64 What's Native Mode For example, If guest is i386 or x86_64, host is x86_64, It will be running without binary-translator What's Emulate Mode For example, If guest is i386 or x86_64, host is riscv64 or aarch64, It will be running with binary-translator Project Address: https://gitlab.com/wine-ce/wine-ce

1 0

Easiest way to build Wine on Debian, Ubuntu, Pop!_OS, Elementary OS and openSUSE
by Francois Gouget 16 May '23

16 May '23

It can be a pain to install all the needed development packages to build BOTH the 32-bit and 64-bit versions of Wine for the old-style Windows-on-Windows mode. So here's what is hopefully the simplest way to do so on distributions based on Debian and openSUSE [1]. wget https://gitlab.winehq.org/fgouget/wt-daily/-/raw/master/wt-install-dev sudo sh ./wt-install-dev Then build Wine normally, no containers or VMs needed. So assuming you have the source in wine, just run: mkdir wow32 wow64 cd wow64 && ../wine/configure --enable-win64 && make cd ../wow32 && ../wine/configure --with-wine64=../wow64 && make Of course you're also all set for builds using the new WoW approach: cd wine && ./configure --enable-archs=i386,x86_64 && make [1] More specifically this has been tested on: Debian 11 (bullseye), 12 (bookworm) Elementary OS 7 Horus (stable and unstable) openSUSE Leap 15.4, Tumbleweed Pop!_OS 22.04 Ubuntu 22.04.2 LTS, 23.04 Patches to extend support to other distributions are welcome. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ In theory, theory and practice are the same, but in practice they're different.

1 0

Wine staging 8.8 release
by Alistair Leslie-Hughes 15 May '23

15 May '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.8 (494 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll/tests: Add test for file attributes of files with names beginning with a dot. * ntdll: Do not open-code hidden file handling in get_dir_data_entry. * ntdll: Handle hidden file names inside get_file_info instead of after it. * ntdll: Only infer hidden attribute from file name if xattr is not present. * ntdll: Set xattr in NtCreateFile if inferred and requested attributes don't match. * ntdll/tests: Increase margins in timer merging tests. * findstr: add basic functionality (also support literal search option e.g. c:/"foo bar") * tasklist.exe: add minimal functionality * winemenubuilder: Blacklist desktop integration for certain associations * ntdll/tests: Add tests for freeing a part of view. * kernelbase: Validate nonzero size for MEM_RELEASE in VirtualFreeEx(). * ntdll: Fix size validation in NtFreeVirtualMemory(). * ntdll: Fully support unaligned views in free ranges management. * ntdll: Factor out some view manipulation functions. * ntdll: Support partial view release in NtFreeVirtualMemory(). * ntdll: Add logging for free ranges. 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Wine staging 8.7 release
by Alistair Leslie-Hughes 30 Apr '23

30 Apr '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.7 (530 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * none Added: * none Updated: * wined3d-WINED3DFMT_B8G8R8X8_UNORM 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Some questions about handling filenames in wineserver
by Richard W.M. Jones 25 Apr '23

25 Apr '23

I'm trying to bring my old AF_UNIX patch up to date: https://www.winehq.org/pipermail/wine-devel/2021-May/187049.html It's not going too well as the code has changed quite a lot. One particular problem I'm having is in wineserver. We need to convert the Windows socket path encoded as a UTF-8 string (eg. Z:\tmp\sock) into a Unix filename. In the old code I used: + num = MultiByteToWideChar(CP_UTF8, 0, wun->sun_path, -1, NULL, 0); + win_path = HeapAlloc(GetProcessHeap(), 0, num * sizeof(WCHAR)); + if (win_path == NULL) + return 0; + MultiByteToWideChar(CP_UTF8, 0, wun->sun_path, -1, win_path, num); + unix_path = wine_get_unix_file_name(win_path); + heap_free(win_path); However none of this seems to work inside wineserver (I guess because it's not part of the "Windows world"). I cannot work out the equivalent of this for wineserver, or if there's something else I should be doing, such as converting the path before it is sent to wineserver. Supplemental question: There appears to be duplicate socket handling code in wineserver server/sock.c and dlls/ntdll/unix/socket.c. In my tests only the wineserver code is called, and never the ntdll/unix code. Why is that? (I'm not very familiar with the architecture of wine, which seems a bit confusing, so I'm just guessing how it all works.) Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

3 4

Wine-Staging 8.6 release
by Zebediah Figura 16 Apr '23

16 Apr '23

The Wine-Staging development release 8.6 is now available. Summary since last release: * Rebased to upstream Wine 8.6. 532 patches are applied to upstream Wine. Patches removed from Wine-Staging since the last release: * win32u-GPU_properties * winex11-wglShareLists. This fixed Wine bug 25495 [1], which is not currently fixed by any other mechanism. However, the relevant patch is a hack, and hence not suitable for Wine-Staging either. Patches added: * None. Patches otherwise updated: * None. Binary packages for various distributions will be available from: https://www.winehq.org/download As always, if you find a bug, please report it via https://bugs.winehq.org ἔρρωσθε, Zeb Figura [1] https://bugs.winehq.org/show_bug.cgi?id=25495

1 1

wine-8.0.1-rc1 Available
by Michael Stefaniuc 05 Apr '23

05 Apr '23

Hello, I have pushed wine-8.0.1-rc1 (f7512a4e1236c36d926ff753decf412eb82a6a35) to https://gitlab.winehq.org/mstefani/wine/-/tree/stable https://people.redhat.com/mstefani/wine/stable/ And created the draft merge request https://gitlab.winehq.org/wine/wine/-/merge_requests/2585 After the 7.0.x Stable releases didn't go so well I'm trying for 8.0.x a time based approach: - Include stuff from 4 devel releases, about 2 months worth. - Last included devel release should be out for 1-2 other devel (2 - 4 weeks). - Merge request in draft state for 1-2 weeks. What's new in this release: - Fixes for macOS Ventura 13.3 on Apple Silicon - Tamil and Turkish translation updates - Various bug fixes ---------------------------------------------------------------- Bugs fixed in 8.0,1 (total 36): - #49615 Device read errors logged in dmesg when running wine commands with empty CD/DVD drive, since 5.5 - #51345 Regression: Visual Studio 2005 "package load failure" - #52506 Setup of game "What's the Secret?" fails to create icon - #52878 Free PC Audit 5.1.211.96 fails to show info in 'Brief' tab (needs GetBinaryValue method of the StdRegProv class) - #53274 adsldp:ldap - test_ParseDisplayName() sometimes fails to connect to the server - #53926 New typelib marshaller depends on IID_IDispatch support from target interface - #53981 Chromium broken sandbox due to GetSecurityInfo giving access denied - #54030 Snagit needs Win32_Volume class ( 'select deviceid from win32_volume where driveletter =C:') - #54215 ListView doesn't refresh when changing between List and Details styles. - #54234 vbscript fails to compile when colon follows Else in If...Else - #54289 RtlCopyContext buffer overflow - #54318 Rich Edit inserts newly composed text at wrong position when system IME composition ends while a selection is active - #54337 AviUtl shows Japanese text as garbage after conversion in ExEdit edit box - #54353 crypt32:cert - testVerifyRevocation() gets unexpected success in Wine on second run - #54357 Spurious fixme message when calling ScrollWindow() - #54364 RtlGenRandom fails on systems with more than 128 cores - #54371 loader won't launch from PATH unless named "wine" - #54376 ws2_32:sock - test_reuseaddr() overflows a sockaddr variable by reading an AF_INET6 peer name into it - #54379 since wine 8.0 print doesn't work any more - #54432 Missing ntdll.RtlAddressInSectionTable() implementation causes all GraalVM Native Image exes to crash on load - #54449 nethack crashes - #54456 vbscript memory leak in For Each with SafeArray as group - #54457 vbscript memory leaks in interp_redim_preserve - #54458 vbscript memory leaks in Global_Split - #54489 VarAbs() does not handle BSTR arguments correctly - #54490 vbscript fails to compile when statement follows ElseIf - #54493 vbscript fails to compile concat when used without space and expression begins with H - #54495 Motorola Ready For Assistant does not start, needs ext-ms-win-networking-wlanapi-l1-1-0.dll - #54563 The gif is displaying wrongly, with weird backgrounds of various colors - #54564 Rich Edit crashes when Ctrl+Right is pressed at past the final paragraph - #54570 Saints Row: The Third heavy rain causes heavy fps reductions - #54581 SpeedCommander 20 installer crashes on unimplemented function SHELL32.dll.Shell_GetCachedImageIndexW - #54617 KakaoTalk IM text edit window leaves artifacts when the text overflows and scroll bar appears - #54663 ldp.exe crashes on unimplemented function wldap32.dll.ldap_set_dbg_flags - #54690 ldp.exe crashes when attempting to connect to an invalid host - #54707 adsldp:ldap - test_DirectorySearch() fails on Windows and Linux ---------------------------------------------------------------- Changes since 8.0: Akihiro Sagawa (2): user32/tests: Add DBCS WM_CHAR tests for edit control. user32/edit: Fix WM_CHAR handler for double-byte characters. Alex Henrie (5): shell32: Add support for Program Manager icons with arguments. wldap32: Add ldap_set_dbg_flags stub. wldap32: Handle null LDAPMessage in ldap_count_entries. wldap32: Handle null LDAPMessage in ldap_parse_result. server: Fix buffer overrun in map_view handler. Alexandre Julliard (2): gitlab: Add workaround for more strict git ownership check. ntdll: Prefer the ntdll path over argv[0] on platforms without reliable exe information. Alistair Leslie-Hughes (1): mountmgr.sys: Don't attempt to read from invalid media. Brendan Shanks (7): loader: In macOS preloader, move the top-down allocations area down. loader: In macOS preloader, stop using mincore() to test if a region is empty. server: On macOS, fake debug registers when running under Rosetta. ntdll: Add a WARN when setting debug registers fails under Rosetta. loader: In macOS preloader, fix an environment variable sometimes being lost. taskmgr: Use exit code 1 when terminating processes. taskkill: Use exit code 1 when terminating processes. Carlos Rodriguez (1): wined3d: Add GPU information for another Intel UHD 630 GPU. Dmitry Timoshkov (3): win32u: Give full access rights to the process window station. win32u: Give full access rights to the thread desktop. rpcrt4: Mark the buffer as invalid in NdrProxyFreeBuffer(). Eric Pouech (3): ntdll: Implement RtlAddressInSectionTable. conhost: Only update font when running with a window. winedbg: Use debuggee's bitness for 'examine /a' command. Florian Will (2): gdiplus/tests: Test for GdipPrivateAddFontFile() sharing violation. gdiplus: Use FILE_SHARE_READ in GdipPrivateAddFontFile(). Gabriel Ivăncescu (1): jscript: Fix jsstr leak after changing variant type to BSTR. Gijs Vermeulen (1): shell32: Add Shell_GetCachedImageIndexA/W exports. Giovanni Mascellani (1): wbemprox: Do not call Release() inside wbemprox_cf_CreateInstance(). Hans Leidekker (8): wbemprox: Implement GetBinaryValue() method. adsldp/tests: Avoid test failures when the server is down. wbemprox: Implement Win32_Volume. advapi32: Bump random buffer size. msi: Install and patch global assemblies in InstallFinalize. msi: Perform late initialization of the assembly caches. adsldp/tests: Skip all remaining tests when the server is down. adsldp/tests: Fix test failures. Hugh McMaster (2): regedit: Allow export_key() to return TRUE. regedit: Append '.reg' file extension if necessary. Illia Polishchuk (2): d3d9/tests: Add test for non-indexed instancing drawing. d3d9: Always draw only a single instance for non-indexed draws. Jacek Caban (2): win32u: Silence spurious FIXME in NtUserScrollWindowEx. oleaut32: Remove overflow check for VT_R4 and VT_R8 in VarAbs. Jason Millard (7): vbscript: Fix compile when colon follows Else on new line. vbscript: Fix memory leak in owned safearray iterator. vbscript: Fix memory leak in Split(). vbscript: Fix memory leak in Split(). oleaut32: Fix VarAbs function for BSTR with positive values. vbscript: Fix compile when statement after ElseIf or after separator. vbscript: Fix compile issue with non hex after concat without space. Jinoh Kang (7): ws2_32/test: Fix sockaddr buffer overflow in test_reuseaddr. riched20: Obtain the composition start index after deleting selection. riched20/tests: Test for word movement across paragraph boundary. riched20: Don't set para unless committing cursor move in ME_MoveCursorWords. riched20/tests: Test for ITextDocument::Freeze and ITextDocument::Unfreeze. riched20: Don't assume that TxDraw preserves the device context's brush selection. riched20: Implement ITextDocument::Freeze and ITextDocument::Unfreeze. K.B.Dharun Krishna (1): po: Update Tamil translation. Michael Stefaniuc (2): tools: Get the ANNOUNCE bug list from the stable-notes git notes. gitlab: Do not run the build script on each commit. Nikolay Sivov (1): apisetschema: Add ext-ms-win-networking-wlanapi-l1-1-0. Paul Gofman (5): ntdll: Factor out context_copy_ranges() function. ntdll: Do not use extended context in RtlCopyContext() if extended state is not copied. cryptnet: Cache revocation status in verify_cert_revocation(). cryptnet: Use cert data hash as cache id instead of serial number. cryptnet: Also hash issuer cert for cache id. Piotr Caban (7): msvcrt: Don't crash on NULL argument in getenv. msvcrt: Don't crash on NULL argument in _wgetenv. msvcrt: Improve error handling in getenv_s. msvcrt: Improve error handling in _wgetenv_s. winspool: Fix FILE: output handling in StartDocDlgW. localspl: Ignore an empty output string. gdiplus: Use transparency instead of background color if transparent color flag is set in GIF GCE. Rémi Bernon (2): dwrite: Statically init the system_fallback locale list. services: Use a separate allocation for NotifyParamsArray[0].params. Serkan Önder (1): po: Update Turkish translation. Tingzhong Luo (1): evr: Fix crash when clearing input type for the mixer. Zebediah Figura (1): oleaut32: Manually construct a stub buffer for dispinterfaces. Zhiyi Zhang (3): comctl32/tests: Add WM_STYLECHANGED tests for changing listview view styles. comctl32/listview: Repaint when changing view styles. user32/tests: Test winstation and desktop access rights. bye michael

1 0

Wine CE 8.5 Released, Cross Architecture Windows Emulator, Support Wow64, Base on wine and qemu
by fanwj＠mail.ustc.edu.cn 03 Apr '23

03 Apr '23

Wine CE is a compatibility layer capable of running Windows applications on Cross-architecture paltform of Linux, It base on wine and qemu, and support aarch64 and riscv64 Linux. It can emulate x86(32bit) x64, aarch64 windows app. Project Address: https://gitlab.com/wine-ce/wine-ce Binary Downnload: https://gitlab.com/wine-ce/wine-ce/-/releases/v8.5 Demo Video: RISCV 64: https://www.bilibili.com/video/BV1gv4y1578t AARCH 64: https://www.bilibili.com/video/BV1yc41157iS

1 0

A novel and accurate method to calculate Julliard Rank
by Alex Henrie 02 Apr '23

02 Apr '23

Dear Wine developers, I am excited to announce that I have discovered a novel and accurate method to calculate a Wine developer's Julliard Rank! As we all know, the Julliard Rank is a measure of how much trust Wine's chief maintainer Alexandre Julliard has in a person, and consequently how easily their patches are accepted.[1] What no one seems to have realized until now is that a person's Julliard Rank has a perfect linear correlation with the number of outstanding bisected regressions caused by that person! Alexandre himself is of course at the top with 21 outstanding regressions, followed of course by Zeb with 15. Henri and Jacek are not far behind with 11 each, Rémi and Zhiyi are somewhat lower with 6 each, and predictably I myself don't even make the cut. That means that 49% of the 142 regressions are held by the top 14% of the 44 people on the list.[2] It is intolerable that so many regressions are concentrated in the hands of so few. There is only one rational course of action: We must rise up and act together to take the regressions that belong to those at the top away from them. When their source of power is gone, the vinous elite will be no different from τῶν πολλῶν. There is unfortunately no alternative but to forcefully abolish the classist system that divides developers into regression-haves and regression-have-nots, but after everyone is made into a regression-have-not, a new era of equality, peace, and alcoholism for all will begin. Sincerely, The Central Committee of the Workers' Wine Party (WWP) [1] https://wiki.winehq.org/Developer_FAQ#I_sent_a_merge_request.2C_but_it_got_… [2] https://source.winehq.org/regressions

3 3

Wine configurations naming
by Eric Pouech 01 Apr '23

01 Apr '23

Hi, it seems we should gain some clarification for the naming of the various ways Wine can be configured. This question arises between "old wow64" and "new wow64" esp. some use wow64 without it being very clear to what it applies (some using wine's old wow64 configuration as it was the only one, others refer to window's wow64 architecture, hence "new wow64" in wine lingo) some have used multi-arch wow(64) or multi arch wine for reference to the new wine wow64... it seems to me we'd better use a common denomination for all of this... - only applying to cross compilation (open point if we still need to refer to ELF/dylib exec:s) - different from images naming (for which the <CPU>-<HOST> applies) So this mail to share the question, and a proposal - *wow64*: the new multi-arch wow64 configuration, which mimics windows wow64 architecture ; dropping the 'new' to match with windows (and also, not sure that in 10years from now it will still be "new") - (wine)*old wow64*: the wine-only old wow64 configuration if needed (at least to remind that they exist) - *pure32*: the 32bit only configuration - *pure64*: the 64bit only configuration Note: the proposal doesn't include whether the configuration can run a module for a given CPU. That's questionable. For comments, rant, other proposals... better ideas TIA

5 6

Wine staging 8.5 release
by Alistair Leslie-Hughes 01 Apr '23

01 Apr '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.5 (537 patches are applied to wine vanilla) The patchinstall.sh script is no longer available and users should use the staging/patchinstall.py instead. Upstreamed (Either directly from staging or fixed with a similar patch). * dinput: Allow mapping of controls based of Genre type. Added: * MR 2449: Allow Diable IV to run without reporting errors. * [53826] Attempting to install / update battle.net fails with Qt error. Updated: * mfplat-streaming-support 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Should we stop linking to FAudio for our XAudio implementation?
by Zebediah Figura 29 Mar '23

29 Mar '23

Hi all, This may seem something of a controversial question, but I am concerned that FAudio is not a good fit for Wine, mainly because of its licensing considerations. Recently I found a bug in FAudio wherein it does not properly handle unaligned buffers. While in the process of drafting a fix, I was stymied multiple times by its rather broken resampler, and when I sought to try to fix that, I found that it was a rather difficult endeavour, which led me to propose replacing it with an external library such as GStreamer. Unfortunately FAudio cannot, counterintuitively, link to LGPL code, because it needs to be able to run on embedded platforms, which (for reasons I do not understand) cannot ship any LGPL code. While I can to some degree respect the decision of FAudio to target platforms that forbid copyleft licensing, I do not think this aligns well with the interests of the Wine project—a project which specifically chose copyleft licensing. More personally, I do not want to have to fix the FAudio resampler or implement another resampler with a non-copyleft license (and I am not even particularly sure that I can, given my familiarity with resamplers in LGPL projects such as GStreamer and Wine). Besides this, it is probably worth noting that we do not seem to gain much from continuing to rely on FAudio. There would be the usual benefit of relying on upstream development, but development on FAudio seems very scarce, especially when restricted to parts relevant to Wine, and much of that is from Wine contributors anyway. (And, of course, due to our bundling practices, there is hardly the usual benefit of size or modularity in linking to external libraries.) Of course we would be well served by simply importing the current version of FAudio; I do not mean to propose that we reimplement XAudio entirely, but rather begin to modify it in ways that would not be acceptable upstream. This would mean replacing the resampler, as well as perhaps also the mixer, and probably with the ones from GStreamer, which is already a dependency of ours, and which has a very featureful resampler and mixer, and a much higher rate of development overall. Do others in the Wine community have thoughts or opinions on this matter? ἔρρωσθε, Zeb

4 8

TestBot News: Missing dlls and VM updates
by Francois Gouget 19 Mar '23

19 Mar '23

I reviewed the tests that are skipped because the dll is missing on Windows and I found 4 tests that are never run on Windows which makes them a bit pointless: * d3dcompiler_46 I can install version 43 and 47 from dxwebsetup.exe without trouble. But d3dcompiler_46.dll? No idea. * d3drm Is this a deprecated Direct 3D 8 dll? dxwebsetup.exe does not install it. * msvcr70 As far as I know this dll is part of the Visual Studio 7.0 runtime. But that runtime is nowhere to be found. * msvcrtd The test look like they succeed on test.winehq.org but in fact all they do is skip the tests: debug.c:45: Tests skipped: LoadLibraryA failed to load msvcrtd.dll with GLE=126 (where 126 == ERROR_MOD_NOT_FOUND) That's the debug version of the Visual C++ C library. As such it's not shipped by the runtime redistributables. Also, which C runtime does it correspond to? (iirc it was already there in the 90s) Note: I'd rather not download these dlls from the many 'not.trojan.horse.dlls.trust.me.com' websites. VM updates: * debiant The gst-plugins-base1.0-dev maintainer intentionally removed multi-arch support in version 1.20.3-2. As a result GStreamer support went missing in 32-bit builds when Wine's detection code was tweaked recently, which in turn caused a lot of new failures (bug 53977). So I hacked multi-arch support back in and the 32-bit tests are back to normal. Another point is that updating the X11 / Mesa packages causes the X server to crash during the Direct 3D tests. So for now that VM is frozen in time. That's all worrying for the future Debian 12. * w11pro64 I added a bunch of Visual Studio C runtime dlls, including msvcr71 which I got through the .Net 1.1 framework. I also added a number of Direct 3D dlls that don't ship with Windows by default. * w1064v1709 It seems this snapshot was not entirely idle so I retook it after Windows Update finished installing the already downloaded updates (see bug 54158). This does not seem to have made much of a difference :-( (particularly for bug 53227) * w1064v1909 Windows Defender was not disabled and was intefering with the tests from time to time. That's because 1909 is the first Windows version where Defender cannot be disabled and where I have to exclude the WineTest folder instead. This is fixed now. * w1064v2004 This snapshot also had some trouble with Windows Update not being idle so I retook it. This does not seem to have made much of a difference either :-( -- Francois Gouget <fgouget(a)codeweavers.com>

4 12

Wine staging 8.4 release
by Alistair Leslie-Hughes 18 Mar '23

18 Mar '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.4 (532 patches are applied to wine vanilla) The patchinstall.sh script is no longer available and users should use the staging/patchinstall.py instead. 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

wine-7.0.2-rc1 Available
by Michael Stefaniuc 16 Mar '23

16 Mar '23

Hello, I have pushed wine-7.0.2-rc1 (f25a27c2e57c9f8c061746a813ace405fbd39073) to https://github.com/mstefani/wine-stable/tree/oldstable https://people.redhat.com/mstefani/wine/stable/ And created the draft merge request https://gitlab.winehq.org/wine/wine/-/merge_requests/2402 Nothing fancy so here we go: What's new in this release: - Various bug fixes ---------------------------------------------------------------- Bugs fixed in 7.0.2 (total 43): - #36711 Sid Meier's Civilization IV crashes while loading saved game (GOG.com complete, Colonization, Warlords, Beyond the Sword)('winetricks -q msxml3' is a workaround) - #39346 Lego Rock Raiders crashes on startup (d3drm_device_init doesn't handle device version 3 case) - #40444 Find doesn't jump to a found item in WinSCP when editing a file - #42751 Multiple applications crash on unimplemented function msvcr{100,110}.dll.?_Schedule@_StructuredTaskCollection@details@Concurrency@@QAEXPAV_UnrealizedChore@23@@Z (Gas Guzzlers Combat Carnage, Clip Studio Paint, Cube World, Intel ACAT) - #42857 Can't select a fixture in FreeStyler's fixture editor - #44814 cygwin's bsdtar.exe needs a better ntdll.NtQueryEaFile stub - #46822 Edit control in ADL search dialog gets initially not drawn in DC++ 0.868, regression - #47375 Multiple applications crash on unimplemented function msvcr120.dll.?_Schedule@_StructuredTaskCollection@details@Concurrency@@QEAAXPEAV_UnrealizedChore@23@@Z (Photoshop C 2018, CLIP Studio Paint) - #48487 MSYS based Git 2.25 installer reports 'could not decode hex <hexstring>' (needs support for CryptStringToBinaryW CRYPT_STRING_HEX) - #48600 Bloomberg Terminal needs unimplemented function dbghelp.dll.SymSrvGetFileIndexInfo - #49285 PNotesPortable crashes inside WritePrivateProfileStructW - #50948 taskmgr.exe: wrong memory usage unit (GB => MB) - #51788 windowscodecs:wmpformat test_decode() fails randomly - #51842 include/winnt.h:403:50: error: size of unnamed array is negative - #52457 CNG Encryption Failure (BCryptEncrypt) - #52534 ListView: multi select never sends LVN_ODSTATECHANGED - #52545 ACE rights parser should allow octal and decimal formats - #52686 DateAdd not implemented - #52831 Kernel32::GetSystemPowerStatus returns invalid data if /sys/class/power_supply/BAT0 is missing - #52841 Leverless arcade controller SOCD cleaning does not work - #52972 wineusb.sys: add_usb_device erroneously releases critical section on failure path - #52975 VTFEdit fails to start: err:module:LdrInitializeThunk "MSVCP80.dll" failed to initialize, aborting - #53003 XM6 TypeG: some MIDI note-on messages aren't sent to MIDI devices (MIDI running status isn't supported in the MIDI mapper) - #53005 quartz:systemclock Fails after timeGetTime() wraps - #53027 Port Royale 4 crashes with wined3d_texture* - #53032 winedevice.exe segfaults on exit when built with GCC - #53051 Kvaser software crashes on unimplemented function ntoskrnl.exe.ExNotifyCallback - #53123 ListView: Ctrl+Shift+LMouse multiselect on LVS_OWNERDATA listviews erroneously sends LVN_ODSTATECHANGED - #53169 Rich edit control becomes unstable or trips assertion after ITextRange::SetFont is called - #53170 Rich edit control becomes unstable or trips assertion after changing TextFont properties - #53234 nsi:nsi - test_ndis_ifinfo() fails randomly on Windows 10 1507 - #53310 Roblox Fails With HttpSendRequest - #53335 Crash when converting an rich text editor already containing text into a password input - #53455 shell32:recyclebin - test_query_recyclebin() gets unexpected recyclebin size in Wine - #53569 postgresql installer 9.3 needs correct string length returned from fso.GetTempName - #53587 comctl32 GetWindowSubclass crash in Notepad++ (v8.4.3 and 8.4.4 only) - #53614 KeePassXC crashes on unimplemented function msvcp140.dll.?ReportUnhandledError@_ExceptionHolder@details@Concurrency@@AEAAXXZ - #53645 AIMP 3 causes memory leaks - #53706 NtDeviceIoControlFile() is quite slow when called with and invalid handle - #53714 SQLGetInfo(W) doesn't fill StringLength when InfoValue is NULL - #53800 CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 - #53821 winbase.h: ReOpenFile declaration missing (and not available in any other header) - #53832 wbemprox: where-clause seems to be case-sensitive ---------------------------------------------------------------- Changes since 7.0.1: Akihiro Sagawa (2): midimap: Handle MIDI running status. mciqtz32: Fix thread handle leak if a second play. Alex Henrie (3): ntoskrnl: Add ExNotifyCallback stub. ntdll: Don't hard-code the battery and AC adapter names on Linux. user32: Plug icon handle leak in MDI_AugmentFrameMenu (Coverity). Alexandre Julliard (4): shell32: Don't return an uninitialized pointer on error in enum_trash_items(). urlmon/tests: Fix race condition in abort test. mountmgr: Don't crash if connecting to dbus fails. gdiplus: Get the compositing mode directly from the graphics object. Alistair Leslie-Hughes (8): d3drm: Support IDirect3D3 when creating device. ntdll: Check return parameter before use. ntdll: RtlFirstFreeAce only return FALSE on error. ntdll/tests: Add RtlFirstFreeAce tests. dsdmo: Add Echo FX Support. dsdmo: Add Compressor FX Support. odbc: SQLGetInfoW allow NULL parameter InfoValue. crypt32: Only report Unimplemented decoder when not found in external dll. Angelo Haller (9): comctl32/tests: Add hold_key and release_key functions. comctl32/tests: Add multi select tests for ownerdata listviews. comctl32/tests: Add change sequence for ownerdata listviews. comctl32/listview: Send one deselect all items notification for LVS_OWNERDATA listviews. comctl32/listview: Move sending LVN_ODSTATECHANGED notifications to a function. comctl32/listview: Send LVN_ODSTATECHANGED only for LVS_OWNERDATA listviews. comctl32/listview: Send LVN_ODSTATECHANGED notification for LVS_OWNERDATA listview on selection changes. comctl32/listview: Don't send LVN_ODSTATECHANGED for empty ranges. comctl32/tests: Add more ownerdata listview tests. Claire Girka (1): winepulse: Fix memory leak in pulse_create_stream in some error cases. Daniel Lehman (1): kernelbase: Pass va_list copy to internal RtlFormatMessage. David Curtiss (1): ws2_32: Allow getsockname after AcceptEx. David Kahurani (2): win32u: Use allocator mechanism to allocate DC attributes. ieframe: Fix memory leak in open_dde_url. Dmitry Timoshkov (2): comctl32/tests: Add iItem and uChanged to LVN_ITEMCHANGING/LVN_ITEMCHANGED context. sechost: Support decimal or octal access rights in ConvertStringSecurityDescriptorToSecurityDescriptor. Eric Pouech (2): wldap32: Fix compilation in 32-bit. winedbg: Fix retrieving integral values. Esme Povirk (1): wmphoto: Zero user buffer before calling jxrlib Copy. Fabian Maurer (1): kernel32: Prevent null pointer dereference in WritePrivateProfileStructW. Gijs Vermeulen (2): dbghelp: Add SymSrvGetFileIndexInfo stub. msvcp140: Add _ExceptionHolder::ReportUnhandledError stub. Hans Leidekker (4): wininet: Remove assertion that is no longer valid in Windows 10. wininet: Always reset the second input buffer in netcon_secure_connect_setup(). bcrypt: Force symmetric key reset if necessary. wbemprox: WQL string comparisons are case insensitive. Hugh McMaster (1): conhost: Set correct face name when the specified font is not available. Huw D. M. Davies (1): nsi: Use the correct members for the error and discard counts. Jeff Smith (2): d3drm/tests: Clean up some magic values. d3drm: Fix components of palette built when loading texture from file. Jinoh Kang (3): wineusb.sys: Remove erroneous call to LeaveCriticalSection() in add_usb_device. riched20: Commit and wrap paragraphs after changing text properties. riched20: Ensure MEPF_COMPLEX is unset when in password input mode. Kevin Puetz (2): winecrt0: Remove free_delay_imports. vbscript: Don't abort when trying to TRACE() functions with many arguments. Limstash Wong (1): taskmgr: Fix the unit in memory usage graph on performance tab. Louis Lenders (1): msvcr80: Update manifest resource. Martin Storsjö (2): include: Add declarations of _alloca and alloca for MSVC mode. ntdll: Add SEH unwind info in ARM assembly functions/trampolines. Mihail Ivanchev (1): include: Add prototype for ReOpenFile(). Nikolay Sivov (2): vbscript: Implement DateSerial(). vbscript: Implement DateAdd(). Paul Gofman (3): msxml3: Use node_get_text() in domelem_get_nodeTypedValue() if no type is present. crypt32: Support CRYPT_STRING_HEX in CryptStringToBinary(). winhttp/tests: Avoid race condition on closing connection in server_thread(). Piotr Caban (4): msvcr120: Add missing _StructuredTaskCollection destructor spec file entry. msvcrt: Fix _wputenv_s return value on error. msvcrt: Fix _putenv_s return value on error. msvcrt: Fix _wputenv_s invalid argument handling. Robert Wilhelm (4): scrrun: Added DateCreated property for IFile. scrrun: Add test for correct string length returned from GetTempName. scrrun: Correct string length returned from GetTempName. scrrun: Avoid memory leak in error case. Rémi Bernon (2): winebus.sys: Implement SOCD neutral cleaning for hatswitches. server: Avoid using pointer value after realloc. Santino Mazza (3): riched20/tests: When selection is out of view, the scrollbar should move. riched20: Ensure that cursor is visible when selecting text. jscript: Return ParseProcedureText when compile fails. Sebastian Lackner (1): ntdll: Improve stub of NtQueryEaFile. Tim Clem (1): kernelbase: Don't assume the length of the process image name. Torge Matthies (8): msvcr110: Add _StructuredTaskCollection::_StructuredTaskCollection_ctor stub. msvcr120: Add _StructuredTaskCollection::_StructuredTaskCollection_dtor stub. msvcr100: Add _StructuredTaskCollection::_Schedule stub. msvcr110: Add _StructuredTaskCollection::_Schedule_loc stub. msvcr100: Implement invalid_multiple_scheduling exception. msvcr100: Factor out the mapping of a context to a scheduler. msvcr100: Implement _StructuredTaskCollection::_Schedule and _Schedule_loc. msvcp90: Fix segfault in bad_alloc exception default constructor. Zebediah Figura (7): quartz/systemclock: Use timeGetTime() to retrieve the current time. wined3d: Correctly handle 3D textures in wined3d_view_{load, invalidate}_location(). ntdll: Add a fast path for NtDeviceIoControlFile(INVALID_HANDLE_VALUE). xslt: Use win32config.h from the correct directory. ntdll: Calculate the necessary length after calling snprintf() in SystemWineVersionInformation. msvcrt: Add SEH annotations for sse2_memcpy(). libwine: Avoid comparing the result of pointer arithmetic to zero. Zhiyi Zhang (14): shell32: Correct SHOpenFolderAndSelectItems() prototype. include: Add SHOpenFolderAndSelectItems() declaration and flags. shell32/tests: Add SHOpenFolderAndSelectItems() tests. shell32: Implement SHOpenFolderAndSelectItems(). comctl32/tests: Add GetWindowSubclass() tests. comctl32: Check reference data pointer before using it. comctl32/tests: Test that changing focus for edit controls doesn't repaint immediately. comctl32/edit: Don't repaint immediately when getting focus. winex11.drv: Handle X errors from glXCopyContext(). winex11.drv: Don't compare error event serial if it's zero. winegstreamer: Always check the return value from mf_media_type_from_wg_format(). gdi32/tests: Add more tests for GetTextMetrics(). win32u: Choose a smaller ppem to avoid exceeding the requested font height. win32u: Fix a memory leak. bye michael

1 0

fileapi.h / Kernel32: GetTempPath2A/W() implementation
by Kevin Connor Arpe 16 Mar '23

16 Mar '23

Hello, This is my first time posting to this mailing list. (This email is a bit long... sorry!) I am a developer writing Win32 code using Wine on Debian Linux. I tried to use the Win32 API function GetTempPath2W(), but my Wine version does not support it. I checked out the Wine source code and found GetTempPathW() here: dlls/kernelbase/file.c ... but did not find GetTempPath2W(). First, if this function is already in the pipeline (another feature branch, etc.), please let me know... and ignore the rest of this email! :-) From GetTempPathW() docs: https://learn.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-gett… "Note: Apps should call GetTempPath2 instead of GetTempPath." From GetTempPath2W() docs: "When calling this function from a process running as SYSTEM it will return the path C:\Windows\SystemTemp" The implementation looks rather straightforward except this part: "process running as SYSTEM". How to detect this? I found a good blog post from (the legend) Raymond Chen: https://devblogs.microsoft.com/oldnewthing/20210106-00/?p=104669 Sample code looks like this: << #include <wil/token_helpers.h> bool DoesTokenRepresentSid(HANDLE token, WELL_KNOWN_SID_TYPE type) { // maps to GetTokenInformation(token, TokenUser, ...); auto user = wil::get_token_information<TOKEN_USER>(token); return !!IsWellKnownSid(user->User.Sid, type); } bool IsCurrentProcessRunningAsSystem() { return DoesTokenRepresentSid(GetCurrentProcessToken(), WinLocalSystemSid); } bool IsCurrentThreadRunningAsSystem() { return DoesTokenRepresentSid(GetCurrentThreadEffectiveToken(), WinLocalSystemSid); } >> Reading the WIL source code on GitHub, I understand the required Win32 calls. In short, I plan to re-write the above same code using pure Win32 code (remove the WIL requirement). My questions: 1. Do you agree with Raymond Chen's technique for Wine source code? (Or: Is there a better way to do it for Wine source code?) 2. Should my SYSTEM account test use IsCurrentProcessRunningAsSystem() or IsCurrentThreadRunningAsSystem()? If I read the official docs literally, I think "process" not "thread". Please advise. 3. Reading the WIL code: TOKEN_INFORMATION_CLASS TokenUser appears to require this pattern: 1. Call GetTokenInformation() to get required buffer size 2. malloc buffer 3. Call GetTokenInformation() again with buffer 4. Check: WinLocalSystemSid == ((TOKEN_USER *) buffer)->User.Sid 5. free buffer 1. Is there a way to avoid the above steps? malloc+free seems like overkill to decide if the current user is SYSTEM! 2. Do I misunderstand the WIL code? Reading the Wine code for: GetTokenInformation() -> NtQueryInformationToken(): TOKEN_USER appears to be fixed size. Why does WIL think TOKEN_USER is not fixed size? I am confused! :-) Kind regards, Kevin Connor ARPE Tokyo, Japan

4 3

dxcore.dll or dxgi?
by James McDonnell 16 Mar '23

16 Mar '23

Hi-d ho winerinos, I have made some changes to add a dxcore.dll on a personal branch. I want to upstream the changes, however I'm unsure of whether I should create a new dll or just append it to dxgi. Dxcore overlaps with dxgi, but presumably has separate functionality as well. Thoughts? Here is my branch if anyone wanted to review the commits. https://gitlab.winehq.org/ElementalWarrior/wine/-/commits/affinity-photo2 Cheers, James

3 2

Wine staging 8.3 release
by Alistair Leslie-Hughes 04 Mar '23

04 Mar '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.3 (532 patches are applied to wine vanilla) The patchinstall.sh script is no longer available and users should use the staging/patchinstall.py instead. Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Add helper function to delete free blocks. * ntdll: Improve heap allocation performance. (v2) Added: * [52012] Implement _vcomp_for_dynamic_init_i8. 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Upcoming vkd3d 1.7 release
by Henri Verbeet 24 Feb '23

24 Feb '23

Hi all, The tentative release date for vkd3d 1.7 is March 22, in slightly under 4 weeks. Please test your applications for any regressions, review any API changes since vkd3d 1.6, and so on. While starting today it will become increasingly harder to make major code changes until the release, improvements to the API documentation and tests are welcome as always. For vkd3d 1.8, the release following 1.7, we're currently aiming for a date in late June. Regards, Henri

1 0

[PATCH] user32/tests: fixed size passed to ToUnicode
by Marcus Meissner 24 Feb '23

24 Feb '23

Signed-off-by: Marcus Meissner <marcus(a)jet.franken.de> --- dlls/user32/tests/input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dlls/user32/tests/input.c b/dlls/user32/tests/input.c index ee39b11fc12..be41078bf29 100644 --- a/dlls/user32/tests/input.c +++ b/dlls/user32/tests/input.c @@ -3186,7 +3186,7 @@ static void test_ToAscii(void) ok(character == '\r', "ToAscii for Return was %i (expected 13)\n", character); wstr[0] = 0; - ret = ToUnicode('A', SC_A, state, wstr, sizeof(wstr), 0); + ret = ToUnicode('A', SC_A, state, wstr, ARRAY_SIZE(wstr), 0); ok(ret == 1, "ToUnicode(A) returned %i, expected 1\n", ret); str[0] = '\0'; -- 2.39.2

2 2

Wine staging 8.2 release
by Alistair Leslie-Hughes 18 Feb '23

18 Feb '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.2 (531 patches are applied to wine vanilla) The patchinstall.sh script is no longer available and users should use the staging/patchinstall.py instead. For those that wanted to use ODBC in windows applications, this is the release for you. For those using ADO to connect to a dababase via ODBC, you will still need to use the native version of msado15 and msdasql. Through some of the bugs have been identified and fixed in this wine release there is still more work to be done. Some cavets on the ODBC support * Only the Unicode drivers for MySql/PostgreSQL were tested. * Not all functions have been mapped, so lodge a bug if something is missing. Developers. If anybody has time to have a look over or reivew the patchset, that would be great. Don't be scared of the 43 patches, most of them are calls into the loaded driver (boiler plate stuff). Users. If you are a user of unixODBC with wine, it would be great if you could post on bug 54499, the database used or if you prefer to use the standard windows driver. Known issues. * Using SQLDriverConnectW to connect to an ANSI ODBC driver will fail (works on windows). * The Driver DLL is possible loaded multiple times (Should have map of driver/function table). Upstreamed (Either directly from staging or fixed with a similar patch). * None Added: * [52233] Black NPC's skin or minor rendering glitches in multiple games (Batman: Arkham Knight, Steel Division: Normandy 44) * [48220] dxruby needs WAVE form loading implemented * [45135] Black Rockman Shooter has no sound, implementation missing in dmime * [34751] Aura: Fate of the Ages: sounds aren't played, but music works fine * [9027] No sound for rise of nations - all versions * [54499] Native ODBC drivers should be able be used. Updated: * Install scripts updated to Python 3 * winex11-Fixed-scancodes (was winex11-key_translation) * ntdll-NtDevicePath * ntdll-Junction_Points 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

How do I package the output of wine as a deb file?
by zhengxianwei 18 Feb '23

18 Feb '23

I've compiled wine on a 64-core machine, and I want to package it up and send it to another machine for installation. I checked 2 pages, but still not sure how to do this https://wiki.winehq.org/Building_Wine https://wiki.winehq.org/Packaging

1 0

Debugging channel weirdness
by Zebediah Figura 14 Feb '23

14 Feb '23

Hi all, I was running into some odd behaviour while debugging—specifically, I found that specifying the d3d channel in WINEDEBUG was cutting my performance in half, even when disabling logging, and even when it should have been functionally identical to a run without the d3d channel specified. I was able to "fix" this inconsistency with this diff: diff --git a/dlls/ntdll/thread.c b/dlls/ntdll/thread.c index 1bd8f900d22..f0e4b824918 100644 --- a/dlls/ntdll/thread.c +++ b/dlls/ntdll/thread.c @@ -103,7 +103,11 @@ unsigned char __cdecl __wine_dbg_get_channel_flags( struct __wine_debug_channel { pos = (min + max) / 2; res = strcmp( channel->name, debug_options[pos].name ); - if (!res) return debug_options[pos].flags; + if (!res) + { + if (channel->flags & (1 << __WINE_DBCL_INIT)) channel->flags = debug_options[pos].flags; + return debug_options[pos].flags; + } if (res < 0) max = pos - 1; else min = pos + 1; } Which makes sense to some degree, but leaves three questions unanswered, which I was hoping someone might be able to cluebat me on: (1) Why does setting channel->flags affect performance at all? I'm thoroughly baffled by this one. (2) Why was this diff not applied in the first place? (Simple oversight?) (3) Why does __WINE_DBCL_INIT even exist, if its only purpose is to guard out a single assignment? --Zeb

2 6

Hangover Update
by André Zwing 11 Feb '23

11 Feb '23

Hi, As you might know, Hangover development stalled years ago waiting for the WoW64 support in Wine to complete. With Wine 8.0 (and even better with Jaceks wow branch) this is now done. In October I started to connect Qemu to that WoW64 support in my spare time and it progressed until I finally was able to publish some of that work today. It's still missing instructions and even some patches, but it should give a good introduction on what this will look like. In fact I started to get wowarmhw running, so I could do the first steps on a x86-64 machine to run ARM32 binaries. But exactly this part is missing for now as things changed since then. So in case I made you curious, here's the code :) https://github.com/AndreRH/hangover

1 0

Compiling issues on macOS after 7.20 on ARM
by Jason Millard 10 Feb '23

10 Feb '23

Hello. I’m using parts of Wine (specifically the vbscript engine) while porting Visual Pinball to be cross platform. I have been using the WIDL utility extensively and it has worked great. I wanted to keep my patches up to date so I don’t fall behind, however I am having issues compiling wine after version 7.20. This was my typical compile: brew install llvm llvm-mingw git clone -b wine-7.20 git://source.winehq.org/git/wine.git git clone git@github.com:vpinball/pinmame.git cd wine export MACOSX_DEPLOYMENT_TARGET="10.14" export LDFLAGS="-Wl,-rpath,/opt/X11/lib" export PATH="$(brew --prefix llvm)/bin:$PATH" export PATH="$(brew --prefix bison)/bin:$PATH" ./configure --without-freetype make -j10 tools/widl/widl -o ../vpinmame_i.h --nostdinc -Ldlls/\* -Iinclude -D__WINESRC__ -D_UCRT ../pinmame/src/win32com/VPinMAME.idl Now with anything past 7.20 I’m getting: configure: error: PE cross-compilation is required for ARM64, please install clang/llvm-dlltool/lld, or llvm-mingw. Is there anyway to disable this? Thanks Jason

2 4

Wine staging 8.1 release
by Alistair Leslie-Hughes 03 Feb '23

03 Feb '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.1 (475 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * rpcrt4: Avoid implicit cast of interface pointer. * include: Add _XHR enum values * ntdll-Builtin_Prot (removed as PE conversion is complete) Added: * None Updated: * ntdll-Placeholders 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: How should one report GitLab CI bugs?
by Francois Gouget 26 Jan '23

26 Jan '23

On Thu, 19 Jan 2023, Alexandre Julliard wrote: [...] > Would it mean failures that only happen on Gitlab CI? Or failures that > happen in CI but also elsewhere? Either way, the distinction doesn't > seem all that useful to me. The idea was that some Wine developers may be more interested in fixing bugs causing false positives in the new CI system (GitLab CI) than in the old one (TestBot). So identifying those in Bugzilla may help them find targets to work on. But of course that assumes that set of developers is non-empty. -- Francois Gouget <fgouget(a)codeweavers.com>

1 0

Re: Alexandre Julliard : shell32: Allocate a full SHITEMID to avoid a compiler warning.
by Eric Pouech 26 Jan '23

26 Jan '23

Le 25/01/2023 à 22:22, Alexandre Julliard a écrit : > Module: wine > Branch: master > Commit: c844ebdb0ae8994ee4f3d1d3c1697ece06f52a4e > URL: https://gitlab.winehq.org/wine/wine/-/commit/c844ebdb0ae8994ee4f3d1d3c1697e… > > Author: Alexandre Julliard <julliard(a)winehq.org> > Date: Tue Jan 24 22:22:52 2023 +0100 > > shell32: Allocate a full SHITEMID to avoid a compiler warning. > > --- > > dlls/shell32/shfldr_fs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/dlls/shell32/shfldr_fs.c b/dlls/shell32/shfldr_fs.c > index 662d8b52d5b..d47911dbef7 100644 > --- a/dlls/shell32/shfldr_fs.c > +++ b/dlls/shell32/shfldr_fs.c > @@ -347,7 +347,7 @@ IShellFolder_fnParseDisplayName (IShellFolder2 * iface, > /* Special case for the root folder. */ > if (!wcsicmp( szPath, L"\\\\?\\unix\\" )) > { > - *ppidl = SHAlloc(sizeof(USHORT)); > + *ppidl = SHAlloc(sizeof(*ppidl)); shouldn't it be sizeof(**ppidl) instead to better match the patch description?

1 0

Problem with the wine-gitlab mailing list archive?
by Francois Gouget 26 Jan '23

26 Jan '23

The wine-gitlab mailing list archive shows no new message since last Tuesday (2022-10-18). Yet I did receive emails on that list since then. https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/ What's going on? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Cahn's Axiom: When all else fails, read the instructions.

4 7

dmloader:dmloader crash on gitlab-debian-64
by Francois Gouget 26 Jan '23

26 Jan '23

On test.winehq.org I see that dmloader:dmloader crashed on gitlab-debian-64 due to an assertion (2023-01-12): 060c:loader: 104 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. dmloader:loader:060c done (-2147483391) in 0s 88B Test failed: crash (80000101) https://test.winehq.org/data/patterns.html#dmloader:loader I'd like to know if this is caused by the one assert() in stream_get_chunk(). A backtrace could help in that regard but: * The test report on test.winehq.org only has the test output, not Wine's stderr traces which is where a backtrace would be. http://winetest.dolphin/data/047118247ce489a7138428c8b2cd5692ed04337e/linux… * And the GitLab log has neither the test output nor the Wine traces. https://gitlab.winehq.org/wine/wine/-/jobs/8996 So are the Wine traces available somewhere for GitLab's nightly WineTest runs? -- Francois Gouget <fgouget(a)codeweavers.com>

2 2

Wine staging 8.0 release
by Alistair Leslie-Hughes 25 Jan '23

25 Jan '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.0 (478 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

8.0 release notes (draft)
by Alexandre Julliard 24 Jan '23

24 Jan '23

Folks, The final 8.0 will be released shortly. Thanks to everybody who helped fix regressions! We didn't quite make it back to the 7.0 count, but we've still made very good progress, with over 160 bugs fixed during code freeze. Below is the draft of the release notes, please have a look and let me know if anything is incorrect or missing. Thanks to Jacek, Nikolay, Rémi and Zeb for their help with this! -- Alexandre Julliard julliard(a)winehq.org ---------------------------------------------------------------- What's new in Wine 8.0 ====================== *** PE modules - After 4 years of work, the PE conversion is finally complete: all modules can be built in PE format. This is an important milestone on the road to supporting various features such as copy protection, 32-bit applications on 64-bit hosts, Windows debuggers, x86 applications on ARM, etc. However, some modules still perform direct calls between the PE and the Unix part, instead of going through the NT system call interface. The remaining direct calls will be removed during the Wine 8.x development phase. - A special syscall dispatcher is used for PE -> Unix transitions, to avoid the overhead of a full NT system call. This minimizes the performance impact of the new architecture, in particular for the OpenGL and Vulkan libraries. - Building mixed Windows/Unix libraries in ELF format (.dll.so libraries) is still supported for use in Winelib applications. However, such applications won't support features enabled by the NT syscall interface, such as WoW64 without 32-bit libraries. *** WoW64 - WoW64 thunks are implemented for essentially all Unix libraries, enabling a 32-bit PE module to call a 64-bit Unix library. Once the remaining direct PE/Unix calls have been removed, this will make it possible to run 32-bit Windows applications without any 32-bit Unix library. - When the 32-bit Wine loader isn't found, 32-bit applications are started in the new "Windows-like" WoW64 mode (where 32-bit code runs inside a 64-bit host process). This mode can be enabled by building with the '--enable-archs' configure option. Since in case of configuration errors it is possible for it to be triggered inadvertently, applications started in this mode print the warning "starting in experimental wow64 mode". *** Graphics - The "Light" theme is enabled in the default configuration, for a more modern look. Other themes can still be configured through WineCfg. - The graphics drivers (winex11.drv, winemac.drv, wineandroid.drv) are converted to run on the Unix side of the syscall boundary, and interface with the Unix side of the Win32u library. - The Print Processor architecture is implemented. This will be used to avoid direct PE<->Unix calls in the printer driver. - Effects are supported in Direct2D, including description parsing and a number of core objects. - Command lists recording and playback are implemented in Direct2D. - The Vulkan driver supports up to version 1.3.237 of the Vulkan spec. *** Direct3D - Many optimizations related to streaming map acceleration are implemented, in common code as well as in the GL renderer. Depending on the application, this may result in major performance improvements. - Adapter video memory budget change notifications are implemented. - The Vulkan renderer supports setting multiple viewports and scissor rectangles. - Several Direct3D 10 and 11 features, which were already implemented, are accurately reported through capability flags: - Per-format support for vertex and index buffers. - Per-format support for all capabilities via D3D11_FEATURE_FORMAT_SUPPORT. - No-overwrite maps on shader resources and constant buffers. - Partial range binding of constant buffers. - For convenience, a new WINE_D3D_CONFIG environment variable may be used instead of modifying the HKEY_CURRENT_USER\Software\Wine\Direct3D registry key. The value is a comma- or semicolon-separated list of key-value pairs, e.g.: WINE_D3D_CONFIG="renderer=vulkan;VideoPciVendorID=0xc0de" If an individual setting is specified in both the environment variable and the registry, the former takes precedence. - The Direct3D graphics card database recognizes more graphics cards. - The Vulkan renderer limits the maximum Direct3D feature level based on available Vulkan features. *** Audio / Video - The MPEG-1 audio decoder filter for layers 1 and 2, and the separate filter for layer 3, are both implemented on top of GStreamer. - The ASF reader filter is implemented. - The OpenAL32.dll wrapper library is removed, in favor of the native OpenAL32.dll library shipped by Windows applications. *** Media Foundation - Content type resolution is improved in the Media Foundation Player. - Rate control is implemented. - The Enhanced Video Renderer default mixer and presenter are better supported. - The DirectShow filter is implemented in the Enhanced Video Renderer. - An initial framework is implemented for the Writer encoding API. - The topology loader is better supported. *** Input devices - Controller hotplug support is greatly improved, and controller removal and insertion are correctly dispatched to applications. - Driving wheel device detection and reporting is better implemented, using the SDL library and HID usages as hints for the device types. - Force feedback effect support is improved, specifically with driving wheels controllers. - The HID Haptics specification is used for left / right motor rumble and trigger rumble. It makes it possible for device drivers to expose haptics support over HidRaw, and overcome EvDev limitations. - The Joystick Control Panel is redesigned, with new graphics and a dedicated view for XInput gamepads. - Sony DualShock and DualSense controllers are supported when the hidraw backend is used, and exposed to applications in the same way as they are on Windows. - The Windows.Gaming.Input module is introduced, one of the first WinRT modules in Wine, implementing a new programming interface to access gamepads, joysticks and driving wheel devices. For this new input API, hotplug notifications are also implemented, as well as force feedback effects and haptics. This API is the first one to support trigger rumble. *** Internationalization - A proper locale database, in Windows locale.nls format, is generated from the Unicode CLDR database. The list of supported locales is essentially identical to that of the latest Windows version. - Unicode string comparison is based on the Windows Sortkey database and algorithms instead of the Unicode Collation Algorithm, yielding more compatible results. - Characters from high Unicode planes (in UTF-16 encoding) are supported in most functions, in particular for case mappings, BiDi formatting, and character shaping. - The UTF-8 encoding is supported as Ansi codepage. It is enabled when requested by the application's manifest. - Unicode character tables are based on version 15.0.0 of the Unicode Standard. - The timezone data is generated from the IANA timezone database version 2022g. *** Text and fonts - Font linking is enabled for most system fonts, which should fix missing glyphs in CJK locales. - Font fallback in DirectWrite is reworked, with additional support for an large number of scripts. *** Kernel - The ApiSetSchema database is implemented, replacing all the api-ms-* forwarding modules. This reduces both disk space and address space usage. - DOS file attributes are persistent, and stored on disk using the filesystem's extended attributes, in a format compatible with Samba. *** Internet and networking - The Online Certificate Status Protocol (OCSP) is implemented. - More EcmaScript features are supported in JScript standard-compliant mode. - The JScript garbage collector is implemented. - Accessibility support is enabled in Wine Gecko package. - Web Storage, Performance object and more event objects are implemented in MSHTML. *** Mono / .NET - The Mono engine is updated to version 7.4.0. The list of changes can be viewed at https://github.com/madewokherd/wine-mono/releases/tag/wine-mono-7.4.0 *** Builtin applications - All the builtin applications use Common Controls version 6, which enables theming and high-DPI rendering by default. - The Wine Debugger (winedbg) prints thread names in the 'info thread' listing, for applications that set the names of their threads. All internal Wine threads also set their own name. - The QWORD type is supported in the REGEDIT and REG registry tools. - Notepad has a status bar displaying the current cursor position. The Goto Line functionality is also implemented. - The builtin console programs print data in the OEM codepage, for better compatibility with applications reading their output. - The Service Control tool (sc.exe) supports the 'query' command. *** Development tools - The PE conversion has made it necessary to implement a new mechanism to run static C++ constructors in Winelib ELF applications. Unfortunately, this requires the corresponding modules to be rebuilt with Wine 8.0. The rebuilt modules will still run correctly on older Wine versions, but older modules will no longer execute static constructors when run on Wine 8.0. - In regression tests, individual checks can be marked as "flaky". This is useful for checks that depend on external factors such as network timings. The errors are still reported but not counted as failures. - Test failure messages can be printed in color by setting the WINETEST_COLOR environment variable, to make them easier to spot in the test log. - The Resource Compiler (WRC) and Message Compiler (WMC) use the locale.nls database to detect languages and codepages, and thus support all the Windows locales. - The WineDump tool supports printing the contents of Enhanced Metafile spool files, as well as more contents from PDB files. *** Build infrastructure - PE binaries can be built for multiple architectures from the same build tree, using the '--enable-archs' option to configure, for example '--enable-archs=i386,x86_64'. This can be used to enable the experimental WoW64 mode, where 32-bit applications can run without any 32-bit host libraries. - Data types that are defined as 'long' on Windows are defined as 'long' instead of 'int' on all platforms with a 32-bit long type. This is more compatible, but it can cause printf format warnings with Unix compilers. In Winelib code, it can be disabled by defining WINE_NO_LONG_TYPES. - Import libraries can be generated without using dlltool, by passing the '--without-dlltool' option to winebuild. This is used to avoid dlltool bugs with delay import libraries. - Libraries that contain only resources and no code can be built with the '--data-only' option to winegcc, which makes them smaller and more efficient to load. *** Bundled libraries - Faudio is updated to the upstream release 22.11. - LCMS2 is updated to the upstream release 2.14. - LibJPEG is updated to the upstream release 9e. - LibMPG123 is updated to the upstream release 1.31.1. - LibPng is updated to the upstream release 1.6.39. - LibTiff is updated to the upstream release 4.4.0. - LibXml2 is updated to the upstream release 2.10.3. - LibXslt is updated to the upstream release 1.1.37. - Zlib is updated to the upstream release 1.2.13. *** Platform-specific features - The experimental WoW64 architecture is supported on macOS versions from 10.15. - 64-bit time_t is supported on 32-bit Linux with recent Glibc versions. - Exception unwinding on ARM platforms is extended with EHABI support on ARM32 and Dwarf support on ARM64. *** Miscellaneous - RSA encryption and the RSA-PSS signing algorithm are implemented. - An initial version of the UI Automation API is implemented. - C++11 syntax is supported in function name demangling. *** External dependencies - The vkd3d and LDAP libraries are bundled in the source tree and built as PE. The corresponding Unix libraries are no longer needed. - The OpenAL library is no longer used.

3 2

Wine staging 8.0-rc5 release
by Alistair Leslie-Hughes 22 Jan '23

22 Jan '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.0-rc5 (478 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

[WINE-CE] Wine-CE Can Run Cross Instruction Architecture Windows App
by fanwj＠mail.ustc.edu.cn 19 Jan '23

19 Jan '23

Wine-CE (Chimera Edition) is a compatibility layer capable of running Windows applications on Cross-architecture paltform of Linux. It is base on Wine Project and Qemu Project. Project Address: https://gitee.com/fanwenjie/wine-ce TEST App: Sword and Fairy 3 Demonstration: https://www.bilibili.com/video/BV1Kd4y157Lm

2 1

How should one report GitLab CI bugs?
by Francois Gouget 18 Jan '23

18 Jan '23

How should one report GitLab CI bugs? I'm thinking of two types of bugs. 1. Wine test bugs that specifically happen on the GitLab CI infrastructure. See for instance bug 54334 which describes a set of qasf:asfreader failures that has, so far, only been seen in the Linux GitLab CI. I'm thinking some Wine developers may be particularly interested in getting such bugs fixed and thus would want to have a way to find them. Would a 'gitlabci' or just 'ci' keyword be appropriate? 2. Bugs and missing features in the GitLab CI infrastructure itself. For instance the failures that gitlab-win10-21h2 gets in the ole32:clipboard, riched20:richole and user32:msg tests strongly suggest that the AMD driver was installed with its Adrenalin GUI. Since it is known to interfere with the clipboard this could be considered a bug in that Windows 10 VM configuration. (Alternatively one could argue the tests should be modified to be resistant to such interference which would move this issue to the first category.) Which product should one pick in Bugzilla for reporting such bugs? They would not fit in 'Wine' product or any of the other existing products except 'Wine-Testbot' if one considers the GitLab CI to be the new TestBot (though I think that would be quite confusing). -- Francois Gouget <fgouget(a)codeweavers.com>

1 0

Wine staging 8.0-rc4 release
by Alistair Leslie-Hughes 15 Jan '23

15 Jan '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.0-rc4 (478 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * none Added: * None Updated: * msxml3-FreeThreadedXMLHTTP60 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

FOSDEM 2023
by Henri Verbeet 09 Jan '23

09 Jan '23

This year FOSDEM will once again take place in Brussels, on February 4 and 5. The Wine project won't have an official presence at the conference this year, but a (modest) number of us do intend to visit Brussels during that time. Is anyone else already planning to attend this year? Like previous conferences, you'll be able to find most of us in the #wineconf:matrix.org Matrix room. Henri

2 1

Wine staging 8.0-rc3 release
by Alistair Leslie-Hughes 08 Jan '23

08 Jan '23

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.0-rc3 (474 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * none Added: * None Updated: * ntdll-Junction_Points * winex11-_NET_ACTIVE_WINDOW * ntdll-NtDevicePath 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

HiDPI / Scaling window content
by Jordan Johnston 06 Jan '23

06 Jan '23

Hey all, I'm looking for some pointers on coming up with a hack to better support HiDPI with wine on my hi-res display (not something that would be submitted upstream. "hack" indeed)... As you are all probably aware; while you can adjust DPI in Winecfg, that only affects Windows UI elements ~ but It does not help with anything outside of that... I have some apps that are basically unusable with HiDPI and i've tried multiple solutions, to no avail. (and setting my resolution to 1440x900 isn't a viable solution either). I've been poking around dlls/winex11.drv and I'm wondering if anyone might have pointers on how some of the scale related stuff works? -- I'm wondering if it may be possible to hack the x11 code to multiply the scale of the window contents? (and perhaps, I can then wrap it in an env variable for use)... If anyone has any pointers, or if they think something like this could work -- I'd appreciate your insights (again, I'm just looking for kind of a one-off hack, not something upstream-able.. I'm sure HiDPI compatibility-mode will land upstream, at some point (Windows has this)). While I am familiar with some of Wine's internals - the graphics stack, window management / x11 code is somewhat alien to me. Alternatively, i suppose if someone is working on related code and has a git branch / patchwork available, I'd be open to try that out too. Thanks, and Happy New Year to you all! Jordan

4 7

CPython fails to import symlinked packages in recent versions of Wine Staging - how to debug?
by Sebastian M. Ernst 28 Dec '22

28 Dec '22

Hi all, I have noticed a "new" issue in Wine Staging that I believe must have found its way into it in the October to November time frame. I am heavily using CPython on top of Wine. When Python imports modules, it looks for them in certain paths, specified in `sys.path`. For development, it is common practise to symlink a package's folder from e.g. a git repo into one of the folders contained in `sys.path`, usually `site-packages`. Python then happily imports the module from there for e.g. testing. Many tools are built around this workflow. This used to work with Wine Staging until about September and still works with stable releases of Wine 7. However, in recent versions of Wine Staging, 7.22 and 8.0-rc2, the import fails: ``` Traceback (most recent call last): File "<string>", line 1, in <module> File "Z:\work\bar\__init__.py", line 1, in <module> from .subbar import funcbar ModuleNotFoundError: No module named 'bar.subbar' ``` Python's module import mechanism appears to follow the symlink correctly (into module "bar") but fails to "locate" stuff within the linked folder (submodule "bar.subbar"). Other Python code can at least correctly navigate the linked folder's contents, so I am suspecting a `stat` syscall of some kind to return unusual values. Python's import mechanism was rewritten recently, so only versions prior to Python 3.10 appear to be affected. Many packages support down to 3.7 at the moment. A minimal reproducer, all steps included: https://gist.github.com/s-m-e/84d5fbf5663825a46d9ae98e4636d8ec Wine builds from dl.winehq.org/wine-builds/ubuntu on Ubuntu 22.04. I am not sure what I am looking for. How would I debug this from Wine's side or, in other words, what am I looking for in Wine's logs? Is there something that I can try as a workaround (other than going back to older versions of Wine)? Thanks, Sebastian

2 2

Wine staging 8.0-rc2 release
by Alistair Leslie-Hughes 23 Dec '22

23 Dec '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.0-rc2 (474 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * none Added: * None Updated: * ntdll-NtDevicePath 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

UIRibbon 2022 Edition
by Fabian Maurer 18 Dec '22

18 Dec '22

Hello wine-devel, trying to get more work done on UiRibbon during the holidays, could need some help regarding planning though. Short rundown: uiribbon.dll uses a proprietary binary format to load ribbon structure data. This is created using UICC.exe (shipped by windows SDK) from a XML markup; the binary is embedded into the application. I already reversed the binary format pretty far, and wrote a file format description. That file format description uses Kaitai Struct, a declarative language to generate binary data parsers. Currently I'm working on a Kaitai backend to generate a C parser. I'm probably going to create a folder under "libs" called "uiribbon" where said description and classes generated by kaitai struct (and the runtime) can lie. I do believe that leaving the parser/generation up to Kaitai is a good idea, especially since Wine itself doesn't need to rely on Kaitai. Just need it to regenerate the parser if the format description is modified. I hope that's not a problem, because I really want to go the Kaitai Struct route. The problem: Still not sure how to deal with tests. And if we need to use a writer.. I could make a "custom UICC", a program to turn XML markup into the binary format. Not really useful for applications, but could be a "nice to have" or useful for tests. Lots of work though. Problem 1: Windows doesn't ship UICC by default. That means if we need it for tests, it needs to be installed, or tests won't be able to run. Problem 2: Windows doesn't really have a parser exposed for the binary markup. You can load it and it either works, or doesn't - in the worst case the application simply crashes. Other error cases simply create a broken ribbon, only displayed completely in black. Not easy to see what's wrong, or test if it's wrong to begin with. Although it should probably be possible to extract existing UI elements using uiautomation. Not sure exactly how useful it is. Question is how we do the tests: 1) Put markup and according binaries into the tests, write tests against the binaries to assert what we expect from the written markup. If I recall correctly, embedding binary blobs wasn't too well received. 2) Put markup into tests. Compile it on windows using real UICC, test the parser that way (using something like C_SRCS = ../uiribbon_parser.c to have the parser available in the tests) 3) Compile markup using custom UICC, test the ribbon against windows (using uiautomation, limited testing only). Maybe some combination. Thoughts? Regards, Fabian Maurer

1 0

Re: How to delete a git branch that's not been merged?
by Gerald Pfeifer 17 Dec '22

17 Dec '22

On Tue, 13 Dec 2022, Gerald Pfeifer wrote: > https://wiki.winehq.org/Git_Wine_Tutorial#Deleting_branches has > > Deleting branches > > git branch -D new-branch > > Alas that does not work for me. > > % git branch -a > * master > remotes/origin/HEAD -> origin/master > remotes/origin/dll_soinit.c-stddef.h : > > % git branch -D dll_soinit.c-stddef.h > error: branch 'dll_soinit.c-stddef.h' not found. I believe I can now answer my own question, having dug into it a bit. The invocation above is for *local* branches, branches in the local checkout. To remove a *remote* branch, for example where a merge request was not accepted or was "bad" for some reason, we need to use `git push` instead of `git branch`: % git push origin --delete dll_soinit.c-stddef.h I plan on adding this to the Wiki in a few days. Any suggestions/concerns? Gerald

2 1

git pull --rebase upstream ?
by Gerald Pfeifer 16 Dec '22

16 Dec '22

These days I find myself spending more time wrestling with Git/Gitlab than it takes me to create and test a patch. So I am keenly interested to help improve https://wiki.winehq.org/Git_Wine_Tutorial#Creating_a_fork_on_Gitlab :-) Here is the first item: I ran # git clone git@gitlab.winehq.org:gerald/wine.git # git remote add upstream https://gitlab.winehq.org/wine/wine.git followed by # git pull --rebase upstream following https://wiki.winehq.org/Git_Wine_Tutorial#Creating_a_fork_on_Gitlab And there is where the instructions fail as follows: # git pull --rebase upstream From https://gitlab.winehq.org/wine/wine * [new branch] master -> upstream/master * [new branch] oldstable -> upstream/oldstable * [new branch] stable -> upstream/stable You asked to pull from the remote 'upstream', but did not specify a branch. Because this is not the default configured remote for your current branch, you must specify a branch on the command line. It appears the invocation should be shown as # git pull --rebase upstream master instead? Gerald PS: I'd volunteer to update the Wiki accordingly if confirmed, alas my wiki.winehq.org account (GeraldPfeifer) does not appear to exist any longer? And creating a new one is not possible?

2 2

Wayland driver - December 2022 update
by Alexandros Frantzis 16 Dec '22

16 Dec '22

Hi everyone! It's been some time since our last Wayland driver update ([1]), and, with the year coming to an end, I wanted to share information about the progress we made this year and discuss future steps. The focus in 2022 was on maturing the Wayland driver and keeping up to date with the Wine upstream internal changes. This involved, among other things, splitting the driver into a PE and Unix part, updating it for the latest internal driver APIs, and making preparations to support WoW64 (we are not there yet, but we are close). A significant improvement compared to last year is support for cross-process rendering, which is required by Chromium/CEF applications. Last year the driver was able to run Chrome with the "--in-process" command-line option. This year Chrome is supported without any special flags, fully GPU accelerated on both OpenGL and Vulkan! This was achieved by implementing what is effectively an internal off-screen swapchain in the driver's OpenGL and Vulkan integration code, along with a mechanism to send buffers to other processes for presentation when needed. This update also brings enhanced support for the linux-dmabuf v4 Wayland protocol (aka dmabuf-feedback), which allows compositors to dynamically send information about optimal formats and modifiers, e.g., depending on the surface presentation mode (fullscreen vs windowed). Our new internal OpenGL swapchain can handle such feedback directly, while for Vulkan we rely on the Wayland WSI to provide this functionality. This year we also made a lot of smaller scale fixes and enhancements, that in aggregate have greatly improved driver stability. These were a result of both testing we performed ourselves, and also of reports from people trying out the Wayland driver, for which we are very grateful. All the features listed in our previous update (multi-monitor, display mode changes, copy-paste, keymaps, relative mouse etc) have been further refined. One issue for which we haven't yet found a reasonable solution, is how to properly position the context/right-click menu in the standalone systray. The Wayland driver uses the Wayland protocol in a manner that, although in spec, exercises less well-trodden paths in compositor code. Throughout the year we have come across a few issues with compositors, which we have been working with upstreams to address. One issue that people should be aware of, in particular, manifests as improper relative mouse motion in first-person 3D games when using the Wayland driver with some compositors (e.g., see [2]). TL;DR of how to use the development branch: $ git clone -b wayland https://gitlab.collabora.com/alf/wine/ $ cd wine $ ./configure --with-wayland [--with-vulkan] $ make [-jN] $ DISPLAY= WAYLAND_DISPLAY=wayland-0 ./wine ... Especially note the use of 'DISPLAY=', which we use to opt in to the Wayland driver by disabling the higher priority X11 driver. Here is a video showing the latest version of the Wayland driver in action (note that in this video I am using Mutter from git main that includes the fix for the relative motion issues mentioned above): https://www.youtube.com/watch?v=lZ-MK72Kyp8 --- Next steps: Last year, due to the extensive ongoing internal rework in Wine (e.g., win32u), the decision was made to postpone the upstreaming of the Wayland driver until some amount of internal stability had been reached. My impression is that things are a lot more stable now, from the drivers' point of view at least. Is there any upcoming work that people feel would be severely hindered by the upstreaming of the Wayland driver? Ideally, I would like to start the upstreaming effort (which I expect will take some time) at some point early next year, after the codebase has been unfrozen. Does this sound reasonable? Thanks, Alexandros [1] https://www.winehq.org/pipermail/wine-devel/2021-December/203035.html [2] https://gitlab.gnome.org/GNOME/mutter/-/issues/2223

2 2

Why is vkd3d an extra projekt?
by Fabian Maurer 13 Dec '22

13 Dec '22

Hello, For a while now I'm curious, so I have to ask: Why is vkd3d an extra project? Is that because it is reusable as standalone library? Just curious, because it's the only library in Wine that is a separate project. Wouldn't it have made sense to develop it as part of Wine to reuse the wine infrastructure and always have the most recent code for dx12/shaders? Regards, Fabian Maurer

3 2

What does the "Override" button do in joy.cpl?
by Alex Henrie 13 Dec '22

13 Dec '22

While looking at the new messages to translate for Wine 8.0, I noticed several like this: "No user detected on slot #0, make sure your gamepad is plugged in, and not overriden for DInput in the Joysticks tab." Leaving aside the misspelling of "overridden" in English, I want to make sure that I translate this text intelligibly into Catalan. I assume that the message is related to the "Override" button in joy.cpl. What exactly does that button do? -Alex

2 2

Regarding Coverity
by Fabian Maurer 12 Dec '22

12 Dec '22

Hello, I'm sometimes working through the issues Coverity scan reported, and I come across a lot of issues that I consider false positives. I however am not 100% comfortable marking them as such, just in case I am wrong... What's the policy on that? Are those getting reviewed by other devs? Should I just mark them as false positives if I think they are? Regards, Fabian Maurer

2 1

Code freeze plans
by Alexandre Julliard 12 Dec '22

12 Dec '22

Folks, As you know, we are now in code freeze towards 8.0. This means that only reasonably small, targeted bug fixes can be accepted. As far as possible, please mention the bug number that the fix is for. We currently have 242 open regressions (cf. https://source.winehq.org/regressions) I'm hoping that we can release 8.0 with fewer open regressions than 7.0, which means we have to bring that number down to 150. All help is welcome! Fixes to the tests can always be accepted since they can't break apps, so this is also a good opportunity to fix some long-standing failures. The rc releases will be a bit more spread out than usual, because I'll be out during the Christmas break. My plan is to have rc2 on December 21, rc3 on January 6, and then resume weekly rc releases, with a final 8.0 towards the end of January. -- Alexandre Julliard julliard(a)winehq.org

1 0

Wine staging 8.0-rc1 release
by Alistair Leslie-Hughes 12 Dec '22

12 Dec '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 8.0-rc1 (473 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * winegstreamer: Implement MF_SD_LANGUAGE. 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

3 3

Wine Source build on native wchar_t 4 bytes
by Mahin Pandya 05 Dec '22

05 Dec '22

Hello All, We are trying to build Wine Source on Linux with native wchar_t size 4 bytes (instead of 2 bytes), is there any way it can be done? I started with doing following changes: diff --git a/tools/winapi/winapi_test b/tools/winapi/winapi_test index b9628e8..91daac3 100644 --- a/tools/winapi/winapi_test +++ b/tools/winapi/winapi_test @@ -206,7 +206,11 @@ sub _find_align_kind_size($) { $align = 2; $kind = "signed"; $size = 2; - } elsif (/^(?:char16_t|wchar_t|USHORT|WCHAR|WORD)$/) { + } elsif (/^(?:wchar_t|WCHAR)$/) { + $align = 4; + $kind = "unsigned"; + $size = 4; + } elsif (/^(?:char16_t|USHORT|WORD|WCHAR_nt)$/) { $align = 2; $kind = "unsigned"; $size = 2; Also started changing some of headers e.g. winnt.h - removed "typedef unsigned short WCHAR;" Any pointers/suggestion are welcome. Thanking you. regards, Mahin

6 11

Re: [PATCH 1/1] mstask: Don't assume a ONCE trigger is on the current day.
by Dmitry Timoshkov 02 Dec '22

02 Dec '22

Sven Baars <wine(a)gitlab.winehq.org> wrote: > - if (CompareFileTime(&begin_ft, &trigger_ft) <= 0 && CompareFileTime(&trigger_ft, &end_ft) < 0) > + if (CompareFileTime(&trigger_ft, &current_ft) >= 0) > { > if (!have_best_time || CompareFileTime(&trigger_ft, &best_ft) < 0) > { Removing the trigger end time check doesn't look right. -- Dmitry.

1 0

Using comdlg32 functions in shell32
by Alex Henrie 02 Dec '22

02 Dec '22

Hello, Does anyone know why shell32 uses LoadLibrary and GetProcAddress to get pointers to GetOpenFileName[AW] in comdlg32, rather than simply importing the library? https://gitlab.winehq.org/wine/wine/-/blob/wine-7.22/dlls/shell32/shellord.… https://gitlab.winehq.org/wine/wine/-/blob/wine-7.22/dlls/shell32/dialogs.c… I was about to rip this code out, but I want to make sure that it exists only by historical accident and no longer has a purpose. -Alex

2 1

Can we use Windows Kits idl files?
by James McDonnell 29 Nov '22

29 Nov '22

Are the Windows Kits SDK WinRT .idl files acceptable to read-rework inside the wine source? They are akin to header files, no? I asked on the irc but didn't get any reply. There was a follow up comment asking about ReactOS headers as well: > on the topic of headers, are we allowed to look at ReactOS NDK headerS > s/headerS/headers/ > they contain internal structure definitions only, nothing else Thank you, James

2 2

Wine staging 7.22 release
by Alistair Leslie-Hughes 27 Nov '22

27 Nov '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.22 (474 patches are applied to wine vanilla) The number is quiet lower compared to the previous version due to the disabling of the nvidia dll patchesets. Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Add support for FreeBSD style extended attributes. Added: * None Updated: * ntdll-DOS_Attributes 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Bug 52263 - Deadlock in dinput
by Fabian Maurer 20 Nov '22

20 Nov '22

Hello, you committed a fix for Bug 52263, but I think that only masks the issue, not really fixing it. Your fix is here: https://gitlab.winehq.org/wine/wine/-/commit/ 7e5eeecdfb5c90042945d9e84a3a9f8b2ed0036a I described what happens in https://bugs.winehq.org/show_bug.cgi?id=52314#c4 I think we can only time out in this wait, so this doesn't seem right. Could you please take a second look? Regards, Fabian Maurer

2 2

Cuda Applications on Wine - suggesting to merge wine-staging/patches/nvcuda-CUDA_Support patches into upstream wine.
by Alois Schlögl 16 Nov '22

16 Nov '22

I'd like suggesting to merge the 17 patches from wine-staging/patches/nvcuda-CUDA_Support patches into upstream wine for the following reasons: Currently Cuda applications for Windows do not run in native Wine. Such an application is Warpem (available for Windows only), and CUDA-Z for Windows. I assume there are other applications as well. This could be fixed by pulling in the 17 patches wine-staging/patches/nvcuda-CUDA_Support. Possible disadvantages: - build dependency to cuda - some distros might not want to have a build dependency on cuda.h That's the choice of the package manager, but this should be endorsed and recommended for the above reason. - run-time dependency on cuda wine does not have a runtime dependency on cuda (probably due to dynamic linking) e.g. cuda-z can be started under wine, and stops gracefully with a message the cuda is not available. - number of APIs to maintain is currently done anyway (by the wine-staging team) From a the perspective of some application, Cuda is part of the operating system should be provided by the platform (Wine in our case). Overall, it seems merging the nvcuda-CUDA_Support into upstream Wine are the right thing to do. Best regards, Alois

7 8

Wine 8.0 code freeze
by Alexandre Julliard 14 Nov '22

14 Nov '22

Folks, With the end of the year approaching, it will soon be time to start the code freeze towards Wine 8.0. My plan is to have another two development releases, and start code freeze with Wine 7.23, on December 9. So if there are things that you want in 8.0, you have another 4 weeks to get them upstreamed... -- Alexandre Julliard julliard(a)winehq.org

1 0

Wine staging 7.21 release
by Alistair Leslie-Hughes 13 Nov '22

13 Nov '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.21 (495 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * mshtml: Add IHTMLLocation::hash property's getter implementation. * uxtheme: Protect CloseThemeData() from invalid input. * user32/tests: Add some tests to see when MessageBox gains WS_EX_TOPMOST style. * user32: MessageBox should be topmost when MB_SYSTEMMODAL style is set. Added: * None Updated: * eventfd_synchronization * ntdll-Syscall_Emulation * ntdll-ForceBottomUpAlloc 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

3 2

Upcoming vkd3d 1.6 release.
by Henri Verbeet 10 Nov '22

10 Nov '22

Hi all, We'd like to release vkd3d 1.6 in about 4 weeks. As we're nearing that date, the vkd3d tree is going to become progressively frozen, starting today. Now is the time to test your applications for any regressions, review any API changes since vkd3d 1.5, review and improve the API documentation, and so on. The next release, vkd3d 1.7, is tentatively planned for late March next year. Regards, Henri

1 0

Winelib stack overflow
by Vitor Ramos 07 Nov '22

07 Nov '22

Hello, I am not sure if this is the appropriate channel but here we go. I am trying to port a windows c++ application using winelib and I found an issue while using some c++ STL containers. Here is a minimal example: # winelib.dll.so ```c++ #include <windows.h> #include <unordered_map> #include <string> extern "C" int f1(long z) { std::unordered_map<int, std::string> y; return 10; } spec file ```c++ 2 stdcall f1(long) ``` # Building winelib.dll.so winemaker --console --dll . winebuild --implib -E winedll.spec -o libwinedll.a winebuild --fake-module --dll -E winedll.spec -o winedll.dll make cp libwinedll.a winedll.dll.so /usr/local/lib/wine/x86_64-unix cp winedll.dll /home/$USER/.wine/drive_c/windows/system32 win64 app ```c++ #include <iostream> extern "C"{ int f1(long z); } int main(){ int ret = f1(2); std::cout << ret << std::endl; } ``` # Building win64 app winemaker . -iwinedll make # Running wine64 win64app.exe.so # Output 0110:err:virtual:virtual_setup_exception stack overflow 2128 bytes in thread 0110 addr 0x17008c804 stack 0x207b0 (0x20000-0x21000-0x120000) If I remove the "std::unordered_map<int, std::string> y" from the custom lib it runs normally. I suspect that wine uses too much of the stack to construct the object, but it's just a wild guess. Does anybody know what the issue could be? Is it possible to increase the stack size? Thanks.

3 4

TestBot News
by Francois Gouget 07 Nov '22

07 Nov '22

* The TestBot has a new Windows 11 VM. It's a new Windows version so it has almost 40 extra failures. To avoid false positives it's only going to be running WineTest until the new failures have been flagged. But you can already select it in the list of available VMs to run tests on it. * There are now two PCI-Passthrough configurations: - w11pro64_amd -> AMD RX6600 GPU - w11pro64_nv -> NVIDIA RTX3050 GPU These have a surprising number of extra failures, about 12, when fgtb-w10pro64-rx550 only has about 2 extra failures. So I will recheck the configuration of the new VMs (on the AMD side it may have the clipboard problem again, but then a number of failures appeared to be in the d3d tests). These are also only running WineTest for now so as to not cause false positives but you can select them in the list of available VMs. -- Francois Gouget <fgouget(a)codeweavers.com>

1 2

invalid read errno bug
by xantares09＠hotmail.com 01 Nov '22

01 Nov '22

Hello, I'm hoping to get more attention for this bug report that have not been confirmed yet: https://bugs.winehq.org/show_bug.cgi?id=53677 Everything should be provided to ease reproducing, Regards

1 0

Wine staging 7.20 release
by Alistair Leslie-Hughes 01 Nov '22

01 Nov '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.20 (504 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * sapi: Implement ISpObjectToken OpenKey * sapi: EnumTokens setup enumeration members * sapi: Implement ISpObjectTokenEnumBuilder Item * sapi: Add default voice registry key * sapi: Return dump object in ISpObjectTokenEnumBuilder Next Added: * None Updated: * nvcuda-CUDA_Support * mfplat-streaming-support 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: ntdll: Fix build on systems without ENODATA (was: [PATCH] ntdll: Complete error case in get_initial_environment)
by Erich E. Hoover 19 Oct '22

19 Oct '22

On Wed, Oct 19, 2022 at 3:05 PM Gerald Pfeifer <gerald(a)pfeifer.com> wrote: > > On Wed, 19 Oct 2022, Erich E. Hoover wrote: > >> https://gitlab.winehq.org/wine/wine/-/merge_requests/1097 > > It looks like this just got merged. Gerald, would you check and see > > if ENOATTR is defined on your system? > > I checked, and FreeBSD (12 and 14, so current and future versions) both > define ENOATTR guarded by #ifndef _POSIX_SOURCE, so generally available. > > > This commit removes the compile warning > > It actually was hard build error. Yes, sorry - I misspoke. > > but you're going to get a lot of unnecessary console warnings > > ("attribute does not exist" is not an error here). > > Is it possible Alexandre's adjusted version of my submission avoids this? > ... No. If the filesystem supports extended attributes (!ENOTSUP) then you will get an error if there aren't any xattr for the file. I suspect that we either want: === #ifdef ENODATA if (errno == ENODATA) return ret; #endif #ifdef ENOATTR if (errno == ENOATTR) return ret; #endif === Or we want to do something like this: === #ifndef ENOATTR #define ENOATTR ENODATA #endif === and then check against ENOATTR instead (little bit of research says that platforms that define both use ENOATTR in this case). Best, Erich

1 0

Re: [PATCH] ntdll: Complete error case in get_initial_environment
by Esme Povirk (any/all) 19 Oct '22

19 Oct '22

> That's more involved than the previous process, but I think I got it: > https://gitlab.winehq.org/gerald/wine/-/commit/2bdbfb583452a62c7d6acf7f416b… > > Is there anything else to do? I found the actual MR at https://gitlab.winehq.org/wine/wine/-/merge_requests/1097, and it looks right to me. Nothing else to do for now, hopefully someone will come along and review it. > PS: It shows the test-linux32 pipeline as failed, while the other two > succeeded; looks like a false positive to the, though. Yes, those errors have been showing up for every MR. -- https://my.pronouns.page/are/any

2 1

Wine staging 7.19 release
by Alistair Leslie-Hughes 17 Oct '22

17 Oct '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.19 (502 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * winegstreamer: Return S_OK from H264 decoder GetAttributes. * Implement retrieving DOS attributes in [fd_]get_file_info(). * ntdll: Implement storing DOS attributes in NtSetInformationFile. * ntdll: Implement storing DOS attributes in NtCreateFile. * sapi: Implement ISpObjectToken GetId * secur32: Input Parameter should be NULL on first call to InitializeSecurityContextW. * sapi: Implement ISpRegDataKey CreateKey * sapi: Implement ISpRegDataKey GetStringValue * ntdll: Improve stub of NtQueryEaFile. * winegstreamer: Reimplement AAC decoder using wg_transform. Added: * None Updated: * ntdll-DOS_Attributes * wined3d-bindless-texture * ntdll-Junction_Points 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: fixing some fixme code
by Jin-oh Kang 16 Oct '22

16 Oct '22

On Mon, Sep 12, 2022, 11:11 AM Owen Hogarth <gurenchan(a)gmail.com> wrote: > Hello guys, I am trying to get this program; R Trader Pro to work on Linux. > I installed winetricks and then I received some different errors. > > I would like to fix the problem but I would also like to avoid doing > unnecessary work, that's why I am asking on the development mailing list. > > Here's the new error log, is it possible to get the program working? > ... > An error occured while contacting the license server. > > Raised in : com.omnesys.omne.om.OMField > Method : OMsetData > Error : no data > Raised in : 31004 1 unknown host 20014 1 unknown addr > > Method : OMaddData > Error : create error > Please contact Omnesys Technologies Inc., at www.omnesys.com. > Please launch the application or the installer with the following command line (without angle brackets): export WINEPREFIX="$HOME/.wine-traderpro-test" # (or whatever wineprefix path you prefer) WINEDEBUG=+winsock wine <path to exe...> Also, please make sure you don't use native DLLs from winetricks when debugging or reporting a bug.

2 8

[PATCH 1/2] qedit/tests: Check the Sample Grabber's buffer during and after flushing.
by Gabriel Ivăncescu 04 Oct '22

04 Oct '22

Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> --- dlls/qedit/tests/samplegrabber.c | 234 +++++++++++++++++++++++++++++++ 1 file changed, 234 insertions(+) diff --git a/dlls/qedit/tests/samplegrabber.c b/dlls/qedit/tests/samplegrabber.c index 8e68e3e..e66180f 100644 --- a/dlls/qedit/tests/samplegrabber.c +++ b/dlls/qedit/tests/samplegrabber.c @@ -1036,6 +1036,239 @@ static void test_connect_pin(void) ok(!ref, "Got outstanding refcount %d.\n", ref); } +struct frame_thread_params +{ + IMemInputPin *sink; + IMediaSample *sample; + DWORD delay; +}; + +static DWORD WINAPI frame_thread(void *arg) +{ + struct frame_thread_params *params = arg; + HRESULT hr; + + if (params->delay) + { + if (winetest_debug > 1) trace("%04x: Sleeping %u ms.\n", GetCurrentThreadId(), params->delay); + Sleep(params->delay); + } + if (winetest_debug > 1) trace("%04x: Sending frame.\n", GetCurrentThreadId()); + hr = IMemInputPin_Receive(params->sink, params->sample); + if (winetest_debug > 1) trace("%04x: Returned %#x.\n", GetCurrentThreadId(), hr); + IMediaSample_Release(params->sample); + free(params); + return hr; +} + +static HANDLE send_frame_time(IMemInputPin *sink, REFERENCE_TIME start_time, unsigned char color, DWORD delay) +{ + struct frame_thread_params *params = malloc(sizeof(*params)); + IMemAllocator *allocator; + REFERENCE_TIME end_time; + IMediaSample *sample; + HANDLE thread; + HRESULT hr; + BYTE *data; + + hr = IMemInputPin_GetAllocator(sink, &allocator); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = IMemAllocator_GetBuffer(allocator, &sample, NULL, NULL, 0); + if (hr == VFW_E_NOT_COMMITTED) + { + IMemAllocator_Commit(allocator); + hr = IMemAllocator_GetBuffer(allocator, &sample, NULL, NULL, 0); + } + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = IMediaSample_GetPointer(sample, &data); + ok(hr == S_OK, "Got hr %#x.\n", hr); + memset(data, 0x55, 32 * 16 * 2); + + hr = IMediaSample_SetActualDataLength(sample, 32 * 16 * 2); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + start_time *= 10000000; + end_time = start_time + 10000000; + hr = IMediaSample_SetTime(sample, &start_time, &end_time); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + params->sink = sink; + params->sample = sample; + params->delay = delay; + thread = CreateThread(NULL, 0, frame_thread, params, 0, NULL); + + IMemAllocator_Release(allocator); + return thread; +} + +static HANDLE send_frame(IMemInputPin *sink, DWORD delay) +{ + return send_frame_time(sink, 0, 0x55, delay); /* purple */ +} + +static HRESULT join_thread_(int line, HANDLE thread) +{ + DWORD ret; + ok_(__FILE__, line)(!WaitForSingleObject(thread, 1000), "Wait failed.\n"); + GetExitCodeThread(thread, &ret); + CloseHandle(thread); + return ret; +} +#define join_thread(a) join_thread_(__LINE__, a) + +static void test_buffer_flush(void) +{ + AM_MEDIA_TYPE req_mt = + { + .majortype = MEDIATYPE_Video, + .subtype = MEDIASUBTYPE_RGB565, + .formattype = FORMAT_VideoInfo, + .bTemporalCompression = TRUE, + }; + LONG buf[(32 * 16 * 2) / sizeof(LONG)], size = sizeof(buf); + IPin *sink, *source, *renderer_pin; + struct testfilter testsource; + ISampleGrabber *grabber; + IMediaControl *control; + IFilterGraph2 *graph; + IMemInputPin *input; + IBaseFilter *filter; + OAFilterState state; + IMediaFilter *mf; + HANDLE thread; + DWORD ticks; + unsigned i; + HRESULT hr; + ULONG ref; + + testfilter_init(&testsource); + CoCreateInstance(&CLSID_FilterGraph, NULL, CLSCTX_INPROC_SERVER, + &IID_IFilterGraph2, (void **)&graph); + CoCreateInstance(&CLSID_NullRenderer, NULL, CLSCTX_INPROC_SERVER, + &IID_IBaseFilter, (void **)&filter); + IFilterGraph2_AddFilter(graph, filter, L"sink"); + IBaseFilter_FindPin(filter, L"In", &renderer_pin); + IBaseFilter_Release(filter); + + filter = create_sample_grabber(); + IFilterGraph2_AddFilter(graph, &testsource.filter.IBaseFilter_iface, L"source"); + IFilterGraph2_AddFilter(graph, filter, L"sample grabber"); + IBaseFilter_FindPin(filter, L"In", &sink); + IBaseFilter_FindPin(filter, L"Out", &source); + IBaseFilter_QueryInterface(filter, &IID_ISampleGrabber, (void **)&grabber); + IFilterGraph2_QueryInterface(graph, &IID_IMediaControl, (void **)&control); + IPin_QueryInterface(sink, &IID_IMemInputPin, (void **)&input); + + ISampleGrabber_SetMediaType(grabber, &req_mt); + ISampleGrabber_SetBufferSamples(grabber, TRUE); + + testsource.sink_mt = &req_mt; + hr = IFilterGraph2_ConnectDirect(graph, &testsource.source.pin.IPin_iface, sink, &req_mt); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = IFilterGraph2_ConnectDirect(graph, source, renderer_pin, &req_mt); + ok(hr == S_OK, "Got hr %#x.\n", hr); + IPin_Release(renderer_pin); + + IFilterGraph2_QueryInterface(graph, &IID_IMediaFilter, (void **)&mf); + IMediaFilter_SetSyncSource(mf, NULL); + IMediaFilter_Release(mf); + + hr = IMemInputPin_ReceiveCanBlock(input); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ok(hr == VFW_E_WRONG_STATE, "Got hr %#x.\n", hr); + + hr = IMediaControl_Pause(control); + ok(hr == S_FALSE, "Got hr %#x.\n", hr); + hr = IMediaControl_GetState(control, 0, &state); + ok(hr == VFW_S_STATE_INTERMEDIATE, "Got hr %#x.\n", hr); + + thread = send_frame(input, 0); + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(WaitForSingleObject(thread, 100) == WAIT_TIMEOUT, "Thread should block in Receive().\n"); + + for (i = 0; i < 3; i++) + { + ticks = GetTickCount(); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ticks = GetTickCount() - ticks; + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(ticks < 100, "Got %u ticks.\n", ticks); + ok(size == sizeof(buf), "Got size %d.\n", size); + } + + hr = IMediaControl_Stop(control); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = join_thread(thread); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(state == State_Stopped, "Got state %d.\n", state); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = IMediaControl_Pause(control); + ok(hr == S_FALSE, "Got hr %#x.\n", hr); + hr = IMediaControl_GetState(control, 0, &state); + ok(hr == VFW_S_STATE_INTERMEDIATE, "Got hr %#x.\n", hr); + + thread = send_frame(input, 0); + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(WaitForSingleObject(thread, 100) == WAIT_TIMEOUT, "Thread should block in Receive().\n"); + + for (i = 0; i < 3; i++) + { + ticks = GetTickCount(); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ticks = GetTickCount() - ticks; + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(ticks < 100, "Got %u ticks.\n", ticks); + ok(size == sizeof(buf), "Got size %d.\n", size); + } + + IPin_BeginFlush(sink); + hr = join_thread(thread); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ok(hr == S_OK, "Got hr %#x.\n", hr); + IPin_EndFlush(sink); + + hr = IMediaControl_GetState(control, 0, &state); + todo_wine ok(hr == VFW_S_STATE_INTERMEDIATE, "Got hr %#x.\n", hr); + + ticks = GetTickCount(); + thread = send_frame(input, 150); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ticks = GetTickCount() - ticks; + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(ticks < 100, "Got %u ticks.\n", ticks); + ok(size == sizeof(buf), "Got size %d.\n", size); + + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = IMediaControl_Stop(control); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = join_thread(thread); + todo_wine ok(hr == S_OK, "Got hr %#x.\n", hr); + + IPin_Release(sink); + IPin_Release(source); + IMemInputPin_Release(input); + IMediaControl_Release(control); + ref = IFilterGraph2_Release(graph); + ok(!ref, "Got outstanding refcount %d.\n", ref); + ISampleGrabber_Release(grabber); + ref = IBaseFilter_Release(filter); + ok(!ref, "Got outstanding refcount %d.\n", ref); + ref = IBaseFilter_Release(&testsource.filter.IBaseFilter_iface); + ok(!ref, "Got outstanding refcount %d.\n", ref); +} + START_TEST(samplegrabber) { IBaseFilter *filter; @@ -1059,6 +1292,7 @@ START_TEST(samplegrabber) test_aggregation(); test_media_types(); test_connect_pin(); + test_buffer_flush(); CoUninitialize(); } -- 2.21.0

5 7

WineConf - starting next week!
by Jeremy White 29 Sep '22

29 Sep '22

Hi folks, We are excited to welcome you in person to the 2022 Wine Conference, held in conjunction with the X.org developers conference (XDC) and the FOSS XR conference. The XDC conference will start on Tuesday morning, October 4th. The program is here: https://indico.freedesktop.org/event/2/timetable/#all.detailed The official events start at 8:30 am, but we will have coffee and pastries available from 7:30 on Tuesday and 8 on Wednesday and Thursday. WineConf proper will start on Wednesday morning, October 5th, with Alexandre's keynote. We expect everyone attending to be vaccinated and to be respectful of people that are trying to avoid catching COVID. Masks are mandatory, except when presenting or eating. The plan is to gather at Brit's Pub, both Monday and Tuesday in the late afternoon to welcome arrivals. We’ll try to have a table with some sort of a sign, and folks can connect, have a drink, and then perhaps group up to explore alternate food. Note that if the weather is nice, we may be up on the roof, so explore far to find us. We will be on the Minneapolis campus of St. Thomas, which is a mildly confusing campus. We have given instructions and a picture to guide you here: https://indico.freedesktop.org/event/2/page/10-attending-xdc-wineconf-foss-… We are working on the remote experience, and expect to have streaming of all events available. The above page will have those details just as soon as they are finalized. We have a page of instructions for folks that will be presenting: https://indico.freedesktop.org/event/2/page/18-speaker-instructions We are also excited to announce the happy hour taking place on Wednesday, from 6:00 pm until 8:00 pm. The hope is that all three projects can mingle and socialize and enjoy the return of in person meetings. We will again use a Matrix chat room just for the conference. Matrix has a variety of apps, and Element, the default one is easy to configure on many devices, including mobile phones. The link to that channel is here: https://matrix.to/#/#xdc-wineconf-fossxr-2022:matrix.org We find the chat channel a good place to learn what restaurants and bars are chosen, and just a good way to track the social aspects of the conference. We look forward to seeing you next week! Cheers, Jeremy

1 0

Winelib portability on USB booted system
by Brent Burkholder 29 Sep '22

29 Sep '22

We had originally tried a software port using winelib 5, and it was just a no-go in functionality. Wine 7 is working a LOT better for what we're doing (Windows GUI with ability to do low level Linux hooks), so thank you all for all of the hard work! Unfortunately, even though the software is running great on our development machine, when I try to run it on another system (configured USB boot, should have the same version of wine, etc) it doesn't run at all with pretty much no feedback. Can anyone help me understand why, or what I need to be looking for? Both systems are starting with the same script (I've done a lot of variations, directly launching myself, and it doesn't seem to matter.) #!/bin/bash sudo env "PATH=/opt/wine-devel/bin:$PATH" /opt/wine-devel/bin/wine xerase.exe.so The compiling system starts right up. The USB boot system that I'm trying to run it on gives me 0078:fixme:wineusb:add_unix_device Interface 1 has 2 alternate settings; using the first one. Wine: failed to start L"F:\\home\\test\.wine\\drive_c\\XERASxlnx\\xerase.exe.so" Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. If I do the command directly instead of through a script I get exactly the same thing. If I cut out the env path stuff (1), or keep the path but call just wine (2), or just call wine (bashrc has the path now) same results 1. sudo /opt/wine-devel/bin/wine xerase.exe.so 2. sudo env "PATH=/opt/wine-devel/bin:$PATH" wine xerase.exe.so 3. sudo wine xerase.exe.so 4. sudo wine /home/test/.wine/drive_c/XERASxlnx/xerase.exe.so 0078:fixme:wineusb:add_unix_device Interface 1 has 2 alternate settings; using the first one. Wine: failed to start L"F:\\home\\test\.wine\\drive_c\\XERASxlnx\\xerase.exe.so" Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found. So... observations... 1. Not sure where F: is coming from? C: I might understand (though frankly, I'd just as soon the program realize we're using the unix file structure, not any virtualized windows stuff for what we're doing) When I look at .wine/dosdevices on both systems... Build/working system: z: -> / c: -> ../drive_c <com devices> . .. Not working USB booted system: z: -> / c: -> ../drive_c d:: -> /dev/sda1 g:: -> /dev/sda f:: -> /dev/sd5 e:: -> /dev/sda2 <com devices> d: -> /boot/efi f: -> / . .. Any suggestions in changes to compilation or environmental variables to get wine to start running it? I guess I could delete d::, g::, f::, e::, d:, and f: and see if that makes a difference but figured I'd ask the question first Brent Burkholder Extreme Protocol Solutions bburk(a)extremeprotocol.com<mailto:bburk@extremeprotocol.com>

2 2

wine-7.0.1-rc1 Available
by Michael Stefaniuc 28 Sep '22

28 Sep '22

Hello, I have pushed wine-7.0.1-rc1 (217323fff7da7f318a30348b4665ace55d04c50b) to https://github.com/mstefani/wine-stable/tree/stable https://people.redhat.com/mstefani/wine/stable/ And created the draft merge request https://gitlab.winehq.org/wine/wine/-/merge_requests/955 Bugs and most other fixes are from the 7.1 to 7.8 era. Previous x.0.1 releases would include only stuff from x.1 to x.4 or x.5 devel versions to fill the "budget" of about 100 cherry picks. Also this is lowest amount of bugs fixed since 1.8.1. The "use long" commits were a major nuisance so I might have missed bugs due to the long patch dependency chains. If your favorite bug is missing please let me know. The rest of the commits picked are small and found by keywords in the commit message. The longer commit messages help here. There are a bunch of "newer" (> 7.8) commits and those are mostly there to fix the currently "broken in 7.0 too" tests. The usual plan is to wait for feedback for 7-10 days before the real 7.0.1 is released. There will be definitely a -rc2 as I need to cherry pick or backport some of the gitlab related commits. What's new in this release: - Various bug fixes - Translation updates ---------------------------------------------------------------- Bugs fixed in 7.0.1 (total 31): 12732 Nota Bene crashes on install 44202 undname.c fails to parse symbols with rvalue-reference semantics '&&' 45916 x64dbg fails to load debuggee, needs ThreadScheduler_ScheduleTask 50352 Maximum sockets per process is set very low 50370 Gothic 1 doesn't start correctly when screen resolution of the game matches display resolution 50433 'MsiBreak' custom action debugging aid should use custom action's name from 'CustomAction' table (currently uses 'Target' field) 50869 Killing Wine process in Wine 6.5 doesn't terminate the application because of the new use of start.exe 51163 WinOffice Pro 5.3 stops after splashscreen, needs WMI class SoftwareLicensingProduct 51619 advapi32:registry fails in Wine because French & German timezone name translations are too long 51900 regression: REAPER scrollbars flash between themed and non-themed 52163 postgresql-9.3 installer expects scrrun:filesys_GetTempName to return filename with TMP suffix 52298 Opening PPT with Freeoffice Presentations crashes on unimplemented function ole32.dll.OleConvertIStorageToOLESTREAMEx 52426 BCryptSignHash mishandles empty arguments 52434 Light Blue theme has rendering errors in tree views 52436 In Light Blue theme, checkable toggle buttons (BS_AUTOCHECKBOX) look unchecked when hovered 52446 Normal dlls with native subsystem id are no longer processed when importing system dlls with uppercase names 52476 QuickLOAD (VB5 app) input value is changed by factor 10 52494 shell32 progman_dde tests crash if run immediately after prefix creation 52510 alt:V mod for Grand Theft Auto V fails due to missing concrt140._Byte_reverse_table@details@Concurrency@@3QBEB 52562 advapi32:registry fails in Wine because some French timezone name translations are too long 52581 Internet MIDI crashes with Light Blue theme enabled 52583 ApiSetView does not display export ordinals correctly 52616 SteelSeries GG installer crashes on unimplemented function setupapi.dll.SetupQueryInfVersionInformationW 52618 32-bit EXEs do not launch from build dir on macOS 10.14 in WOW64 52626 MahjongSoul needs unimplemented function combase.dll.RoSetErrorReportingFlags 52667 DTS Master Audio Suite can't select save file location when wine's "Light" theme is used 52679 Anno 1602 / 1602 A.D. graphics too dark / black 52704 FreeHand 9 demo: invalid handle exception (0xc0000008) when attaching uxtheme.dll 52787 Invalid function prototype for "RegisterUserApiHook" when compiling for C++ 52953 GuiPy crashes on unimplemented function xmllite.dll.CreateXmlReaderInputWithEncodingCodePage 53430 urlmon:url fails due to unexpected redirection ---------------------------------------------------------------- Changes since 7.0: Alex Henrie (14): explorer: Only try to destroy the IShellWindows object if it exists. tzres: Inform translators of 31-character limit. po: Update Catalan translation. msi: Fix memory leak in get_fusion_filename (Coverity). winhttp: Fix memory leak on error path in WinHttpCrackUrl (Coverity). adsldp: Fix memory leak on error path in search_ExecuteSearch (Coverity). conhost: Fix memory leak on error path in create_screen_buffer (cppcheck). dbghelp: Fix memory leak on error path in dwarf2_read_range (cppcheck). ws2_32: Fix memory leak on error path in get_local_ips (cppcheck). ws2_32: Fix memory leaks on error paths in unix_gethostby* (scan-build). sane: Fix memory leak in create_item (Coverity). winspool: Fix memory leaks on error path in DeviceCapabilitiesA (Coverity). shell32: Fix sizeof argument in DoPaste (Coverity). mciwave: Fix bad free in MCI_SendCommandAsync (Coverity). Alexandre Julliard (9): user.exe: Make sure that the thunk selector doesn't get freed. makefiles: Disable printf format warnings for non-PE msvcrt modules. README: Mention Gitlab. kernel32/tests: Fix affinity test when there are too many CPUs. ntdll/tests: Fix affinity test when there are too many CPUs. secur32/tests: Update for new WineHQ certificate. urlmon/tests: Run tests against the gitlab server to avoid redirects. webservices/tests: Mark tests that fail on 64-bit as todo. wininet/tests: Update WineHQ certificate. Alistair Leslie-Hughes (1): msado15: Return valid object in Recordset::Clone. Andrey Gusev (1): d3d11: Implement the ID3DUserDefinedAnnotation interface. Aurimas Fišeras (1): po: Update Lithuanian translation. Bastien Orivel (1): ws2_32: Fix setsockopt(TCP_NODELAY) when optlen is less than 4. Ben Shefte (1): ntdll: Use case insensitive comparison in is_import_dll_system(). Bhavesh Davda (1): wined3d: Add GPU information for NVIDIA Ampere A10 and AMD Radeon Pro V620 GPUs. Brandon Moore (1): msadpm: Stop decoding instead of crashing for invalid adpcm data. Brendan Shanks (1): makefiles: On macOS, use @rpath instead of @loader_path when building Unix libs. David Kahurani (1): oleaut32: Do not skip the first decimal digit in VarParseNumFromStr(). Dmitry Timoshkov (2): ieframe: Clear a being invalidated history entry. ieframe: Initialize new history log entry. Eric Pouech (3): start: Wrap child inside a job so it gets killed when start.exe terminates. include/msvcrt: Redefine towlower* & towupper* with wint_t types. msacm32: Use extended structure definition for driver configuration. Fabian Maurer (4): printui: Use LocalFree for memory allocated by LocalAlloc (Coverity). mfplay: Prevent usage of uninitialized pointer in error case (Coverity). mfplat: Prevent use after free (Coverity). shell32: Prevent user after free in error case (Coverity). Floris Renaud (1): po: Update Dutch Translation. François Gouget (8): po: Fix the French translation of 'code page'. po: Fix backslash duplication in a French translation. po: Remove a space before a linefeed in the French translation. po: Remove spaces before linefeeds in the Spanish translation. po: Remove a space before a linefeed in the Chinese translation. po: Fix an accelerator shortcut in the Norwegian Bokmål translation. inetmib1: Avoid overflows in IPv4 address comparisons. inetmib1: Fix the IPv4 address network order for comparisons. Gabriel Ivăncescu (3): ddraw: Use WINED3D_SWAPCHAIN_NO_WINDOW_CHANGES only if window is not in foreground. jscript: Handle NULL return pointers in all constructors. mshtml: Fix leak on failure in return_nsstr. Gerald Pfeifer (1): iphlpapi: Zero-init prefix_len to avoid a compiler warning. Gijs Vermeulen (1): setupapi: Add SetupQueryInfVersionInformationA/W stub. Giovanni Mascellani (3): winegstreamer: Do not block forever if EOS races with command queue. mfplat: Avoid a race condition when releasing a tracked sample. mfmediaengine: Fix a memory leak. Hans Leidekker (1): msi: Use custom action name for MsiBreak handling. Henri Verbeet (2): d3d11/tests: Add some tests for ID3DUserDefinedAnnotation. wined3d: Add GPU information for NVIDIA Tesla T4. Kevin Puetz (1): winegcc: --out-implib needs to propagate -m32/-m64 to winebuild. Lauri Kenttä (2): po: Update Finnish translation. readme: Update Finnish translation. Louis Lenders (2): wbemprox: Add some properties of SoftwareLicensingProduct class. ole32: Add stub for OleConvertIStorageToOLESTREAMEx. Martin Storsjö (1): ntdll: Zero-initialize the syscall_frame used for starting threads on ARM/ARM64. Matteo Bruni (1): combase: Add RoSetErrorReportingFlags() stub. Michael Stefaniuc (1): tools: Get the ANNOUNCE bug list from the stable-notes git notes. Mohamad Al-Jaf (1): hid: Implement HidD_GetPhysicalDescriptor. Nikolay Sivov (4): comctl32/listview: Initialize subitem text buffer before drawing each subitem. uxtheme: Fix double free on registry key handle. xmllite/reader: Implement CreateXmlReaderInputWithEncodingCodePage(). evr/sample: Avoid a race condition when releasing a tracked sample. Paul Gofman (1): concrt140: Add ?_Byte_reverse_table@details@Concurrency@@3QBEB data export. Piotr Caban (2): ucrtbase: Add support for r-value demangling in unDName. msvcr100: Improve ThreadScheduler_ScheduleTask_loc stub. Piotr Kleski (1): bcrypt: Return BCryptSignHash len when only output is NULL. Robert Wilhelm (2): scrrun: Add test for GetTempName. scrrun: Generate temp name with tmp suffix. Rémi Bernon (1): mf: Handle MESourceSeeked and MEStreamSeeked state change events. Santino Mazza (2): ncrypt/tests: Test key import of an rsa key. ncrypt: Make NCryptOpenStorageProvider return a valid stub pointer. Saulius Krasuckas (1): ntdll: Check __WINE_PE_BUILD instead of compiler macros. Zebediah Figura (12): ws2_32/tests: Add tests for WSAStartup(). ws2_32: Always fill the WSADATA structure in WSAStartup(). ws2_32: Cap the negotiated winsock version to 1.1 or 2.2. ws2_32: Return 32767 or 0 in the iMaxSockets field. ws2_32: Return 65467 or 0 in the iMaxUdpDg field. ws2_32: Return WSAEFAULT instead of WSAEINVAL from WSAStartup() if "data" is NULL. configure: Fix the check for CAPI support. d3dx9: Don't mark annotation variables as dirty. winegstreamer: Release stream_cs on error in stream_thread(). setupapi: Avoid leaking subKey in SETUPDI_AddDeviceInterfaces(). server: Allocate enough space for the backslash in dup_nt_name() (Valgrind). tiff: Explictly link to zlib. Zhiyi Zhang (12): user32/tests: Test painting standard scroll bars in hovered state. user32: Draw standard scroll bars in hovered state only when they were previously painted by DefWinProc(). comctl32/button: Use pressed state when a pushlike checkbox or radio button is checked and hovered. comctl32/treeview: Do not draw client edge without WS_EX_CLIENTEDGE. light.msstyles: Do not use transparent treeview parts. uxtheme/tests: Add IsThemePartDefined() tests. uxtheme: Search parts of any state in IsThemePartDefined(). light.msstyles: Add Menu stub class. user32/tests: Test NUMCOLORS for display DCs. win32u: Return -1 for NUMCOLORS with 8-bit display DCs. include: Avoid a C++ keyword for RegisterUserApiHook(). light.msstyles: Use stretch sizing type for scroll bar arrow button background. -- Michael Stefaniuc mstefani(a)winehq.org

1 0

Wine staging 7.18 release
by Alistair Leslie-Hughes 23 Sep '22

23 Sep '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.18 (514 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ws2_32: Return a valid value for WSAIoctl SIO_IDEAL_SEND_BACKLOG_QUERY. * dwrite: Test IDWriteTextFormat with nonexistent font. * dwrite: Use MapCharacters for non-visual characters. * dwrite: Use MapCharacters for dummy line metrics. Added: * None Updated: * server-unix_name * ntdll-Junction_Points 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

What macOS SDK is being tested against on gitlab?
by Dean Greer 23 Sep '22

23 Sep '22

Hi everyone, I’d just tried to build the current git and winemac.drv is failing building on macOS Monterey with the latest 12.3 SDK so I’m assuming the gitlab test is using an older macOS SDK?

3 10

How to test out wines WoW64?
by Dean Greer 23 Sep '22

23 Sep '22

Hi everyone, Since there now seems to be support within winex11.drv and winemac.drv what patches are now required to make use of the WoW64 work? I'd like to have this enabled within the macOS packages as soon as possible even if that means possibly carrying some patches locally for a while, ideally having a way to build the contents of i386-windows without needing to build i386-unix.

2 3

[vkd3d] Handling object components within the HLSL compiler.
by Francisco Casas 20 Sep '22

20 Sep '22

Hello, I write this update on what I am working on, because I think it introduces some architectural changes that may be good to discuss, or at least mention. Sorry if this text is a bit dense, I hope to send all this as a merge request in a couple of days from now. Albeit we may want to avoid merging before the code freeze ends. More than a week ago, I started trying to implement SM1 resource loads. For this, in particular, it is necessary to infer each sampler's dimensions from usage (a use in a tex2D implies that the sampler is 2D, if not previously declared as such). This gets complicated when there are arrays of samplers, because each sampler component can have a different dimension, and yet being part of the same variable. For solving this I tried introducing a field to allow us to store data for each component within hlsl_ir_var. But this turned to be a complicated solution. As now, we lost the component information in the derefs once we start working with register offsets. I also wanted to have per-component data because I realized that, in general, we are not handling object components properly when they are part of a larger array/struct. But then I thought on an alternative solution: adding a compiler pass to promote each object component within a large variable to a new standalone variable, and prepend a store from this standalone variable to the the original path of the component within the large variable; relying on copy-prop and dce so that all references that refer to these components end up pointing to the new standalone variable. This allows us to use the fields of the hlsl_ir_var (in particular, the register allocation) for each object component, which solves the problem. While that strategy works, I then realized that we cannot use it when targeting SM1 profiles, because we wouldn't be replicating the CTAB (which doesn't introduce a new variable for each component in multi-dimensional object arrays, just increases its register size). SM4 on the other hand seems to do this, separating each sampler and texture as its own variable in the RDEF block. My conclusion then, is that it is a good idea to separate each object component into its own variable in SM4 (as long they are named with the correct subscripts, like "foo.tex[3]"). And while we can't do that in SM1, the good news is that SM1 doesn't allow objects as components of larger types except within (possible multi-dimensional) arrays. Samplers and Textures cannot be components of structs within SM1 profiles, so we only have to support those cases in hlsl_sm1.c. This approach also has the benefit that now, all the component register allocation information should be representable using the fields in the hlsl_ir_var struct and the register size data within hlsl_type [1], since each variable should only care about a single register type now. Storing register allocation data component-wise should not be necessary. So I am implementing a series of patches to ensure that: * When targeting SM4 profiles, all object components are separated into a sole variable. * When targeting SM1 profiles, it is not allowed to declare objects as components of structs; so they will either be a sole variable, or belong to either a (possibly multi-dimensional) array of elements of the same type, as declared within the shader. * SM1 resource loads work. My plan for this series, in terms of patches is: * Parse the tex3D() intrinsic. (already made by zf) * Parse the tex2D() intrinsic. (already made by zf) * Validate that object are not components of structs in SM1. * Properly allocate registers for object arrays for SM1. * Infer sampler register dimensions and write declarations in SM1. * Write resource loads in SM1. * Separate objects as standalone variables in SM4. * Lower combined samplers to separate sampler and texture objects for SM4. (already made by zf) * Lower separate sampler and texture objects to combined samplers for SM1. (already made by zf) It remains to check if object arrays are handled properly in the last two [2], or modify these patches accordingly. Best regards, Francisco. --- [1] I know we intend to remove this field later, when we move register allocation to each sm*_write.c, but I think we probably want to replace those precomputed register offset fields with equivalent SM-specific functions that retrieve the register offset for each component. [2] In SM1 profiles, when there are texture arrays and they are used together with samplers, only one variable is created (not one for each pair of components). This is allowed: ``` Texture2D tex[3][2]; sampler sam; float4 main() : SV_TARGET { return tex[0][1].Sample(sam, float2(1, 2)) + tex[1][0].Sample(sam, float2(1, 2)); } ``` This is allowed (but "not yet implemented" in fxc 9 and 10) ``` Texture2D tex; sampler sam[2][3]; float4 main() : SV_TARGET { return tex.Sample(sam[0][2], float2(1, 2)) + tex.Sample(sam[1][0], float2(1, 2)); } ``` This is not allowed: ``` Texture2D tex[3]; sampler sam[4]; float4 PSMain() : SV_TARGET { return tex[1].Sample(sam[1], float2(1, 2)) + tex[2].Sample(sam[0], float2(1, 2)); } ``` gives: ``` error X4581: Cannot use texture arrays on DX9 targets with multiple samplers. ```

2 5

Request for new 7.0 stable release
by Nick Sarnie 18 Sep '22

18 Sep '22

Hi, I'm part of the Wine packaging team for Gentoo. We noticed that the 7.0.x stable branch is currently at 7.0, and the 6.0.x stable branch has had some maintenance releases after the release of 7.0, so there have been some bug fixes backported to 6.0.x (e.g. 6.0.4) that are not available in the 7.0 stable release. Would the Wine team be willing to do a maintenance release for the 7.0.x branch to include these bug fixes (and possibly others)? If not, would you please explain the rationale behind that decision and the intended stable branch release cadence? Thanks for your time, Sarnex

2 2

WineHQ.org Downtime
by Jeremy Newman 12 Sep '22

12 Sep '22

The WineHQ.org server will be down for maintenance and upgrades starting today 2022-09-12 at 13:00 CDT (GMT-5) This downtime will be a minimum of 30 minutes, but could take longer depending on any issues that arise. This will take offline all mailing lists and websites during the maintenance timeframe. After the maintenance is complete, various services may take longer to come back online or may exhibit unexpected behavior. We will be fixing these issues are quickly as we can. Thanks for your patience and I will reply back to this thread if anything changes. I will also be online on the #winehackers IRC room. -N

1 1

Re: fixing some fixme code
by Jin-oh Kang 12 Sep '22

12 Sep '22

Forwarding to wine-devel. Please remember to use the "reply all" button next time. Thank you! On Mon, Sep 12, 2022, 11:11 AM Owen Hogarth <gurenchan(a)gmail.com> wrote: > Hello guys, I am trying to get this program; R Trader Pro to work on Linux. > I installed winetricks and then I received some different errors. > > I would like to fix the problem but I would also like to avoid doing > unnecessary work, that's why I am asking on the development mailing list. > > Here's the new error log, is it possible to get the program working? > 017c:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0174:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0174:fixme:file:NtLockFile I/O completion on lock not implemented yet > 0174:fixme:ntdll:NtQuerySystemInformation info_class > SYSTEM_PERFORMANCE_INFORMATION > 0194:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:imm:ImeSetActiveContext (0x2ca590, 1): stub > 0174:fixme:imm:ImmReleaseContext (0004006E, 002CA590): stub > 017c:fixme:imm:ImeSetActiveContext (0x3c780, 0): stub > 017c:fixme:imm:ImmReleaseContext (0000000000020082, 000000000003C780): stub > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:err:richedit:ReadStyleSheet skipping optional destination > 0174:err:richedit:ReadStyleSheet skipping optional destination > 0174:err:richedit:ReadStyleSheet skipping optional destination > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0174:fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, > advertised shortcut > 0174:fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, > advertised shortcut > 0174:fixme:msi:ITERATE_CreateShortcuts poorly handled shortcut format, > advertised shortcut > 01e8:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 01f0:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 01e0:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 01f8:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > regsvr32: Successfully registered DLL 'C:\Program Files > (x86)\Rithmic\Rithmic Trader Pro\StockChartX.ocx' > 0174:fixme:msi:internal_ui_handler internal UI not implemented for message > 0x0b000000 (UI level = 5) > 0174:fixme:msi:internal_ui_handler internal UI not implemented for message > 0x0b000000 (UI level = 5) > 0174:fixme:wincodecs:jpeg_decoder_get_metadata_blocks stub > 0200:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling > back to RandR 1.0. Please consider using the Nouveau driver instead. > 0200:fixme:mscoree:parse_supported_runtime > sku=L".NETFramework,Version=v4.5.2" not implemented > 0200:fixme:mscoree:parse_supported_runtime > sku=L".NETFramework,Version=v4.5.2" not implemented > 0200:fixme:ntdll:NtQuerySystemInformation info_class > SYSTEM_PERFORMANCE_INFORMATION > 0200:fixme:nls:GetFileMUIPath stub: 0x10, > L"C:\\windows\\system32\\tzres.dll", (null), 0032EE98, 00DAA728, 0032EE9C, > 0032EE90 > 0200:fixme:nls:GetFileMUIPath stub: 0x10, > L"C:\\windows\\system32\\tzres.dll", (null), 0032EE98, 00DAA728, 0032EE9C, > 0032EE90 > 0200:fixme:nls:GetFileMUIPath stub: 0x10, > L"C:\\windows\\system32\\tzres.dll", (null), 0032EE98, 00DAA728, 0032EE9C, > 0032EE90 > 0200:fixme:imm:ImeSetActiveContext (0xdc41c0, 1): stub > 0200:fixme:imm:ImmReleaseContext (00030080, 00DC41C0): stub > 0200:fixme:winsock:errno_from_unix unknown error: Device or resource busy > 0200:err:winediag:getaddrinfo Failed to resolve your host name IP > 0218:fixme:wbemprox:wbem_locator_ConnectServer authentication not supported > 0218:fixme:wbemprox:wbem_locator_ConnectServer specific locale not > supported > 0218:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags > 021c:fixme:wbemprox:wbem_locator_ConnectServer authentication not supported > 021c:fixme:wbemprox:wbem_locator_ConnectServer specific locale not > supported > 021c:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags > wine: Read access denied for device L"\\??\\Z:\\", FS volume label and > serial are not available. > 0200:fixme:winsock:errno_from_unix unknown error: Device or resource busy > 0200:err:winediag:getaddrinfo Failed to resolve your host name IP > 0200:fixme:winsock:errno_from_unix unknown error: Device or resource busy > 0200:err:winediag:getaddrinfo Failed to resolve your host name IP > An error occured while contacting the license server. > > Raised in : com.omnesys.omne.om.OMField > Method : OMsetData > Error : no data > Raised in : 31004 1 unknown host 20014 1 unknown addr > > Method : OMaddData > Error : create error > Please contact Omnesys Technologies Inc., at www.omnesys.com. > > On Mon, Sep 12, 2022 at 8:51 AM Jin-oh Kang <jinoh.kang.kr(a)gmail.com> > wrote: > >> On Mon, Sep 12, 2022, 9:46 AM Zebediah Figura <zfigura(a)codeweavers.com> >> wrote: >> >>> On 9/11/22 19:38, Jin-oh Kang wrote: >>> >> and secondly because it's actually quite hard if not >>> >> impossible to implement (POSIX has no way to wait for a mandatory >>> lock, >>> >> for instance). >>> >> >>> > >>> > We don't use POSIX locks to implement file locks; they are emulated >>> > entirely in the server, which I guess is specifically designed to avoid >>> > that problem with POSIX file lock semantics. Thus, this won't be *that* >>> > hard to implement; nonetheless, asynchronous I/O is not really easy to >>> > implement in general, especially for those new to wine codebase. >>> >>> I don't see where you're getting that; we do indeed use POSIX locks. See >>> set_unix_lock() in server/fd.c. >> >> >> I stand corrected. >> >> There's no poll() for file locks, so it would have to busy-wait anyway. >> >> I did incorrectly use the term >>> "mandatory", though; we don't set mandatory locks on a file. >>> >>

1 0

fixing some fixme code
by Owen Hogarth 12 Sep '22

12 Sep '22

Hello, I tried to run an application and saw that there are a few unimplemented features, such as: 00d0:fixme:file:NtLockFile I/O completion on lock not implemented yet I was reading the developers guide and wanted to say hello to the mailing list.

3 4

Wine staging 7.17 release
by Alistair Leslie-Hughes 10 Sep '22

10 Sep '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.17 (529 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * ntdll: Add support for FileFsFullSizeInformation class in NtQueryVolumeInformationFile(try 2) 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. * Suggest patches to be included in staging. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Ubuntu 20.04 vs 32bit wine [-staging] - more detailed documentation?
by Sebastian M. Ernst 09 Sep '22

09 Sep '22

Hi all, just burned *a lot* of time making Wine (Staging) for 64 and **32 bit** work on Ubuntu 20.04 (Ubuntu 22.04 was a little less painful) as part of a Github action of mine. The official documentation that is very commonly referred / pointed to ("if it does not work, you did not follow the instructions there to the letter") ... https://wiki.winehq.org/Ubuntu ... misses a few, apparently constantly shifting details on the 32 bit side of things. The "authoritative resource" on this topic appears to be this lovely long Github issue ... https://github.com/actions/runner-images/issues/4589 ... which thankfully also provides up-to-date workarounds (with rather significant side-effects), like the following as of July 26: ```bash sudo rm -f /etc/apt/sources.list.d/microsoft-prod.list sudo apt-get update -qq sudo apt-get install -yqq --allow-downgrades libgd3/focal libpcre2-8-0/focal libpcre2-16-0/focal libpcre2-32-0/focal libpcre2-posix2/focal sudo apt-get purge -yqq libmono* moby* mono* php* libgdiplus libpcre2-posix3 libzip4 ``` See, in the following order: - https://github.com/actions/runner-images/issues/4589#issuecomment-980506595 - https://github.com/actions/runner-images/issues/4589#issuecomment-1100899313 - https://github.com/actions/runner-images/issues/4589#issuecomment-1123074635 - https://github.com/actions/runner-images/issues/4589#issuecomment-1194891446 I am not sure if (or how) this belongs into your wiki (of if it can even be fixed / worked around partially within the dependencies of the packages from WineHQ's PPA). But since the above mentioned Github issue is not easy to find between a lot of other related but less helpful "noise" in online search results (and takes a while to comprehend), it might warrant creating a central, well known place that documents this behaviour in an up-to-date manner. Either way, in all honesty, thx to everybody who keeps 32 bit support running. For better or for worse, it is still badly needed. Best regards, Sebastian

3 2

[PATCH] include: disable some process/thread functions when in UAP mode
by Steve Lhomme 08 Sep '22

08 Sep '22

Wine doesn't use the winapifamily.h features but this header is also used in mingw-w64. These functions are also defined in processthreadsapi.h and many of them are not supposed to be called by non desktop apps. In order to have mingw-w64 avoid making these functions public when they should not, winbase.h need to match the mingw-w64 processthreadsapi.h. Either this is fixed in Wine it will need careful update of winbase.h when imported in mingw-w64. --- include/winbase.h | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/include/winbase.h b/include/winbase.h index 0a8409c10e1..f8f04643637 100644 --- a/include/winbase.h +++ b/include/winbase.h @@ -20,6 +20,7 @@ #define __WINE_WINBASE_H #include <winerror.h> +#include <winapifamily.h> #ifdef __cplusplus extern "C" { @@ -1901,15 +1902,19 @@ WINBASEAPI BOOL WINAPI CreateProcessA(LPCSTR,LPSTR,LPSECURITY_ATTRIBUTES, WINBASEAPI BOOL WINAPI CreateProcessW(LPCWSTR,LPWSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION); #define CreateProcess WINELIB_NAME_AW(CreateProcess) WINADVAPI BOOL WINAPI CreateProcessAsUserA(HANDLE,LPCSTR,LPSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCSTR,LPSTARTUPINFOA,LPPROCESS_INFORMATION); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINADVAPI BOOL WINAPI CreateProcessAsUserW(HANDLE,LPCWSTR,LPWSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION); +#endif #define CreateProcessAsUser WINELIB_NAME_AW(CreateProcessAsUser) WINBASEAPI BOOL WINAPI CreateProcessInternalA(HANDLE,LPCSTR,LPSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCSTR,LPSTARTUPINFOA,LPPROCESS_INFORMATION,HANDLE*); WINBASEAPI BOOL WINAPI CreateProcessInternalW(HANDLE,LPCWSTR,LPWSTR,LPSECURITY_ATTRIBUTES,LPSECURITY_ATTRIBUTES,BOOL,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION,HANDLE*); #define CreateProcessInternal WINELIB_NAME_AW(CreateProcessInternal) WINADVAPI BOOL WINAPI CreateProcessWithLogonW(LPCWSTR,LPCWSTR,LPCWSTR,DWORD,LPCWSTR,LPWSTR,DWORD,LPVOID,LPCWSTR,LPSTARTUPINFOW,LPPROCESS_INFORMATION); WINADVAPI BOOL WINAPI CreateProcessWithTokenW(HANDLE,DWORD,LPCWSTR,LPWSTR,DWORD,void *,LPCWSTR,STARTUPINFOW *,PROCESS_INFORMATION *); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI HANDLE WINAPI CreateRemoteThread(HANDLE,LPSECURITY_ATTRIBUTES,SIZE_T,LPTHREAD_START_ROUTINE,LPVOID,DWORD,LPDWORD); WINBASEAPI HANDLE WINAPI CreateRemoteThreadEx(HANDLE,LPSECURITY_ATTRIBUTES,SIZE_T,LPTHREAD_START_ROUTINE,LPVOID,DWORD,LPPROC_THREAD_ATTRIBUTE_LIST,LPDWORD); +#endif WINADVAPI BOOL WINAPI CreateRestrictedToken(HANDLE,DWORD,DWORD,PSID_AND_ATTRIBUTES,DWORD,PLUID_AND_ATTRIBUTES,DWORD,PSID_AND_ATTRIBUTES,PHANDLE); WINBASEAPI HANDLE WINAPI CreateSemaphoreA(LPSECURITY_ATTRIBUTES,LONG,LONG,LPCSTR); WINBASEAPI HANDLE WINAPI CreateSemaphoreW(LPSECURITY_ATTRIBUTES,LONG,LONG,LPCWSTR); @@ -1958,7 +1963,9 @@ WINBASEAPI void WINAPI DeleteFiber(LPVOID); WINBASEAPI BOOL WINAPI DeleteFileA(LPCSTR); WINBASEAPI BOOL WINAPI DeleteFileW(LPCWSTR); #define DeleteFile WINELIB_NAME_AW(DeleteFile) +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI void WINAPI DeleteProcThreadAttributeList(struct _PROC_THREAD_ATTRIBUTE_LIST*); +#endif WINBASEAPI BOOL WINAPI DeleteTimerQueue(HANDLE); WINBASEAPI BOOL WINAPI DeleteTimerQueueEx(HANDLE,HANDLE); WINBASEAPI BOOL WINAPI DeleteTimerQueueTimer(HANDLE,HANDLE,HANDLE); @@ -2248,12 +2255,16 @@ WINBASEAPI BOOL WINAPI GetLogicalProcessorInformation(PSYSTEM_LOGICAL_PRO WINBASEAPI BOOL WINAPI GetLogicalProcessorInformationEx(LOGICAL_PROCESSOR_RELATIONSHIP,PSYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX,PDWORD); WINBASEAPI DWORD WINAPI GetProcessHeaps(DWORD,PHANDLE); WINBASEAPI DWORD WINAPI GetProcessId(HANDLE); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI DWORD WINAPI GetProcessIdOfThread(HANDLE); +#endif WINBASEAPI BOOL WINAPI GetProcessIoCounters(HANDLE,PIO_COUNTERS); WINBASEAPI BOOL WINAPI GetProcessPriorityBoost(HANDLE,PBOOL); WINBASEAPI BOOL WINAPI GetProcessShutdownParameters(LPDWORD,LPDWORD); WINBASEAPI BOOL WINAPI GetProcessTimes(HANDLE,LPFILETIME,LPFILETIME,LPFILETIME,LPFILETIME); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI DWORD WINAPI GetProcessVersion(DWORD); +#endif WINBASEAPI BOOL WINAPI GetProcessWorkingSetSize(HANDLE,PSIZE_T,PSIZE_T); WINBASEAPI BOOL WINAPI GetProcessWorkingSetSizeEx(HANDLE,SIZE_T*,SIZE_T*,DWORD*); WINBASEAPI BOOL WINAPI GetProductInfo(DWORD,DWORD,DWORD,DWORD,PDWORD); @@ -2282,7 +2293,9 @@ WINBASEAPI DWORD WINAPI GetShortPathNameA(LPCSTR,LPSTR,DWORD); WINBASEAPI DWORD WINAPI GetShortPathNameW(LPCWSTR,LPWSTR,DWORD); #define GetShortPathName WINELIB_NAME_AW(GetShortPathName) WINBASEAPI VOID WINAPI GetStartupInfoA(LPSTARTUPINFOA); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI VOID WINAPI GetStartupInfoW(LPSTARTUPINFOW); +#endif #define GetStartupInfo WINELIB_NAME_AW(GetStartupInfo) WINBASEAPI HANDLE WINAPI GetStdHandle(DWORD); WINBASEAPI BOOL WINAPI GetSystemCpuSetInformation(SYSTEM_CPU_SET_INFORMATION*,ULONG,ULONG*,HANDLE,ULONG); @@ -2400,7 +2413,9 @@ WINBASEAPI BOOL WINAPI InitializeContext2(void *,DWORD,CONTEXT **,DWORD * WINBASEAPI void WINAPI InitializeCriticalSection(CRITICAL_SECTION *lpCrit); WINBASEAPI BOOL WINAPI InitializeCriticalSectionAndSpinCount(CRITICAL_SECTION *,DWORD); WINBASEAPI BOOL WINAPI InitializeCriticalSectionEx(CRITICAL_SECTION *,DWORD,DWORD); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI InitializeProcThreadAttributeList(struct _PROC_THREAD_ATTRIBUTE_LIST*,DWORD,DWORD,SIZE_T*); +#endif WINADVAPI BOOL WINAPI InitializeSecurityDescriptor(PSECURITY_DESCRIPTOR,DWORD); WINADVAPI BOOL WINAPI InitializeSid(PSID,PSID_IDENTIFIER_AUTHORITY,BYTE); WINBASEAPI VOID WINAPI InitializeSListHead(PSLIST_HEADER); @@ -2559,7 +2574,9 @@ WINBASEAPI VOID WINAPI OutputDebugStringW(LPCWSTR); WINBASEAPI BOOL WINAPI PeekNamedPipe(HANDLE,PVOID,DWORD,PDWORD,PDWORD,PDWORD); WINBASEAPI BOOL WINAPI PostQueuedCompletionStatus(HANDLE,DWORD,ULONG_PTR,LPOVERLAPPED); WINBASEAPI DWORD WINAPI PrepareTape(HANDLE,DWORD,BOOL); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI ProcessIdToSessionId(DWORD,DWORD*); +#endif WINADVAPI BOOL WINAPI PrivilegeCheck(HANDLE,PPRIVILEGE_SET,LPBOOL); WINADVAPI BOOL WINAPI PrivilegedServiceAuditAlarmA(LPCSTR,LPCSTR,HANDLE,PPRIVILEGE_SET,BOOL); WINADVAPI BOOL WINAPI PrivilegedServiceAuditAlarmW(LPCWSTR,LPCWSTR,HANDLE,PPRIVILEGE_SET,BOOL); @@ -2680,7 +2697,9 @@ WINADVAPI BOOL WINAPI SetPrivateObjectSecurity(SECURITY_INFORMATION,PSEC WINADVAPI BOOL WINAPI SetPrivateObjectSecurityEx(SECURITY_INFORMATION,PSECURITY_DESCRIPTOR,PSECURITY_DESCRIPTOR*,ULONG,PGENERIC_MAPPING,HANDLE); WINBASEAPI BOOL WINAPI SetProcessAffinityMask(HANDLE,DWORD_PTR); WINBASEAPI BOOL WINAPI SetProcessPriorityBoost(HANDLE,BOOL); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI SetProcessShutdownParameters(DWORD,DWORD); +#endif WINBASEAPI BOOL WINAPI SetProcessWorkingSetSize(HANDLE,SIZE_T,SIZE_T); WINBASEAPI BOOL WINAPI SetProcessWorkingSetSizeEx(HANDLE,SIZE_T,SIZE_T,DWORD); WINBASEAPI BOOL WINAPI SetSearchPathMode(DWORD); @@ -2698,7 +2717,9 @@ WINBASEAPI BOOL WINAPI SetSystemTimeAdjustment(DWORD,BOOL); WINBASEAPI DWORD WINAPI SetTapeParameters(HANDLE,DWORD,LPVOID); WINBASEAPI DWORD WINAPI SetTapePosition(HANDLE,DWORD,DWORD,DWORD,DWORD,BOOL); WINBASEAPI DWORD_PTR WINAPI SetThreadAffinityMask(HANDLE,DWORD_PTR); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI SetThreadContext(HANDLE,const CONTEXT *); +#endif WINBASEAPI BOOL WINAPI SetThreadErrorMode(DWORD,LPDWORD); WINBASEAPI DWORD WINAPI SetThreadExecutionState(EXECUTION_STATE); WINBASEAPI DWORD WINAPI SetThreadIdealProcessor(HANDLE,DWORD); @@ -2731,7 +2752,9 @@ WINBASEAPI BOOL WINAPI SwitchToThread(void); WINBASEAPI BOOL WINAPI SystemTimeToFileTime(const SYSTEMTIME*,LPFILETIME); WINBASEAPI BOOL WINAPI TerminateJobObject(HANDLE,UINT); WINBASEAPI BOOL WINAPI TerminateProcess(HANDLE,DWORD); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI TerminateThread(HANDLE,DWORD); +#endif WINBASEAPI DWORD WINAPI TlsAlloc(void); WINBASEAPI BOOL WINAPI TlsFree(DWORD); WINBASEAPI LPVOID WINAPI TlsGetValue(DWORD); @@ -2753,7 +2776,9 @@ WINBASEAPI BOOL WINAPI UmsThreadYield(void *); WINBASEAPI HRESULT WINAPI UnregisterApplicationRestart(void); WINBASEAPI BOOL WINAPI UnregisterWait(HANDLE); WINBASEAPI BOOL WINAPI UnregisterWaitEx(HANDLE,HANDLE); +#if WINAPI_FAMILY_PARTITION (WINAPI_PARTITION_DESKTOP) WINBASEAPI BOOL WINAPI UpdateProcThreadAttribute(struct _PROC_THREAD_ATTRIBUTE_LIST*,DWORD,DWORD_PTR,void*,SIZE_T,void*,SIZE_T*); +#endif WINBASEAPI BOOL WINAPI UpdateResourceA(HANDLE,LPCSTR,LPCSTR,WORD,LPVOID,DWORD); WINBASEAPI BOOL WINAPI UpdateResourceW(HANDLE,LPCWSTR,LPCWSTR,WORD,LPVOID,DWORD); #define UpdateResource WINELIB_NAME_AW(UpdateResource) -- 2.29.2

3 3

[PATCH] ntdll: Complete error case in get_initial_environment
by Gerald Pfeifer 06 Sep '22

06 Sep '22

GCC 12 (rightfully) would warn dlls/ntdll/unix/env.c:1910:12: warning: 'env_pos' may be used uninitialized Signed-off-by: Gerald Pfeifer <gerald(a)pfeifer.com> --- dlls/ntdll/unix/env.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/dlls/ntdll/unix/env.c b/dlls/ntdll/unix/env.c index 105038a34cb..cbbfb99f4b3 100644 --- a/dlls/ntdll/unix/env.c +++ b/dlls/ntdll/unix/env.c @@ -920,7 +920,11 @@ static WCHAR *get_initial_environment( SIZE_T *pos, SIZE_T *size ) *size = 1; for (e = main_envp; *e; e++) *size += strlen(*e) + 1; - if (!(env = malloc( *size * sizeof(WCHAR) ))) return NULL; + if (!(env = malloc( *size * sizeof(WCHAR) ))) + { + *pos = 0; + return NULL; + } ptr = env; end = env + *size - 1; for (e = main_envp; *e && ptr < end; e++) -- 2.34.1

2 1

RFC: Allow marking unreliable tests as flaky.
by Francois Gouget 02 Sep '22

02 Sep '22

Wine has many unreliable tests which makes it hard to know whether a patch causes new failures. So one proposal was to mark unreliable tests as flaky, and have a mode where flaky failures can ignored by setting $WINETEST_ALLOW_FLAKY. So one would be able to apply a patch, run 'WINETEST_ALLOW_FLAKY=1 make test' and if that fails that means the patch introduces a new failure. The way it works is that when a flaky test fails the message is 'Flaky failed...' instead of 'Test failed...'. I also added the count of flaky failures to the summary line. So the flaky failures are not totally swept under the rug. The main difference is that if $WINETEST_ALLOW_FLAKY is set, the exit code is 0 if the only failures are flaky ones. That still leaves some open questions though: * Should the message be 'Test failed' instead of 'Flaky failed' when $WINETEST_ALLOW_FLAKY is not set? I opted for the latter because it adds information that the failed test has been marked as flaky. * Should tests that fail systematically on some platforms but not others (for instance specific Windows versions, specific locales, specific GPUs) be marked as flaky? Or should flaky be reserved for tests that fail randomly? * What about failures where the message is different every time so that the failure always looks new? Should these not be marked as flaky since it only impacts the TestBot? * On a related note the patch below has flaky_windows and flaky_wine macros. Is that too fine grained? Maybe we don't want to run the risk of marking a test as flaky_windows only to discover later that it can also fail in Wine? But conversely, wouldn't it be valuable to know that a test is only flaky in Wine and not in Windows? Note: flaky_windows is a bit long but I was worried that flaky_win would be too similar to flaky_wine. * I decided having flaky_{windows,wine}_if() macros would be overkill. * How does one know a flaky directive can be removed? * Is it allowed to submit a patch that contains new flaky directives? * Also the flaky directive cannot deal with tests that randomly crash, prematurely exit, or time out. These issues are rarer so maybe we can hope they can all be fixed? * How does this impact bug 48912, aka "Allow blacklisting unreliable and always new failures"? https://bugs.winehq.org/show_bug.cgi?id=48912 * test.winehq.org and the TestBot will need to be updated to highlight the new messages and, more importantly, to recognize the new summary line. The patch is below and I bundled it with tweaks to a few tests for illustration purposes: d3d8:device - Failure happens on Windows (rarely) and Wine. dinput:mouse - Failure happens on Windows 7 and Wine. mmdevapi:render - Timing issue. schedsvc:atsvcapi - Wine-only failure. --- dlls/d3d8/tests/device.c | 2 +- dlls/dinput/tests/mouse.c | 2 +- dlls/mmdevapi/tests/render.c | 2 +- dlls/schedsvc/tests/atsvcapi.c | 2 +- include/wine/test.h | 78 +++++++++++++++++++++++++++++----- 5 files changed, 72 insertions(+), 14 deletions(-) diff --git a/dlls/d3d8/tests/device.c b/dlls/d3d8/tests/device.c index cb1e83b64b3..f0e8c27fafd 100644 --- a/dlls/d3d8/tests/device.c +++ b/dlls/d3d8/tests/device.c @@ -3356,7 +3356,7 @@ static void test_wndproc(void) expect_messages = sc_maximize_messages; SendMessageA(focus_window, WM_SYSCOMMAND, SC_MAXIMIZE, 0); - ok(!expect_messages->message, "Expected message %#x for window %#x, but didn't receive it.\n", + flaky ok(!expect_messages->message, "Expected message %#x for window %#x, but didn't receive it.\n", expect_messages->message, expect_messages->window); expect_messages = NULL; flush_events(); diff --git a/dlls/dinput/tests/mouse.c b/dlls/dinput/tests/mouse.c index 8be808e5da6..dcb5453a825 100644 --- a/dlls/dinput/tests/mouse.c +++ b/dlls/dinput/tests/mouse.c @@ -156,7 +156,7 @@ static void test_acquire(IDirectInputA *pDI, HWND hwnd) SetActiveWindow( hwnd ); hr = IDirectInputDevice_Acquire(pMouse); - ok(hr == S_OK, "Acquire() failed: %#lx\n", hr); + flaky ok(hr == S_OK, "Acquire() failed: %#lx\n", hr); mouse_event(MOUSEEVENTF_MOVE, 10, 10, 0, 0); cnt = 1; diff --git a/dlls/mmdevapi/tests/render.c b/dlls/mmdevapi/tests/render.c index 4e19b91c5f5..882be89b7ff 100644 --- a/dlls/mmdevapi/tests/render.c +++ b/dlls/mmdevapi/tests/render.c @@ -1098,7 +1098,7 @@ static void test_clock(int share) ok(pos == 0, "GetPosition returned non-zero pos before being started\n"); hr = IAudioClient_Start(ac); /* #1 */ - ok(hr == S_OK, "Start failed: %08lx\n", hr); + flaky ok(hr == S_OK, "Start failed: %08lx\n", hr); Sleep(100); slept += 100; diff --git a/dlls/schedsvc/tests/atsvcapi.c b/dlls/schedsvc/tests/atsvcapi.c index 3aaad8b5cfe..83774804b40 100644 --- a/dlls/schedsvc/tests/atsvcapi.c +++ b/dlls/schedsvc/tests/atsvcapi.c @@ -168,7 +168,7 @@ START_TEST(atsvcapi) skip_tests_delete: ret = NetrJobDel(server_name, jobid, jobid); - ok(ret == ERROR_SUCCESS, "NetrJobDel error %lu\n", ret); + flaky_wine ok(ret == ERROR_SUCCESS, "NetrJobDel error %lu\n", ret); skip_tests: SetUnhandledExceptionFilter(old_exception_filter); diff --git a/include/wine/test.h b/include/wine/test.h index 01ba81f4857..422ba3dce38 100644 --- a/include/wine/test.h +++ b/include/wine/test.h @@ -50,6 +50,9 @@ extern int winetest_time; /* running in interactive mode? */ extern int winetest_interactive; +/* always count flaky tests as successful (BOOL) */ +extern int winetest_allow_flaky; + /* report successful tests (BOOL) */ extern int winetest_report_success; @@ -117,6 +120,13 @@ extern void winetest_pop_context(void); #define trace trace_(__FILE__, __LINE__) #define wait_child_process wait_child_process_(__FILE__, __LINE__) +#define flaky_if(is_flaky) for (winetest_start_flaky(is_flaky); \ + winetest_loop_flaky(); \ + winetest_end_flaky()) +#define flaky flaky_if(1) +#define flaky_windows flaky_if(!strcmp(winetest_platform, "windows")) +#define flaky_wine flaky_if(!strcmp(winetest_platform, "wine")) + #define todo_if(is_todo) for (winetest_start_todo(is_todo); \ winetest_loop_todo(); \ winetest_end_todo()) @@ -200,6 +210,9 @@ int winetest_interactive = 0; /* current platform */ const char *winetest_platform = "windows"; +/* always count flaky tests as successful (BOOL) */ +int winetest_allow_flaky; + /* report successful tests (BOOL) */ int winetest_report_success = 0; @@ -214,6 +227,7 @@ static const struct test *current_test; /* test currently being run */ static LONG successes; /* number of successful tests */ static LONG failures; /* number of failures */ +static LONG flaky_failures; /* number of failures inside flaky block */ static LONG skipped; /* number of skipped test chunks */ static LONG todo_successes; /* number of successful tests inside todo block */ static LONG todo_failures; /* number of failures inside todo block */ @@ -229,6 +243,8 @@ struct tls_data { const char* current_file; /* file of current check */ int current_line; /* line of current check */ + unsigned int flaky_level; /* current flaky nesting level */ + int flaky_do_loop; unsigned int todo_level; /* current todo nesting level */ int todo_do_loop; char *str_pos; /* position in debug buffer */ @@ -355,9 +371,18 @@ int winetest_vok( int condition, const char *msg, va_list args ) { if (condition) { - winetest_print_context( "Test succeeded inside todo block: " ); - vprintf(msg, args); - InterlockedIncrement(&todo_failures); + if (data->flaky_level) + { + winetest_print_context( "Flaky succeeded inside todo block: " ); + vprintf(msg, args); + InterlockedIncrement(&flaky_failures); + } + else + { + winetest_print_context( "Test succeeded inside todo block: " ); + vprintf(msg, args); + InterlockedIncrement(&todo_failures); + } return 0; } else @@ -381,9 +406,18 @@ int winetest_vok( int condition, const char *msg, va_list args ) { if (!condition) { - winetest_print_context( "Test failed: " ); - vprintf(msg, args); - InterlockedIncrement(&failures); + if (data->flaky_level) + { + winetest_print_context( "Flaky failed: " ); + vprintf(msg, args); + InterlockedIncrement(&flaky_failures); + } + else + { + winetest_print_context( "Test failed: " ); + vprintf(msg, args); + InterlockedIncrement(&failures); + } return 0; } else @@ -456,6 +490,27 @@ void winetest_win_skip( const char *msg, ... ) va_end(valist); } +void winetest_start_flaky( int is_flaky ) +{ + struct tls_data *data = get_tls_data(); + data->flaky_level = (data->flaky_level << 1) | (is_flaky != 0); + data->flaky_do_loop=1; +} + +int winetest_loop_flaky(void) +{ + struct tls_data *data = get_tls_data(); + int do_flaky=data->flaky_do_loop; + data->flaky_do_loop=0; + return do_flaky; +} + +void winetest_end_flaky(void) +{ + struct tls_data *data = get_tls_data(); + data->flaky_level >>= 1; +} + void winetest_start_todo( int is_todo ) { struct tls_data *data = get_tls_data(); @@ -601,14 +656,16 @@ static int run_test( const char *name ) printf( "%04x:%s:%s Silenced %d todos, %d skips and %d traces.\n", (UINT)GetCurrentProcessId(), test->name, winetest_elapsed(), (UINT)muted_todo_successes, (UINT)muted_skipped, (UINT)muted_traces); - printf( "%04x:%s:%s %d tests executed (%d marked as todo, %d %s), %d skipped.\n", + printf( "%04x:%s:%s %d tests executed (%d marked as todo, %d as flaky, %d %s), %d skipped.\n", (UINT)GetCurrentProcessId(), test->name, winetest_elapsed(), - (UINT)(successes + failures + todo_successes + todo_failures), - (UINT)todo_successes, (UINT)(failures + todo_failures), + (UINT)(successes + failures + flaky_failures + todo_successes + todo_failures), + (UINT)todo_successes, (UINT)flaky_failures, (UINT)(failures + todo_failures), (failures + todo_failures != 1) ? "failures" : "failure", (UINT)skipped ); } - status = (failures + todo_failures < 255) ? failures + todo_failures : 255; + status = failures + todo_failures; + if (!winetest_allow_flaky) status += flaky_failures; + if (status > 255) status = 255; return status; } @@ -665,6 +722,7 @@ int main( int argc, char **argv ) if (GetEnvironmentVariableA( "WINETEST_DEBUG", p, sizeof(p) )) winetest_debug = atoi(p); if (GetEnvironmentVariableA( "WINETEST_INTERACTIVE", p, sizeof(p) )) winetest_interactive = atoi(p); + if (GetEnvironmentVariableA( "WINETEST_ALLOW_FLAKY", p, sizeof(p) )) winetest_allow_flaky = atoi(p); if (GetEnvironmentVariableA( "WINETEST_REPORT_SUCCESS", p, sizeof(p) )) winetest_report_success = atoi(p); if (GetEnvironmentVariableA( "WINETEST_TIME", p, sizeof(p) )) winetest_time = atoi(p); winetest_last_time = winetest_start_time = GetTickCount(); -- 2.30.2

7 12

Puzzling IPrincipal:UserId check in taskschd
by Francois Gouget 31 Aug '22

31 Aug '22

So I'm a bit puzzled by this check in taskschd/task.c's write_principal(): hr = IPrincipal_get_UserId(principal, &bstr); if (hr == S_OK && lstrlenW(bstr)) { hr = write_text_value(stream, L"UserId", bstr); What's puzzling to me is the lstrlenW(bstr) check: * write_principal() has no such check for Id, GroupId, DisplayName and RunLevel. Maybe that's because they are guaranteed to be set and non empty but I could not find any documentation saying so and they are not implemented in Wine. * write_registration_info() is very similar but checks bstr, not what is in effect *bstr: hr = IRegistrationInfo_get_Source(reginfo, &bstr); if (hr == S_OK && bstr) { hr = write_text_value(stream, L"Source", bstr); * We don't seem to have tests showing how this works. I would expect all these property getters to work the same way. So would something like that make more sense? hr = IPrincipal_get_UserId(principal, &bstr); if (hr == S_OK && bstr) { hr = write_text_value(stream, L"UserId", bstr); Dmitry: Do you remember if you wrote the lstrlenW(bstr) check because of some test you did? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Computers are like airconditioners They stop working properly if you open WINDOWS

2 1

Whenever i use wine this message pop up and the application doesn't run please any help
by anthonyuser33 29 Aug '22

29 Aug '22

Sent from my Galaxy

1 0

Wine staging 7.16 release
by Alistair Leslie-Hughes 29 Aug '22

29 Aug '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.16 (531 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * wined3d: Use wined3d_array_reserve() in wined3d_adapter_create_output(). * dsdmo: Add Echo FX Support * dsdmo: Add Compressor FX Support * ddraw: Don't set HWTRANSFORMANDLIGHT flag on d3d7 RGB device. 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

[PATCH 1/2] readme: Update Finnish translation.
by Lauri Kenttä 29 Aug '22

29 Aug '22

Signed-off-by: Lauri Kenttä <lauri.kentta(a)gmail.com> --- documentation/README.fi | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/documentation/README.fi b/documentation/README.fi index e459bbc779a..00af959c033 100644 --- a/documentation/README.fi +++ b/documentation/README.fi @@ -146,6 +146,8 @@ Kysymyksiä: Wiki: Wine Wiki on osoitteessa https://wiki.winehq.org/. +Gitlab: Winen kehitykseen voi osallistua sivustolla https://gitlab.winehq.org + Postituslistat: Winen käyttäjille ja kehittäjille on joitakin postituslistoja, sivulla https://www.winehq.org/forums kerrotaan niistä lisää. @@ -157,14 +159,6 @@ Virheet: IRC: Online-apua voi saada kanavalta #WineHQ palvelimella irc.libera.chat. -Git: Winen tämänhetkinen kehitysversio on jaossa Git-järjestelmän kautta. - Sivulla https://www.winehq.org/git kerrotaan tästä lisää. - - -Jos lisäät jotain tai korjaat jonkin virheen, lähetä toki muutoksesi -(mieluiten komennon git-format-patch avulla) listalle wine-devel(a)winehq.org, -jotta se voidaan lisätä Winen seuraavaan versioon. - -- Alkuperäisen version tekstistä on kirjoittanut Alexandre Julliard -- 2.37.2

2 2

Upcoming vkd3d 1.5 release.
by Henri Verbeet 24 Aug '22

24 Aug '22

Hi all, As previously discussed, we'd like to release vkd3d 1.5 in about 4 weeks. Practically speaking, that means that as we're nearing that date, the vkd3d tree is going to become progressively frozen, starting today. Now is the time to test your games for any regressions, review any API changes since vkd3d 1.4, review/improve the API documentation, and so on. If you're working on any larger features or architectural changes, ideally you'd have those ready to merge shortly after the 1.5 release, so that they'll make it into the 1.6 release, tentatively planned for early December. Regards, Henri

1 0

wine-devel moved to Mailman3
by Jeremy Newman 22 Aug '22

22 Aug '22

This list has been migrated to a new interface. To manage your subscription go here: https://www.winehq.org/mailman3/postorius/lists/wine-devel.winehq.org/ To view the archives go here: https://www.winehq.org/mailman3/hyperkitty/list/wine-devel@winehq.org/ The old archives will remain online to preserve links. -N

1 0

[PATCH 1/2] user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.
by Dmitry Timoshkov 18 Aug '22

18 Aug '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/user32/tests/sysparams.c | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/dlls/user32/tests/sysparams.c b/dlls/user32/tests/sysparams.c index 4f2709094e9..e354ef69a94 100644 --- a/dlls/user32/tests/sysparams.c +++ b/dlls/user32/tests/sysparams.c @@ -4124,6 +4124,31 @@ static void test_GetAutoRotationState(void) ok(ret, "Expected GetAutoRotationState to succeed, error %ld\n", GetLastError()); } +static void test_LOGFONT_charset(void) +{ + CHARSETINFO csi; + LOGFONTA lf; + NONCLIENTMETRICSA ncm; + BOOL ret; + + ret = TranslateCharsetInfo(ULongToPtr(GetACP()), &csi, TCI_SRCCODEPAGE); + ok(ret, "TranslateCharsetInfo(%d) error %lu\n", GetACP(), GetLastError()); + + GetObjectA(GetStockObject(DEFAULT_GUI_FONT), sizeof(lf), &lf); + ok(lf.lfCharSet == csi.ciCharset, "got %d, expected %d\n", lf.lfCharSet, csi.ciCharset); + + ret = SystemParametersInfoA(SPI_GETICONTITLELOGFONT, sizeof(lf), &lf, FALSE); + ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); + todo_wine + ok(lf.lfCharSet == DEFAULT_CHARSET, "got %d\n", lf.lfCharSet); + + ncm.cbSize = FIELD_OFFSET(NONCLIENTMETRICSA, iPaddedBorderWidth); + ret = SystemParametersInfoA(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0); + ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); + todo_wine + ok(ncm.lfCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfCaptionFont.lfCharSet); +} + START_TEST(sysparams) { int argc; @@ -4172,6 +4197,8 @@ START_TEST(sysparams) strict=(argc >= 3 && strcmp(argv[2],"strict")==0); trace("strict=%d\n",strict); + test_LOGFONT_charset(); + trace("testing GetSystemMetrics with your current desktop settings\n"); test_GetSystemMetrics( ); test_metrics_for_dpi( 192 ); -- 2.37.2

2 2

[PATCH 2/2] user32: Set font charset to DEFAULT_CHARSET to support locale change.
by Dmitry Timoshkov 18 Aug '22

18 Aug '22

Otherwise when the prefix was created with one locale and later an application in the prefix is running with a different locale values cached in the registry lead to broken UI. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/user32/tests/sysparams.c | 4 ++-- dlls/win32u/sysparams.c | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/dlls/user32/tests/sysparams.c b/dlls/user32/tests/sysparams.c index e354ef69a94..6ab7010c4ed 100644 --- a/dlls/user32/tests/sysparams.c +++ b/dlls/user32/tests/sysparams.c @@ -4139,14 +4139,13 @@ static void test_LOGFONT_charset(void) ret = SystemParametersInfoA(SPI_GETICONTITLELOGFONT, sizeof(lf), &lf, FALSE); ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); - todo_wine ok(lf.lfCharSet == DEFAULT_CHARSET, "got %d\n", lf.lfCharSet); ncm.cbSize = FIELD_OFFSET(NONCLIENTMETRICSA, iPaddedBorderWidth); ret = SystemParametersInfoA(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0); ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); - todo_wine ok(ncm.lfCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfCaptionFont.lfCharSet); + ok(ncm.lfSmCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfSmCaptionFont.lfCharSet); } START_TEST(sysparams) diff --git a/dlls/win32u/sysparams.c b/dlls/win32u/sysparams.c index 52665f7a641..879dffb58e2 100644 --- a/dlls/win32u/sysparams.c +++ b/dlls/win32u/sysparams.c @@ -3039,12 +3039,14 @@ static BOOL get_font_entry( union sysparam_all_entry *entry, UINT int_param, voi switch (load_entry( &entry->hdr, &font, sizeof(font) )) { case sizeof(font): + font.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ if (font.lfHeight > 0) /* positive height value means points ( inch/72 ) */ font.lfHeight = -muldiv( font.lfHeight, USER_DEFAULT_SCREEN_DPI, 72 ); entry->font.val = font; break; case sizeof(LOGFONT16): /* win9x-winME format */ logfont16to32( (LOGFONT16 *)&font, &entry->font.val ); + entry->font.val.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ if (entry->font.val.lfHeight > 0) entry->font.val.lfHeight = -muldiv( entry->font.val.lfHeight, USER_DEFAULT_SCREEN_DPI, 72 ); break; @@ -3055,6 +3057,7 @@ static BOOL get_font_entry( union sysparam_all_entry *entry, UINT int_param, voi /* fall through */ case 0: /* use the default GUI font */ NtGdiExtGetObjectW( GetStockObject( DEFAULT_GUI_FONT ), sizeof(font), &font ); + font.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ font.lfHeight = map_from_system_dpi( font.lfHeight ); font.lfWeight = entry->font.weight; entry->font.val = font; @@ -3094,6 +3097,7 @@ static BOOL set_font_entry( union sysparam_all_entry *entry, UINT int_param, voi static BOOL init_font_entry( union sysparam_all_entry *entry ) { NtGdiExtGetObjectW( GetStockObject( DEFAULT_GUI_FONT ), sizeof(entry->font.val), &entry->font.val ); + entry->font.val.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ entry->font.val.lfHeight = map_from_system_dpi( entry->font.val.lfHeight ); entry->font.val.lfWeight = entry->font.weight; get_real_fontname( &entry->font.val, entry->font.fullname ); -- 2.37.2

1 0

wine-cvs renamed to wine-commits
by Jeremy Newman 17 Aug '22

17 Aug '22

The wine-cvs mailing list for git push notifications has *finally* been renamed to wine-commits. How many years has it been since we switched away from cvs? Something like 15 years! We also migrated the list over to mailman v3 so the links to the archives and subscription management have changed. The old archives will remain online to not break links. All the lists save one have been migrated. We will be migrating wine-devel soonish(tm). Updated links to the mailing lists and archives are here: https://www.winehq.org/forums Remember to update your email filters. -N

1 0

Patch tracker
by Alexandre Julliard 16 Aug '22

16 Aug '22

Folks, We now have an automated reviewer assignment bot in Gitlab, thanks to the work of Jeremy White, so I think it's time to retire the wine-devel patch tracker. From now on, please submit everything through merge requests; patches sent to wine-devel will no longer be applied. Some reminders about the new policies: - Adding a Signed-off-by header is no longer necessary. This is replaced by the Gitlab approval mechanism. - When a new MR is submitted, the bot will assign reviewers based on the MAINTAINERS file. If the bot got it wrong, or if you would like to request reviews from other people, feel free to modify the list of reviewers. - If you don't have permission to modify reviewers, you should request access to the Wine project. There should be a link for this on the main project page at https://gitlab.winehq.org/wine/wine - I won't merge a MR until all reviewers have approved it. If you are assigned as reviewer but are unable/unwilling to review that MR, please unassign yourself so that the MR isn't blocked waiting for your approval. - In general, approving your own MR is not necessary or useful. - As an exception to the above, if your MR contains commits authored by someone else, you are asked to explicitly approve it. The bot will assign you as an extra reviewer in that case. - Approval information is stored in git notes. You can fetch the refs/notes/commits head if you'd like to see that information in your local tree. - We now have a CI pipeline to make sure that all the commits of a MR compile cleanly. Later on, the pipeline will also run the tests. Make sure to check the pipeline results; a MR with a failed pipeline won't be merged. Questions? Comments? -- Alexandre Julliard julliard(a)winehq.org

4 7

[PATCH] qedit: Remove "ugly" work around
by Brendan McGrath 15 Aug '22

15 Aug '22

This patch removes a work around that causes a crash in Unravel Two. There is a callback in Unravel Two that appears to add a reference to a IMediaSample, which this work around treats as a leak and releases. However, the application also releases the reference causing a negative overflow and an assertion failure on line 345 of dlls/quartz/memallocator.c. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51616 Signed-off-by: Brendan McGrath <brendan(a)redmandi.com> --- Although I'm not convinced just deleting 12 yr old code is a great idea, the original author did describe this work around as "ugly". I would describe it as unsafe. See Wine Bug 51616. I think it may also be possible for the work around to fail in a multi-threaded scenario, where the IMediaSample is accessed in parallel to the callback; potentially with a negative overflow of its own (and looping 4294967295 times). Although I'm not familiar enough with the uses of qedit to understand if this is even plausible. Unfortunately, I've only tested the removal of this work around with the one application; Unravel Two. Also note that I've only been able to test this "fix" with a local build of Proton 7 Experimental. I couldn't get the application to run in vanilla Wine (as the Origin launcher failed to install). Definitely interested in thoughts. dlls/qedit/samplegrabber.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/dlls/qedit/samplegrabber.c b/dlls/qedit/samplegrabber.c index 9b9780e564a8..cefb2f370785 100644 --- a/dlls/qedit/samplegrabber.c +++ b/dlls/qedit/samplegrabber.c @@ -164,9 +164,6 @@ static void SampleGrabber_callback(struct sample_grabber *This, IMediaSample *sa if (ref) { ERR("(%p) Callback referenced sample %p by %lu\n", This, sample, ref); - /* ugly as hell but some apps are sooo buggy */ - while (ref--) - IMediaSample_Release(sample); } } break; -- 2.34.1

4 6

Wine staging 7.15 release
by Alistair Leslie-Hughes 14 Aug '22

14 Aug '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.15 (536 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * xactengine3_7: Record context for each notification. * xactengine3_7: Add helper function to add entries. * xactengine3_7: Map SoundBank interfaces. * xactengine3_7: Map IXACT3Cue interfaces. * xactengine3_7: Map IXACT3Wave interfaces. * xactengine3_7: Implement callback for supported messages. Added: * [52396] ntdll: Don't use Wine frames during exception processing on x64. * [52396] dsdmo: Add more FX interfaces. * [53497] wined3d: Use wined3d_array_reserve() in wined3d_adapter_create_output() 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

Re: [PATCH v2 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.
by Marvin 12 Aug '22

12 Aug '22

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=121155 Your paranoid android. === w1064 (32 bit report) === d3d11: d3d11.c:5914: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:28519: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28528: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28519: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28519: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28528: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28528: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH v2 2/3] d3d11: Always return E_FAIL for formats which have no support flags.
by Marvin 12 Aug '22

12 Aug '22

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=121154 Your paranoid android. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Test marked todo: Feature level 0xb000: Format 0x5b - display not supported, format support 0x80f3f1. d3d11.c:1571: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: d3d11.c:1576: Test marked todo: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:9946: Test failed: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:28489: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28498: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28489: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28489: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28498: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28498: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH v2 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.
by Marvin 12 Aug '22

12 Aug '22

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=121153 Your paranoid android. === w10pro64 (32 bit report) === d3d11: d3d11.c:5914: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:28486: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28486: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28486: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.
by Marvin 11 Aug '22

11 Aug '22

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=121056 Your paranoid android. === w1064_adm (64 bit report) === d3d11: d3d11.c:5910: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28515: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28515: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28524: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28524: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:28515: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28524: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28278: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28278: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28278: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28286: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28286: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28295: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 2/3] d3d11: Always return E_FAIL for formats which have no support flags.
by Marvin 11 Aug '22

11 Aug '22

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=121055 Your paranoid android. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28485: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28485: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28494: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28494: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28485: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28494: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28248: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28248: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28248: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28256: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28256: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28265: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.
by Marvin 11 Aug '22

11 Aug '22

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=121054 Your paranoid android. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28482: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28491: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28482: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28482: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28491: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28491: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28428: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:28428: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28428: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28245: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28245: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28245: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28253: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28253: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28262: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 1/6] mshtml: Forward Document's Invoke to InvokeEx.
by Marvin 11 Aug '22

11 Aug '22

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=121042 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

WineConf 2022 - Bring out your talks
by Jeremy White 11 Aug '22

11 Aug '22

Hey folks, I've just learned that what we've done all these years is an un conference (https://en.wikipedia.org/wiki/Unconference) or a BarCamp (https://en.wikipedia.org/wiki/BarCamp). So we were cool *long* before these other cats starting copying us. However, since we are partnering with X.org on Wine Conf, and they use the slick Indico conference system, we should get with the program. I would really appreciate it if folks could submit talk ideas: https://indico.freedesktop.org/event/2/abstracts/ We have, a non zero number of scheduled presentations already, but think that number may be one. So I would really appreciate it if folks would submit abstracts. Cheers, Jeremy p.s. Other reminders: - We have funds available to sponsor travel. If cost makes you hesitate, please reach out to me privately. - There is a hotel block you can sign up for - New this year, it's nice if you sign to show you are coming: https://indico.freedesktop.org/event/2/registrations/2/.

2 1

Re: [PATCH v2 4/6] mf: Allow resolving topology with missing downstream current type.
by Marvin 11 Aug '22

11 Aug '22

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=121023 Your paranoid android. === w10pro64_ja (64 bit report) === mf: mf: Timeout

1 0

Re: [PATCH 1/5] comctl32/tests: Add IME tests for edit control.
by Marvin 11 Aug '22

11 Aug '22

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=120932 Your paranoid android. === w10pro64 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v3 1/2] mshtml: Semi-implement non-string primitive data for postMessage.
by Marvin 10 Aug '22

10 Aug '22

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=120888 Your paranoid android. === w10pro64_zh_CN (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH v5 01/10] winmm/tests: Add tests for visibility of video window.
by Marvin 10 Aug '22

10 Aug '22

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=120860 Your paranoid android. === w7u_adm (32 bit report) === winmm: midi.c:988: Test failed: bad message 1e/0 from midiStreamOpen, expect 3c7/0 midi.c:1039: Test failed: bad message 3c7/0 from midiStreamOut, expect 3c9/22f940 midi.c:1048: Test failed: bad message 3c9/22f940 from midiStreamClose, expect 3c8/0 === w7u_adm (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w7u_adm (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v4 03/13] mmdevapi: Integrate winepulse's additions in unixlib.h
by Marvin 10 Aug '22

10 Aug '22

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=120814 Your paranoid android. === debian11 (32 bit Chinese:China report) === mmdevapi: capture.c:205: Test failed: GCP 16553 past ReleaseBuffer(0) initially 16058

1 0

Re: [PATCH 1/1] d3d11: Validate layout description in d3d_input_layout_create().
by Marvin 09 Aug '22

09 Aug '22

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=120787 Your paranoid android. === w1064 (32 bit report) === d3d11: d3d11.c:5908: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: d3d11.c:1570: Test marked todo: Format 0x57 - display not supported, feature_level 0x9200, format support 0x200f3f2.

1 0

Re: [PATCH v2 1/2] mshtml: Semi-implement non-string primitive data for postMessage.
by Marvin 09 Aug '22

09 Aug '22

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=120782 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

WinRt activable class registration
by Kacper rączy 09 Aug '22

09 Aug '22

Hi everyone, First of all, I’m not really familiar with Windows dev environment and tools outside of wine. I’m building custom implementation of some Windows Runtime modules (separate project outside of wine-tree). Similarly to windows.gaming.input in wine, I’ve created classes.idl with `#pragma makedep register`, and using widl to compile it into classes_r.res script file. Then I’m using windres to convert to coff and link it against my dll. Then the runtime classes implemented by dll have to registered. So far I was adding registry entries with DllPath manually in regedit (in HKLM.Software.Microsoft.WindowsRuntime.ActivatableClassId.[CLASS_NAME]) for testing purposes, because I don’t really know how utilize registration script that’s already embedded in dll. So my question is, how do I register Dll for activable winrt classes? Is there a tool for that? Thanks, Kacper Rączy

1 0

Re: [PATCH 2/2] ntdll: Fix leak of mach_host_self port.
by Marvin 08 Aug '22

08 Aug '22

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=120698 Your paranoid android. === debian11 (32 bit WoW report) === ntdll: change.c:277: Test failed: should be ready

1 0

Re: [PATCH v2 1/2] mf: Handle timer time behind clock time in present_clock_schedule_timer().
by Marvin 08 Aug '22

08 Aug '22

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=120690 Your paranoid android. === w7u_el (32 bit report) === mf: mf: Timeout

1 0

[PATCH] srvsvc: Add LanmanServer stub service.
by Dmitry Timoshkov 08 Aug '22

08 Aug '22

wine.inf already has an entry for it. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- configure.ac | 1 + dlls/srvsvc/Makefile.in | 5 +++ dlls/srvsvc/srvsvc.c | 87 +++++++++++++++++++++++++++++++++++++++++ dlls/srvsvc/srvsvc.spec | 1 + loader/wine.inf.in | 4 +- 5 files changed, 96 insertions(+), 2 deletions(-) create mode 100644 dlls/srvsvc/Makefile.in create mode 100644 dlls/srvsvc/srvsvc.c create mode 100644 dlls/srvsvc/srvsvc.spec diff --git a/configure.ac b/configure.ac index dd4abd39e32..bec0513c46d 100644 --- a/configure.ac +++ b/configure.ac @@ -3035,6 +3035,7 @@ WINE_CONFIG_MAKEFILE(dlls/spoolss/tests) WINE_CONFIG_MAKEFILE(dlls/sppc) WINE_CONFIG_MAKEFILE(dlls/srclient) WINE_CONFIG_MAKEFILE(dlls/srvcli) +WINE_CONFIG_MAKEFILE(dlls/srvsvc) WINE_CONFIG_MAKEFILE(dlls/sspicli) WINE_CONFIG_MAKEFILE(dlls/stdole2.tlb) WINE_CONFIG_MAKEFILE(dlls/stdole32.tlb) diff --git a/dlls/srvsvc/Makefile.in b/dlls/srvsvc/Makefile.in new file mode 100644 index 00000000000..f9c68fd12aa --- /dev/null +++ b/dlls/srvsvc/Makefile.in @@ -0,0 +1,5 @@ +MODULE = srvsvc.dll +IMPORTS = advapi32 + +C_SRCS = \ + srvsvc.c diff --git a/dlls/srvsvc/srvsvc.c b/dlls/srvsvc/srvsvc.c new file mode 100644 index 00000000000..3b2b563bc6c --- /dev/null +++ b/dlls/srvsvc/srvsvc.c @@ -0,0 +1,87 @@ +/* + * LanmanServer Service + * + * Copyright 2022 Dmitry Timoshkov + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA + */ + +#include <stdarg.h> + +#include "windef.h" +#include "winbase.h" +#include "winsvc.h" +#include "wine/debug.h" + +WINE_DEFAULT_DEBUG_CHANNEL(lanman); + +static SERVICE_STATUS_HANDLE svc_handle; +static HANDLE done_event; + +static void svc_update_status(DWORD state) +{ + SERVICE_STATUS status; + + status.dwServiceType = SERVICE_WIN32; + status.dwControlsAccepted = SERVICE_ACCEPT_STOP | SERVICE_ACCEPT_SHUTDOWN; + status.dwWin32ExitCode = 0; + status.dwServiceSpecificExitCode = 0; + status.dwCheckPoint = 0; + status.dwWaitHint = 0; + status.dwCurrentState = state; + + SetServiceStatus(svc_handle, &status); +} + +static void WINAPI svc_handler(DWORD control) +{ + TRACE("%#lx\n", control); + + switch (control) + { + case SERVICE_CONTROL_STOP: + case SERVICE_CONTROL_SHUTDOWN: + svc_update_status(SERVICE_STOP_PENDING); + SetEvent(done_event); + break; + + default: + svc_update_status(SERVICE_RUNNING); + break; + } +} + +void WINAPI ServiceMain(DWORD argc, LPWSTR *argv) +{ + TRACE("Starting LanmanServer\n"); + + svc_handle = RegisterServiceCtrlHandlerW(L"LanmanServer", svc_handler); + if (!svc_handle) + { + ERR("RegisterServiceCtrlHandler error %ld\n", GetLastError()); + return; + } + + svc_update_status(SERVICE_START_PENDING); + done_event = CreateEventW(NULL, TRUE, FALSE, NULL); + + svc_update_status(SERVICE_RUNNING); + WaitForSingleObject(done_event, INFINITE); + CloseHandle(done_event); + + svc_update_status(SERVICE_STOPPED); + + TRACE("Exiting LanmanServer\n"); +} diff --git a/dlls/srvsvc/srvsvc.spec b/dlls/srvsvc/srvsvc.spec new file mode 100644 index 00000000000..daa88578f7f --- /dev/null +++ b/dlls/srvsvc/srvsvc.spec @@ -0,0 +1 @@ +@ stdcall -private ServiceMain(long ptr) diff --git a/loader/wine.inf.in b/loader/wine.inf.in index e7b435ed0f0..d686e0b4f2f 100644 --- a/loader/wine.inf.in +++ b/loader/wine.inf.in @@ -2396,12 +2396,12 @@ Description="Lanman Server" DisplayName="Lanman Server" ServiceBinary="%11%\svchost.exe -k netsvcs" ServiceType=32 -StartType=4 +StartType=3 ErrorControl=1 [LanmanServerServiceKeys] HKR,Parameters,"ServiceDll",,"%11%\srvsvc.dll" -;; HKLM,%CurrentVersionNT%\SvcHost,"netsvcs",0x00010008,"lanmanserver" +HKLM,%CurrentVersionNT%\SvcHost,"netsvcs",0x00010008,"lanmanserver" [FontCacheService] AddReg=FontCacheServiceKeys -- 2.37.1

1 0

[PATCH] wevtsvc: Remove duplicate dwControlsAccepted initialization.
by Dmitry Timoshkov 08 Aug '22

08 Aug '22

dwControlsAccepted is initialized a few lines earlier. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/wevtsvc/wevtsvc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/dlls/wevtsvc/wevtsvc.c b/dlls/wevtsvc/wevtsvc.c index 2e303045740..78c68bac69b 100644 --- a/dlls/wevtsvc/wevtsvc.c +++ b/dlls/wevtsvc/wevtsvc.c @@ -40,7 +40,6 @@ static void eventlog_update_status(DWORD state) status.dwServiceSpecificExitCode = 0; status.dwCheckPoint = 0; status.dwWaitHint = 0; - status.dwControlsAccepted = 0; status.dwCurrentState = state; SetServiceStatus(svc_handle, &status); -- 2.37.1

1 0

[PATCH] schedsvc: Remove duplicate dwControlsAccepted initialization.
by Dmitry Timoshkov 08 Aug '22

08 Aug '22

dwControlsAccepted is initialized a few lines earlier. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/schedsvc/svc_main.c | 1 - 1 file changed, 1 deletion(-) diff --git a/dlls/schedsvc/svc_main.c b/dlls/schedsvc/svc_main.c index 7681a220592..2250854e953 100644 --- a/dlls/schedsvc/svc_main.c +++ b/dlls/schedsvc/svc_main.c @@ -281,7 +281,6 @@ static void schedsvc_update_status(DWORD state) status.dwServiceSpecificExitCode = 0; status.dwCheckPoint = 0; status.dwWaitHint = 0; - status.dwControlsAccepted = 0; status.dwCurrentState = state; SetServiceStatus(schedsvc_handle, &status); -- 2.37.1

1 0

Re: [PATCH v8 2/5] winegstreamer: Implement IWMOutputMediaProps_SetMediaType.
by Marvin 08 Aug '22

08 Aug '22

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=120665 Your paranoid android. === debian11 (32 bit report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Arabic:Morocco report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit German report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit French report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Hebrew:Israel report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Hindi:India report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Japanese:Japan report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Chinese:China report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit WoW report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (64 bit WoW report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2.

1 0

Wine-Contribution
by Alan 07 Aug '22

07 Aug '22

Hello There i need some help regarding to start applying patches to wine and start contributing the problem is I don't know where to start? I went to the wine website and started reading. I didn't get much useful stuff but There was some good documentation about the codebase and the structure of it , but if I want to start applying patches to wine, where should I start besides the website ? Should I start reading the codebase ? If so, where should I start reading the codebase from ? or should I just go and try to patch the bugs that's on the forks issue section? Thanks For your Time Alan

2 1

Re: [PATCH v4 09/10] mciqtz32: Hide the default video window when switching to another one.
by Marvin 06 Aug '22

06 Aug '22

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=120640 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === winmm: mci.c:1291: Test failed: sysinfo quantity open expected 0 after auto-close, got: 1

1 0

Wine web-based translation using Weblate
by Óvári 06 Aug '22

06 Aug '22

Hello, Can Wine please be available for translation using a browser (eg Firefox) at Weblate? https://hosted.weblate.org/ Thank you On Tue, 19 Jul 2022: [...] > I would have to reassess to be exact but the requirement that caused > issues with most of the systems I investigated was that wine requires > all patches, even translations, to be clearly accredited to a user by > full real name and email. I remember that being the main issue too. But their attribution FAQ says every change is committed under the translators name: https://docs.weblate.org/fr/latest/faq.html#how-does-weblate-credit-transla… | Every change made in Weblate is committed into VCS under the | translators name. This way every single change has proper authorship, | and you can track it down using the standard VCS tools you use for | code. It sounds like this would fulfil Wine's requirement. Also this should probably be posted on wine-devel since it concerns the whole community and would broaden the pool of people who can move forward on this.

1 0

Re: [PATCH v7 1/5] wmvcore/tests: Add some IWMOutputMediaProps_SetMediaType tests.
by Marvin 05 Aug '22

05 Aug '22

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=120582 Your paranoid android. === debian11 (32 bit report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Arabic:Morocco report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit German report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit French report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Hebrew:Israel report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Hindi:India report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Japanese:Japan report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Chinese:China report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit WoW report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (64 bit WoW report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0.

1 0

Re: [PATCH vkd3d v3 13/17] vkd3d-shader/hlsl: Replace register offsets with index paths in resource loads initialization.
by Francisco Casas 04 Aug '22

04 Aug '22

Ah, I finally see, the hlsl_src_from_node(&deref->offset, other->offset.node); indeed is a noop. I will fix it. On 25-07-22 04:11, Giovanni Mascellani wrote: > Hi, > > Il 22/07/22 20:36, Francisco Casas ha scritto: >>>> diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c >>>> index 2d5fe40a..a4d594b7 100644 >>>> --- a/libs/vkd3d-shader/hlsl.c >>>> +++ b/libs/vkd3d-shader/hlsl.c >>>> @@ -862,6 +862,28 @@ static bool type_is_single_reg(const struct >>>> hlsl_type *type) >>>> return type->type == HLSL_CLASS_SCALAR || type->type == >>>> HLSL_CLASS_VECTOR; >>>> } >>>> +static bool deref_copy(struct hlsl_ctx *ctx, struct hlsl_deref >>>> *deref, struct hlsl_deref *other) >>>> +{ >>>> + unsigned int i; >>>> + >>>> + memset(deref, 0, sizeof(*deref)); >>>> + >>>> + if (!other) >>>> + return true; >>>> + >>>> + assert(!other->offset.node); >>>> + >>>> + if (!init_deref(ctx, deref, other->var, other->path_len)) >>>> + return false; >>>> + >>>> + for (i = 0; i < deref->path_len; ++i) >>>> + hlsl_src_from_node(&deref->path[i], other->path[i].node); >>>> + >>>> + hlsl_src_from_node(&deref->offset, other->offset.node); >>> >>> You just asserted that other->offset.node is NULL and *deref was >>> initialized to zero, so that seems to be a noop, doesn't it? >>> >> >> Hmm, sorry, I am not sure I understand. >> Initializing *deref to zero shouldn't affect >> >> assert(!other->offset.node); >> >> The idea of this assertion is to ensure that the "other" deref is in >> the index path format instead of the register offset format. > > My point is that, given that you just asserted that other->offset.node > is NULL, the effect of "hlsl_src_from_node(&deref->offset, > other->offset.node)" would be to set deref->offset.node to NULL, but > that's already ensured by the memset(). Or maybe I am getting confused > on something trivial? > > Giovanni.

1 0

[PATCH vkd3d v3 05/17] vkd3d-shader/hlsl: Introduce add_load_component().
by Francisco Casas 04 Aug '22

04 Aug '22

Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> Signed-off-by: Giovanni Mascellani <gmascellani(a)codeweavers.com> --- v3: * Using hlsl_get_string_buffer() and hlsl_release_string_buffer(). Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- libs/vkd3d-shader/hlsl.y | 99 +++++++++++++++++++++++++++------------- 1 file changed, 68 insertions(+), 31 deletions(-) diff --git a/libs/vkd3d-shader/hlsl.y b/libs/vkd3d-shader/hlsl.y index bfafd981..3b3d3582 100644 --- a/libs/vkd3d-shader/hlsl.y +++ b/libs/vkd3d-shader/hlsl.y @@ -272,8 +272,8 @@ static bool implicit_compatible_data_types(struct hlsl_type *t1, struct hlsl_typ return false; } -static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, - struct hlsl_ir_node *offset, struct hlsl_type *data_type, const struct vkd3d_shader_location loc); +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, + unsigned int comp, const struct vkd3d_shader_location *loc); static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *node, struct hlsl_type *dst_type, const struct vkd3d_shader_location *loc) @@ -311,8 +311,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, for (dst_idx = 0; dst_idx < dst_type->dimx * dst_type->dimy; ++dst_idx) { - struct hlsl_type *src_scalar_type, *dst_scalar_type; - unsigned int src_idx, src_offset, dst_offset; + struct hlsl_type *dst_scalar_type; + unsigned int src_idx, dst_offset; struct hlsl_ir_store *store; struct hlsl_ir_constant *c; @@ -335,13 +335,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, } dst_offset = hlsl_compute_component_offset(ctx, dst_type, dst_idx, &dst_scalar_type); - src_offset = hlsl_compute_component_offset(ctx, src_type, src_idx, &src_scalar_type); - - if (!(c = hlsl_new_uint_constant(ctx, src_offset, loc))) - return NULL; - list_add_tail(instrs, &c->node.entry); - if (!(load = add_load(ctx, instrs, node, &c->node, src_scalar_type, *loc))) + if (!(load = add_load_component(ctx, instrs, node, src_idx, loc))) return NULL; if (!(cast = hlsl_new_cast(ctx, &load->node, dst_scalar_type, loc))) @@ -668,6 +663,63 @@ static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, return load; } +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, + unsigned int comp, const struct vkd3d_shader_location *loc) +{ + struct hlsl_type *comp_type; + struct hlsl_ir_node *offset; + struct hlsl_ir_constant *c; + struct hlsl_ir_load *load; + unsigned int comp_offset; + struct hlsl_ir_var *var; + + comp_offset = hlsl_compute_component_offset(ctx, var_node->data_type, comp, &comp_type); + + if (!(c = hlsl_new_uint_constant(ctx, comp_offset, loc))) + return NULL; + list_add_tail(instrs, &c->node.entry); + + offset = &c->node; + + if (var_node->type == HLSL_IR_LOAD) + { + const struct hlsl_deref *src = &hlsl_ir_load(var_node)->src; + struct hlsl_ir_node *add; + + var = src->var; + if (src->offset.node) + { + if (!(add = hlsl_new_binary_expr(ctx, HLSL_OP2_ADD, src->offset.node, &c->node))) + return NULL; + list_add_tail(instrs, &add->entry); + offset = add; + } + } + else + { + struct vkd3d_string_buffer *name; + struct hlsl_ir_store *store; + + if (!(name = hlsl_get_string_buffer(ctx))) + return NULL; + vkd3d_string_buffer_printf(name, "<deref-%p>", var_node); + var = hlsl_new_synthetic_var(ctx, name->buffer, var_node->data_type, var_node->loc); + hlsl_release_string_buffer(ctx, name); + if (!var) + return NULL; + + if (!(store = hlsl_new_simple_store(ctx, var, var_node))) + return NULL; + list_add_tail(instrs, &store->node.entry); + } + + if (!(load = hlsl_new_load(ctx, var, offset, comp_type, *loc))) + return NULL; + list_add_tail(instrs, &load->node.entry); + + return load; +} + static bool add_record_load(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *record, unsigned int idx, const struct vkd3d_shader_location loc) { @@ -1766,22 +1818,17 @@ static void initialize_var_components(struct hlsl_ctx *ctx, struct list *instrs, for (k = 0; k < src_comp_count; ++k) { - struct hlsl_type *dst_comp_type, *src_comp_type; - unsigned int dst_reg_offset, src_reg_offset; + struct hlsl_type *dst_comp_type; + unsigned int dst_reg_offset; struct hlsl_ir_store *store; struct hlsl_ir_constant *c; struct hlsl_ir_load *load; struct hlsl_ir_node *conv; - dst_reg_offset = hlsl_compute_component_offset(ctx, dst->data_type, *store_index, &dst_comp_type); - src_reg_offset = hlsl_compute_component_offset(ctx, src->data_type, k, &src_comp_type); - - if (!(c = hlsl_new_uint_constant(ctx, src_reg_offset, &src->loc))) + if (!(load = add_load_component(ctx, instrs, src, k, &src->loc))) return; - list_add_tail(instrs, &c->node.entry); - if (!(load = add_load(ctx, instrs, src, &c->node, src_comp_type, src->loc))) - return; + dst_reg_offset = hlsl_compute_component_offset(ctx, dst->data_type, *store_index, &dst_comp_type); if (!(conv = add_implicit_conversion(ctx, instrs, &load->node, dst_comp_type, &src->loc))) return; @@ -2218,20 +2265,10 @@ static bool intrinsic_mul(struct hlsl_ctx *ctx, struct hlsl_ir_load *value1, *value2; struct hlsl_ir_node *mul; - offset = hlsl_compute_component_offset(ctx, cast_type1, j * cast_type1->dimx + k, &scalar_type); - if (!(c = hlsl_new_uint_constant(ctx, offset, loc))) - return false; - list_add_tail(params->instrs, &c->node.entry); - - if (!(value1 = add_load(ctx, params->instrs, cast1, &c->node, scalar_type, *loc))) - return false; - - offset = hlsl_compute_component_offset(ctx, cast_type2, k * cast_type2->dimx + i, &scalar_type); - if (!(c = hlsl_new_uint_constant(ctx, offset, loc))) + if (!(value1 = add_load_component(ctx, params->instrs, cast1, j * cast1->data_type->dimx + k, loc))) return false; - list_add_tail(params->instrs, &c->node.entry); - if (!(value2 = add_load(ctx, params->instrs, cast2, &c->node, scalar_type, *loc))) + if (!(value2 = add_load_component(ctx, params->instrs, cast2, k * cast2->data_type->dimx + i, loc))) return false; if (!(mul = add_binary_arithmetic_expr(ctx, params->instrs, HLSL_OP2_MUL, &value1->node, &value2->node, loc))) -- 2.34.1

5 31

Re: [PATCH v8 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin 04 Aug '22

04 Aug '22

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=120511 Your paranoid android. === w10pro64 (32 bit report) === user32: win.c:10984: Test failed: pos = 014a015e

1 0

Re: [PATCH v8 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 04 Aug '22

04 Aug '22

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=120510 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === user32: win.c:4592: Test failed: hwnd 00000000001F0326/00000000001F0326 message 0200 win.c:4595: Test failed: hwnd 00000000001F0326/00000000001F0326 message 0201 === w10pro64_ar (64 bit report) === user32: win.c:4641: Test failed: hwnd 00000000000B02D2/00000000000B02D2 message 0200 win.c:4643: Test failed: wparam 0 win.c:4654: Test failed: hwnd 00000000000B02D2/00000000000B02D2 message 0203 win.c:4658: Test failed: message 0202 available

1 0

[PATCH vkd3d 01/17] vkd3d-shader/hlsl: Store the struct fields as an array.
by Francisco Casas 03 Aug '22

03 Aug '22

From: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- v2: * No changes. --- libs/vkd3d-shader/hlsl.c | 123 +++++++++++++++---------------- libs/vkd3d-shader/hlsl.h | 10 ++- libs/vkd3d-shader/hlsl.y | 99 ++++++++++++++----------- libs/vkd3d-shader/hlsl_codegen.c | 18 +++-- libs/vkd3d-shader/hlsl_sm1.c | 13 +++- libs/vkd3d-shader/hlsl_sm4.c | 13 +++- 6 files changed, 150 insertions(+), 126 deletions(-) diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c index 7239b183..b349eb15 100644 --- a/libs/vkd3d-shader/hlsl.c +++ b/libs/vkd3d-shader/hlsl.c @@ -175,13 +175,14 @@ static void hlsl_type_calculate_reg_size(struct hlsl_ctx *ctx, struct hlsl_type case HLSL_CLASS_STRUCT: { - struct hlsl_struct_field *field; + unsigned int i; type->dimx = 0; type->reg_size = 0; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + struct hlsl_struct_field *field = &type->e.record.fields[i]; unsigned int field_size = field->type->reg_size; assert(field_size); @@ -282,10 +283,12 @@ unsigned int hlsl_compute_component_offset(struct hlsl_ctx *ctx, struct hlsl_typ case HLSL_CLASS_STRUCT: { struct hlsl_struct_field *field; + unsigned int elem_comp_count, i; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { - unsigned int elem_comp_count = hlsl_type_component_count(field->type); + field = &type->e.record.fields[i]; + elem_comp_count = hlsl_type_component_count(field->type); if (idx < elem_comp_count) { @@ -331,7 +334,8 @@ struct hlsl_type *hlsl_new_array_type(struct hlsl_ctx *ctx, struct hlsl_type *ba return type; } -struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, struct list *fields) +struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, + struct hlsl_struct_field *fields, size_t field_count) { struct hlsl_type *type; @@ -341,7 +345,8 @@ struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, s type->base_type = HLSL_TYPE_VOID; type->name = name; type->dimy = 1; - type->e.elements = fields; + type->e.record.fields = fields; + type->e.record.field_count = field_count; hlsl_type_calculate_reg_size(ctx, type); list_add_tail(&ctx->types, &type->entry); @@ -401,8 +406,7 @@ struct hlsl_ir_function_decl *hlsl_get_func_decl(struct hlsl_ctx *ctx, const cha unsigned int hlsl_type_component_count(struct hlsl_type *type) { - struct hlsl_struct_field *field; - unsigned int count = 0; + unsigned int count = 0, i; if (type->type <= HLSL_CLASS_LAST_NUMERIC) { @@ -418,10 +422,8 @@ unsigned int hlsl_type_component_count(struct hlsl_type *type) return 0; } - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) - { - count += hlsl_type_component_count(field->type); - } + for (i = 0; i < type->e.record.field_count; ++i) + count += hlsl_type_component_count(type->e.record.fields[i].type); return count; } @@ -451,24 +453,22 @@ bool hlsl_types_are_equal(const struct hlsl_type *t1, const struct hlsl_type *t2 return false; if (t1->type == HLSL_CLASS_STRUCT) { - struct list *t1cur, *t2cur; - struct hlsl_struct_field *t1field, *t2field; + size_t i; + + if (t1->e.record.field_count != t2->e.record.field_count) + return false; - t1cur = list_head(t1->e.elements); - t2cur = list_head(t2->e.elements); - while (t1cur && t2cur) + for (i = 0; i < t1->e.record.field_count; ++i) { - t1field = LIST_ENTRY(t1cur, struct hlsl_struct_field, entry); - t2field = LIST_ENTRY(t2cur, struct hlsl_struct_field, entry); - if (!hlsl_types_are_equal(t1field->type, t2field->type)) + const struct hlsl_struct_field *field1 = &t1->e.record.fields[i]; + const struct hlsl_struct_field *field2 = &t2->e.record.fields[i]; + + if (!hlsl_types_are_equal(field1->type, field2->type)) return false; - if (strcmp(t1field->name, t2field->name)) + + if (strcmp(field1->name, field2->name)) return false; - t1cur = list_next(t1->e.elements, t1cur); - t2cur = list_next(t2->e.elements, t2cur); } - if (t1cur != t2cur) - return false; } if (t1->type == HLSL_CLASS_ARRAY) return t1->e.array.elements_count == t2->e.array.elements_count @@ -480,7 +480,6 @@ bool hlsl_types_are_equal(const struct hlsl_type *t1, const struct hlsl_type *t2 struct hlsl_type *hlsl_type_clone(struct hlsl_ctx *ctx, struct hlsl_type *old, unsigned int default_majority, unsigned int modifiers) { - struct hlsl_struct_field *old_field, *field; struct hlsl_type *type; if (!(type = hlsl_alloc(ctx, sizeof(*type)))) @@ -512,37 +511,30 @@ struct hlsl_type *hlsl_type_clone(struct hlsl_ctx *ctx, struct hlsl_type *old, case HLSL_CLASS_STRUCT: { - if (!(type->e.elements = hlsl_alloc(ctx, sizeof(*type->e.elements)))) + size_t field_count = old->e.record.field_count, i; + + type->e.record.field_count = field_count; + + if (!(type->e.record.fields = hlsl_alloc(ctx, field_count * sizeof(*type->e.record.fields)))) { vkd3d_free((void *)type->name); vkd3d_free(type); return NULL; } - list_init(type->e.elements); - LIST_FOR_EACH_ENTRY(old_field, old->e.elements, struct hlsl_struct_field, entry) + + for (i = 0; i < field_count; ++i) { - if (!(field = hlsl_alloc(ctx, sizeof(*field)))) - { - LIST_FOR_EACH_ENTRY_SAFE(field, old_field, type->e.elements, struct hlsl_struct_field, entry) - { - vkd3d_free((void *)field->semantic.name); - vkd3d_free((void *)field->name); - vkd3d_free(field); - } - vkd3d_free(type->e.elements); - vkd3d_free((void *)type->name); - vkd3d_free(type); - return NULL; - } - field->loc = old_field->loc; - field->type = hlsl_type_clone(ctx, old_field->type, default_majority, modifiers); - field->name = hlsl_strdup(ctx, old_field->name); - if (old_field->semantic.name) + const struct hlsl_struct_field *src_field = &old->e.record.fields[i]; + struct hlsl_struct_field *dst_field = &type->e.record.fields[i]; + + dst_field->loc = src_field->loc; + dst_field->type = hlsl_type_clone(ctx, src_field->type, default_majority, modifiers); + dst_field->name = hlsl_strdup(ctx, src_field->name); + if (src_field->semantic.name) { - field->semantic.name = hlsl_strdup(ctx, old_field->semantic.name); - field->semantic.index = old_field->semantic.index; + dst_field->semantic.name = hlsl_strdup(ctx, src_field->semantic.name); + dst_field->semantic.index = src_field->semantic.index; } - list_add_tail(type->e.elements, &field->entry); } break; } @@ -911,24 +903,22 @@ static int compare_param_hlsl_types(const struct hlsl_type *t1, const struct hls return r; if (t1->type == HLSL_CLASS_STRUCT) { - struct list *t1cur, *t2cur; - struct hlsl_struct_field *t1field, *t2field; + size_t i; - t1cur = list_head(t1->e.elements); - t2cur = list_head(t2->e.elements); - while (t1cur && t2cur) + if (t1->e.record.field_count != t2->e.record.field_count) + return t1->e.record.field_count - t2->e.record.field_count; + + for (i = 0; i < t1->e.record.field_count; ++i) { - t1field = LIST_ENTRY(t1cur, struct hlsl_struct_field, entry); - t2field = LIST_ENTRY(t2cur, struct hlsl_struct_field, entry); - if ((r = compare_param_hlsl_types(t1field->type, t2field->type))) + const struct hlsl_struct_field *field1 = &t1->e.record.fields[i]; + const struct hlsl_struct_field *field2 = &t2->e.record.fields[i]; + + if ((r = compare_param_hlsl_types(field1->type, field2->type))) return r; - if ((r = strcmp(t1field->name, t2field->name))) + + if ((r = strcmp(field1->name, field2->name))) return r; - t1cur = list_next(t1->e.elements, t1cur); - t2cur = list_next(t2->e.elements, t2cur); } - if (t1cur != t2cur) - return t1cur ? 1 : -1; return 0; } if (t1->type == HLSL_CLASS_ARRAY) @@ -1519,17 +1509,20 @@ void hlsl_replace_node(struct hlsl_ir_node *old, struct hlsl_ir_node *new) void hlsl_free_type(struct hlsl_type *type) { - struct hlsl_struct_field *field, *next_field; + struct hlsl_struct_field *field; + size_t i; vkd3d_free((void *)type->name); if (type->type == HLSL_CLASS_STRUCT) { - LIST_FOR_EACH_ENTRY_SAFE(field, next_field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + field = &type->e.record.fields[i]; + vkd3d_free((void *)field->name); vkd3d_free((void *)field->semantic.name); - vkd3d_free(field); } + vkd3d_free((void *)type->e.record.fields); } vkd3d_free(type); } diff --git a/libs/vkd3d-shader/hlsl.h b/libs/vkd3d-shader/hlsl.h index 3c1dd08d..ce1f69df 100644 --- a/libs/vkd3d-shader/hlsl.h +++ b/libs/vkd3d-shader/hlsl.h @@ -126,7 +126,11 @@ struct hlsl_type unsigned int dimy; union { - struct list *elements; + struct + { + struct hlsl_struct_field *fields; + size_t field_count; + } record; struct { struct hlsl_type *type; @@ -147,7 +151,6 @@ struct hlsl_semantic struct hlsl_struct_field { - struct list entry; struct vkd3d_shader_location loc; struct hlsl_type *type; const char *name; @@ -752,7 +755,8 @@ struct hlsl_ir_resource_load *hlsl_new_resource_load(struct hlsl_ctx *ctx, struc struct hlsl_ir_store *hlsl_new_simple_store(struct hlsl_ctx *ctx, struct hlsl_ir_var *lhs, struct hlsl_ir_node *rhs); struct hlsl_ir_store *hlsl_new_store(struct hlsl_ctx *ctx, struct hlsl_ir_var *var, struct hlsl_ir_node *offset, struct hlsl_ir_node *rhs, unsigned int writemask, struct vkd3d_shader_location loc); -struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, struct list *fields); +struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, + struct hlsl_struct_field *fields, size_t field_count); struct hlsl_ir_swizzle *hlsl_new_swizzle(struct hlsl_ctx *ctx, DWORD s, unsigned int components, struct hlsl_ir_node *val, const struct vkd3d_shader_location *loc); struct hlsl_ir_var *hlsl_new_synthetic_var(struct hlsl_ctx *ctx, const char *name, struct hlsl_type *type, diff --git a/libs/vkd3d-shader/hlsl.y b/libs/vkd3d-shader/hlsl.y index 09a01c6d..f293b82e 100644 --- a/libs/vkd3d-shader/hlsl.y +++ b/libs/vkd3d-shader/hlsl.y @@ -28,6 +28,12 @@ #define HLSL_YYLTYPE struct vkd3d_shader_location +struct parse_fields +{ + struct hlsl_struct_field *fields; + size_t count, capacity; +}; + struct parse_parameter { struct hlsl_type *type; @@ -799,14 +805,15 @@ static bool add_array_load(struct hlsl_ctx *ctx, struct list *instrs, struct hls return !!add_load(ctx, instrs, array, index, data_type, loc); } -static struct hlsl_struct_field *get_struct_field(struct list *fields, const char *name) +static const struct hlsl_struct_field *get_struct_field(const struct hlsl_struct_field *fields, + size_t count, const char *name) { - struct hlsl_struct_field *f; + size_t i; - LIST_FOR_EACH_ENTRY(f, fields, struct hlsl_struct_field, entry) + for (i = 0; i < count; ++i) { - if (!strcmp(f->name, name)) - return f; + if (!strcmp(fields[i].name, name)) + return &fields[i]; } return NULL; } @@ -857,31 +864,28 @@ static void free_parse_variable_def(struct parse_variable_def *v) vkd3d_free(v); } -static struct list *gen_struct_fields(struct hlsl_ctx *ctx, - struct hlsl_type *type, unsigned int modifiers, struct list *fields) +static bool gen_struct_fields(struct hlsl_ctx *ctx, struct parse_fields *fields, + struct hlsl_type *type, unsigned int modifiers, struct list *defs) { struct parse_variable_def *v, *v_next; - struct hlsl_struct_field *field; - struct list *list; + size_t i = 0; if (type->type == HLSL_CLASS_MATRIX) assert(type->modifiers & HLSL_MODIFIERS_MAJORITY_MASK); - if (!(list = make_empty_list(ctx))) - return NULL; - LIST_FOR_EACH_ENTRY_SAFE(v, v_next, fields, struct parse_variable_def, entry) - { - unsigned int i; + memset(fields, 0, sizeof(*fields)); + fields->count = list_count(defs); + if (!hlsl_array_reserve(ctx, (void **)&fields->fields, &fields->capacity, fields->count, sizeof(*fields->fields))) + return false; - if (!(field = hlsl_alloc(ctx, sizeof(*field)))) - { - free_parse_variable_def(v); - continue; - } + LIST_FOR_EACH_ENTRY_SAFE(v, v_next, defs, struct parse_variable_def, entry) + { + struct hlsl_struct_field *field = &fields->fields[i++]; + unsigned int j; field->type = type; - for (i = 0; i < v->arrays.count; ++i) - field->type = hlsl_new_array_type(ctx, field->type, v->arrays.sizes[i]); + for (j = 0; j < v->arrays.count; ++j) + field->type = hlsl_new_array_type(ctx, field->type, v->arrays.sizes[j]); vkd3d_free(v->arrays.sizes); field->loc = v->loc; field->name = v->name; @@ -892,11 +896,10 @@ static struct list *gen_struct_fields(struct hlsl_ctx *ctx, hlsl_error(ctx, &v->loc, VKD3D_SHADER_ERROR_HLSL_INVALID_SYNTAX, "Illegal initializer on a struct field."); free_parse_initializer(&v->initializer); } - list_add_tail(list, &field->entry); vkd3d_free(v); } - vkd3d_free(fields); - return list; + vkd3d_free(defs); + return true; } static bool add_typedef(struct hlsl_ctx *ctx, DWORD modifiers, struct hlsl_type *orig_type, struct list *list) @@ -2681,6 +2684,7 @@ static bool add_method_call(struct hlsl_ctx *ctx, struct list *instrs, struct hl DWORD modifiers; struct hlsl_ir_node *instr; struct list *list; + struct parse_fields fields; struct parse_function function; struct parse_parameter parameter; struct parse_initializer initializer; @@ -2809,8 +2813,6 @@ static bool add_method_call(struct hlsl_ctx *ctx, struct list *instrs, struct hl %type <list> equality_expr %type <list> expr %type <list> expr_statement -%type <list> field -%type <list> fields_list %type <list> initializer_expr %type <list> jump_statement %type <list> logicand_expr @@ -2847,6 +2849,9 @@ static bool add_method_call(struct hlsl_ctx *ctx, struct list *instrs, struct hl %type <colon_attribute> colon_attribute +%type <fields> field +%type <fields> fields_list + %type <function> func_declaration %type <function> func_prototype @@ -3002,7 +3007,7 @@ named_struct_spec: { bool ret; - $$ = hlsl_new_struct_type(ctx, $2, $4); + $$ = hlsl_new_struct_type(ctx, $2, $4.fields, $4.count); if (hlsl_get_var(ctx->cur_scope, $2)) { @@ -3021,7 +3026,7 @@ named_struct_spec: unnamed_struct_spec: KW_STRUCT '{' fields_list '}' { - $$ = hlsl_new_struct_type(ctx, NULL, $3); + $$ = hlsl_new_struct_type(ctx, NULL, $3.fields, $3.count); } any_identifier: @@ -3032,30 +3037,35 @@ any_identifier: fields_list: %empty { - if (!($$ = make_empty_list(ctx))) - YYABORT; + $$.fields = NULL; + $$.count = 0; + $$.capacity = 0; } | fields_list field { - struct hlsl_struct_field *field, *next, *existing; + size_t i; - $$ = $1; - LIST_FOR_EACH_ENTRY_SAFE(field, next, $2, struct hlsl_struct_field, entry) + for (i = 0; i < $2.count; ++i) { - if ((existing = get_struct_field($$, field->name))) + const struct hlsl_struct_field *field = &$2.fields[i]; + const struct hlsl_struct_field *existing; + + if ((existing = get_struct_field($1.fields, $1.count, field->name))) { - hlsl_error(ctx, &@2, VKD3D_SHADER_ERROR_HLSL_REDEFINED, + hlsl_error(ctx, &field->loc, VKD3D_SHADER_ERROR_HLSL_REDEFINED, "Field \"%s\" is already defined.", field->name); hlsl_note(ctx, &existing->loc, VKD3D_SHADER_LOG_ERROR, "'%s' was previously defined here.", field->name); - vkd3d_free(field); - } - else - { - list_add_tail($$, &field->entry); } } - vkd3d_free($2); + + if (!hlsl_array_reserve(ctx, (void **)&$1.fields, &$1.capacity, $1.count + $2.count, sizeof(*$1.fields))) + YYABORT; + memcpy($1.fields + $1.count, $2.fields, $2.count * sizeof(*$2.fields)); + $1.count += $2.count; + vkd3d_free($2.fields); + + $$ = $1; } field_type: @@ -3079,7 +3089,8 @@ field: "Modifiers '%s' are not allowed on struct fields.", string->buffer); hlsl_release_string_buffer(ctx, string); } - $$ = gen_struct_fields(ctx, type, modifiers, $3); + if (!gen_struct_fields(ctx, &$$, type, modifiers, $3)) + YYABORT; } func_declaration: @@ -3936,9 +3947,9 @@ postfix_expr: if (node->data_type->type == HLSL_CLASS_STRUCT) { struct hlsl_type *type = node->data_type; - struct hlsl_struct_field *field; + const struct hlsl_struct_field *field; - if (!(field = get_struct_field(type->e.elements, $3))) + if (!(field = get_struct_field(type->e.record.fields, type->e.record.field_count, $3))) { hlsl_error(ctx, &@3, VKD3D_SHADER_ERROR_HLSL_NOT_DEFINED, "Field \"%s\" is not defined.", $3); YYABORT; diff --git a/libs/vkd3d-shader/hlsl_codegen.c b/libs/vkd3d-shader/hlsl_codegen.c index bc7f0a62..484b415d 100644 --- a/libs/vkd3d-shader/hlsl_codegen.c +++ b/libs/vkd3d-shader/hlsl_codegen.c @@ -137,10 +137,12 @@ static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct static void prepend_input_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, struct hlsl_type *type, unsigned int field_offset) { - struct hlsl_struct_field *field; + size_t i; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + const struct hlsl_struct_field *field = &type->e.record.fields[i]; + if (field->type->type == HLSL_CLASS_STRUCT) prepend_input_struct_copy(ctx, instrs, var, field->type, field_offset + field->reg_offset); else if (field->semantic.name) @@ -225,10 +227,12 @@ static void append_output_copy(struct hlsl_ctx *ctx, struct list *instrs, struct static void append_output_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, struct hlsl_type *type, unsigned int field_offset) { - struct hlsl_struct_field *field; + size_t i; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + const struct hlsl_struct_field *field = &type->e.record.fields[i]; + if (field->type->type == HLSL_CLASS_STRUCT) append_output_struct_copy(ctx, instrs, var, field->type, field_offset + field->reg_offset); else if (field->semantic.name) @@ -859,10 +863,10 @@ static bool split_array_copies(struct hlsl_ctx *ctx, struct hlsl_ir_node *instr, static bool split_struct_copies(struct hlsl_ctx *ctx, struct hlsl_ir_node *instr, void *context) { - const struct hlsl_struct_field *field; const struct hlsl_ir_node *rhs; const struct hlsl_type *type; struct hlsl_ir_store *store; + size_t i; if (instr->type != HLSL_IR_STORE) return false; @@ -879,8 +883,10 @@ static bool split_struct_copies(struct hlsl_ctx *ctx, struct hlsl_ir_node *instr return false; } - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + const struct hlsl_struct_field *field = &type->e.record.fields[i]; + if (!split_copy(ctx, store, hlsl_ir_load(rhs), field->reg_offset, field->type)) return false; } diff --git a/libs/vkd3d-shader/hlsl_sm1.c b/libs/vkd3d-shader/hlsl_sm1.c index 0cdd3917..06313a42 100644 --- a/libs/vkd3d-shader/hlsl_sm1.c +++ b/libs/vkd3d-shader/hlsl_sm1.c @@ -243,28 +243,33 @@ static void write_sm1_type(struct vkd3d_bytecode_buffer *buffer, struct hlsl_typ { const struct hlsl_type *array_type = get_array_type(type); unsigned int array_size = get_array_size(type); - struct hlsl_struct_field *field; unsigned int field_count = 0; size_t fields_offset = 0; + size_t i; if (type->bytecode_offset) return; if (array_type->type == HLSL_CLASS_STRUCT) { - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + field_count = array_type->e.record.field_count; + + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + field->name_bytecode_offset = put_string(buffer, field->name); write_sm1_type(buffer, field->type, ctab_start); } fields_offset = bytecode_get_size(buffer) - ctab_start; - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + put_u32(buffer, field->name_bytecode_offset - ctab_start); put_u32(buffer, field->type->bytecode_offset - ctab_start); - ++field_count; } } diff --git a/libs/vkd3d-shader/hlsl_sm4.c b/libs/vkd3d-shader/hlsl_sm4.c index 79027169..7758555b 100644 --- a/libs/vkd3d-shader/hlsl_sm4.c +++ b/libs/vkd3d-shader/hlsl_sm4.c @@ -355,7 +355,7 @@ static void write_sm4_type(struct hlsl_ctx *ctx, struct vkd3d_bytecode_buffer *b const struct hlsl_profile_info *profile = ctx->profile; unsigned int field_count = 0, array_size = 0; size_t fields_offset = 0, name_offset = 0; - struct hlsl_struct_field *field; + size_t i; if (type->bytecode_offset) return; @@ -368,20 +368,25 @@ static void write_sm4_type(struct hlsl_ctx *ctx, struct vkd3d_bytecode_buffer *b if (array_type->type == HLSL_CLASS_STRUCT) { - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + field_count = array_type->e.record.field_count; + + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + field->name_bytecode_offset = put_string(buffer, field->name); write_sm4_type(ctx, buffer, field->type); } fields_offset = bytecode_get_size(buffer); - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + put_u32(buffer, field->name_bytecode_offset); put_u32(buffer, field->type->bytecode_offset); put_u32(buffer, field->reg_offset); - ++field_count; } } -- 2.34.1

6 50

Re: [PATCH 2/2] mshtml: Implement targetOrigin for postMessage.
by Marvin 03 Aug '22

03 Aug '22

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=120464 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

1 0

Re: [PATCH 2/5] d3d9/tests: Expand tests for valid pools in UpdateTexture().
by Marvin 03 Aug '22

03 Aug '22

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=120466 Your paranoid android. === w8 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w8adm (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w864 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1507 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1809 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_tsign (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w864 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1507 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1809 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_2qxl (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. device.c:14775: Test failed: Adapter 1: Expect window rect (1024,0)-(2304,800), got (0,0)-(1280,800). === w1064_adm (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_tsign (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_en_AE_u8 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_ar (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_ja (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_zh_CN (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === debian11 (64 bit WoW report) === d3d9: device: Timeout

1 0

Re: [PATCH 1/5] d3d8/tests: Expand tests for valid pools in UpdateTexture().
by Marvin 03 Aug '22

03 Aug '22

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=120465 Your paranoid android. === w1064v1507 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === w1064v1809 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === w10pro64 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === debian11 (32 bit report) === d3d8: Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b859f). === debian11 (32 bit German report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (32 bit French report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (32 bit Chinese:China report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (64 bit WoW report) === d3d8: Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000000712b2dce).

1 0

Re: [PATCH 2/3] dlls/urlmon/tests: Don't use read as a global variable.
by Marvin 03 Aug '22

03 Aug '22

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=120438 Your paranoid android. === w1064v1507 (32 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064_adm (64 bit report) === urlmon: url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 === debian11 (32 bit report) === urlmon: url.c:1654: Test failed: unexpected call OnProgress_CONNECTING url.c:1466: Test failed: progress 2: status = 302

1 0

Re: [PATCH 7/7] win32u: Move display placement logic out of graphics drivers.
by Marvin 03 Aug '22

03 Aug '22

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=120436 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 error: patch failed: dlls/winex11.drv/display.c:390 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 error: patch failed: dlls/winex11.drv/display.c:390 Task: Patch failed to apply

1 0

Re: [PATCH 6/7] win32u: Use current mode position if desired mode doesn't specify it.
by Marvin 03 Aug '22

03 Aug '22

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=120435 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 Task: Patch failed to apply

1 0

Re: [PATCH 5/7] win32u: Validate NtUserChangeDisplaySettings mode against available modes.
by Marvin 03 Aug '22

03 Aug '22

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=120434 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 Task: Patch failed to apply

1 0

Re: [PATCH 6/6] mf: Propagate missing attributes to downstream media types.
by Marvin 03 Aug '22

03 Aug '22

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=120429 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 5/6] mf: Use the MFT_CATEGORY_VIDEO_PROCESSOR category for converters.
by Marvin 03 Aug '22

03 Aug '22

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=120428 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 4/6] winegstreamer: Better implement Video Processor MFT.
by Marvin 03 Aug '22

03 Aug '22

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=120427 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 3/6] mf/tests: Add topology loader tests with video formats.
by Marvin 03 Aug '22

03 Aug '22

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=120426 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 2/6] mf/tests: Add video processor conversion tests.
by Marvin 03 Aug '22

03 Aug '22

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=120425 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 1/6] mf/tests: Rotate test videos 90° to better show vertical flips.
by Marvin 03 Aug '22

03 Aug '22

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=120424 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH v15 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin 02 Aug '22

02 Aug '22

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=120358 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v14 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin 02 Aug '22

02 Aug '22

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=120357 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v12 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin 02 Aug '22

02 Aug '22

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=120356 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v11 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin 02 Aug '22

02 Aug '22

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=120355 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === debian11 (32 bit report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v10 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin 02 Aug '22

02 Aug '22

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=120354 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v9 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) Dl
by Marvin 02 Aug '22

02 Aug '22

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=120351 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127.

1 0

Re: [PATCH v2 4/7] ws2_32/tests: Work around a Linux bug.
by Marvin 02 Aug '22

02 Aug '22

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=120345 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8699: Test failed: got 0

1 0

Re: [PATCH v2 3/7] ws2_32/tests: Test send() after TCP reset.
by Marvin 02 Aug '22

02 Aug '22

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=120344 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

1 0

Re: [PATCH v2 1/7] ws2_32/tests: Test sending data to a peer is closed().
by Marvin 02 Aug '22

02 Aug '22

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=120342 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

1 0

Re: [PATCH v6 3/3] cabinet: Implement GetDllVersion implement GetDllVersion, use DllGetVersion as helper function to retreiv
by Marvin 01 Aug '22

01 Aug '22

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=120332 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

1 0

Re: [PATCH v6 2/3] cabinet: implement DllGetVersion correctly implement DllGetVersion with correct parameter and behaviour c
by Marvin 01 Aug '22

01 Aug '22

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=120331 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

1 0

Re: [PATCH v6 1/3] cabinet: test GetDllVersion & DllGetVersion Tests are expected to fail as: DllGetVersion isn't implemente
by Marvin 01 Aug '22

01 Aug '22

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=120330 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH 3/3] mshtml: Implement MediaQueryList's matches prop.
by Marvin 01 Aug '22

01 Aug '22

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=120307 Your paranoid android. === w1064v1809 (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH 2/3] mshtml: Implement MediaQueryList's media prop.
by Marvin 01 Aug '22

01 Aug '22

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=120306 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

1 0

Re: [PATCH 6/6] widl: Use a struct list for the import stack.
by Marvin 01 Aug '22

01 Aug '22

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=120323 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 5/6] widl: Simplify handling of already parsed imports.
by Marvin 01 Aug '22

01 Aug '22

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=120322 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 4/6] widl: Use a struct list to keep imported files.
by Marvin 01 Aug '22

01 Aug '22

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=120321 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 3/6] widl: Move output generation calls out of parser.y.
by Marvin 01 Aug '22

01 Aug '22

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=120320 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 1/3] mshtml: Implement window.matchMedia() with MediaQueryList stub.
by Marvin 01 Aug '22

01 Aug '22

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=120305 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE === w10pro64_ja (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH 2/3] shell32: Add SHBindToFolderIDListParent tests.
by Marvin 01 Aug '22

01 Aug '22

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=120263 Your paranoid android. === w1064v1809 (64 bit report) === shell32: shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064_tsign (64 bit report) === shell32: shlfolder.c:5009: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w10pro64_zh_CN (64 bit report) === shell32: shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH v2 2/4] bcrypt/tests: Test for BCryptEncrypt with RSA keys.
by Marvin 31 Jul '22

31 Jul '22

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=120255 Your paranoid android. === debian11 (32 bit report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Arabic:Morocco report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit German report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit French report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hebrew:Israel report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hindi:India report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Japanese:Japan report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Chinese:China report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (64 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same

1 0

Re: [PATCH 2/4] bcrypt/tests: Test for BCryptEncrypt with RSA keys.
by Marvin 31 Jul '22

31 Jul '22

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=120251 Your paranoid android. === debian11 (32 bit report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Arabic:Morocco report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit German report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit French report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hebrew:Israel report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Hindi:India report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Japanese:Japan report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit Chinese:China report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (32 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same === debian11 (64 bit WoW report) === bcrypt: bcrypt.c:2083: Test failed: got c0000002 bcrypt.c:2084: Test failed: got size of 60 bcrypt.c:2092: Test failed: got c0000002 bcrypt.c:2094: Test failed: got c0000002 bcrypt.c:2095: Test failed: Both outputs are the same

1 0

Re: [PATCH v2 1/1] cabinet.dll: implement DllGetVersion & GetDllVersion Fix stub DllGetVersion implementation to read Dll ve
by Marvin 31 Jul '22

31 Jul '22

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=120249 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 1/1] cabinet.dll: implement DllGetVersion & GetDllVersion Fix stub DllGetVersion implementation to read Dll versi
by Marvin 31 Jul '22

31 Jul '22

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=120247 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w8 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w8adm (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w864 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w864 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:55: Test failed: Size of cabinet version structure incorrect: Error = 203. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

1 0

Re: [PATCH v2 01/11] winmm/tests: Add tests for visibility of video window.
by Marvin 31 Jul '22

31 Jul '22

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=120234 Your paranoid android. === w8 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v2 05/11] winmm/tests: Add tests for destination of video window.
by Marvin 31 Jul '22

31 Jul '22

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=120238 Your paranoid android. === debian11 (32 bit report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit German report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit French report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) === debian11 (32 bit WoW report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (64 bit WoW report) === winmm: mci.c:1606: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1606: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1606: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51)

1 0

Re: [PATCH v2 04/11] winmm/tests: Add tests for dimensions of video window.
by Marvin 31 Jul '22

31 Jul '22

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=120237 Your paranoid android. === debian11 (32 bit report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit German report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit French report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,10)-(112,61), got (0,10)-(112,61) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(113,52), got (0,0)-(113,52) === debian11 (32 bit WoW report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) === debian11 (64 bit WoW report) === winmm: mci.c:1601: Test succeeded inside todo block: 0: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 2: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51) mci.c:1601: Test succeeded inside todo block: 3: window rectangle doesn't match, expected (0,0)-(112,51), got (0,0)-(112,51)

1 0

Re: [PATCH v2 7/7] xactengine3_7: Return error on invalid notification value.
by Marvin 31 Jul '22

31 Jul '22

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=120222 Your paranoid android. === debian11 (32 bit report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Arabic:Morocco report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit German report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit French report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Hebrew:Israel report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Hindi:India report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Japanese:Japan report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit Chinese:China report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (32 bit WoW report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received === debian11 (64 bit WoW report) === xactengine3_7: xact3.c:215: Test failed: got hr 0 xact3.c:218: Test failed: got hr 0 xact3.c:224: Test failed: got hr 0 xact3.c:227: Test failed: got hr 0 xact3.c:272: Test failed: The 'wave bank prepared' notification was never received xact3.c:276: Test failed: The 'wave bank destroyed' notification was never received

1 0

[PATCH] fltlib: Add fixme stub for FilterSendMessage.
by Chao Long 31 Jul '22

31 Jul '22

Signed-off-by: Chao Long <longchao(a)uniontech.com> --- dlls/fltlib/fltlib.c | 11 +++++++++++ dlls/fltlib/fltlib.spec | 2 +- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/dlls/fltlib/fltlib.c b/dlls/fltlib/fltlib.c index a6cf060b3d1..a322e7559de 100644 --- a/dlls/fltlib/fltlib.c +++ b/dlls/fltlib/fltlib.c @@ -80,3 +80,14 @@ HRESULT WINAPI FilterUnload(LPCWSTR filtername) return S_OK; } + +/********************************************************************** + * FilterSendMessage (FLTLIB.@) + */ +HRESULT WINAPI FilterSendMessage(HANDLE port, LPVOID in_buffer, DWORD in_size, LPVOID out_buffer, + DWORD out_size, LPDWORD returned) +{ + FIXME("(%p, %p, %d, %p, %d, %p) stub\n", port,in_buffer,in_size,out_buffer,out_size,returned); + + return S_OK; +} \ No newline at end of file diff --git a/dlls/fltlib/fltlib.spec b/dlls/fltlib/fltlib.spec index 226a61519d1..48caa505a28 100644 --- a/dlls/fltlib/fltlib.spec +++ b/dlls/fltlib/fltlib.spec @@ -18,7 +18,7 @@ @ stub FilterInstanceGetInformation @ stdcall FilterLoad(wstr) @ stub FilterReplyMessage -@ stub FilterSendMessage +@ stdcall FilterSendMessage(ptr ptr long ptr long ptr) @ stdcall FilterUnload(wstr) @ stub FilterVolumeClose @ stub FilterVolumeFindClose -- 2.20.1

2 1

Wine staging 7.14 release
by Alistair Leslie-Hughes 30 Jul '22

30 Jul '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.14 (537 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * xactengine3.7: Delay Notication for WAVEBANKPREPARED * ntdll: Check return parameter before use * ntdll: RtlFirstFreeAce only return FALSE on error * xactengine3_7: Remove Entry after FAudio Destroyed call Added: * None Updated: * xactengine3_7-Notification * xactengine3_7-callbacks 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

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