- Wine-Devel - list.winehq.org

8.0 release notes (draft)
by Alexandre Julliard Jan. 25, 2023

Jan. 25, 2023

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 Jan. 25, 2023

Jan. 25, 2023

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 Jan. 25, 2023

Jan. 25, 2023

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 Jan. 25, 2023

Jan. 25, 2023

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 release
by Alistair Leslie-Hughes Jan. 24, 2023

Jan. 24, 2023

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

Wine staging 8.0-rc4 release
by Alistair Leslie-Hughes Jan. 15, 2023

Jan. 15, 2023

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 Jan. 9, 2023

Jan. 9, 2023

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 Jan. 7, 2023

Jan. 7, 2023

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 Jan. 6, 2023

Jan. 6, 2023

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 Dec. 28, 2022

Dec. 28, 2022

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