Language Selection

English French German Italian Portuguese Spanish

Wine 5.7 Released

Filed under
  • Wine Announcement
    The Wine development release 5.7 is now available.
    What's new in this release (see below for details):
      - Wine Mono engine updated to 5.0.0, with upstream WPF support.
      - More progress on the WineD3D Vulkan backend.
      - Beginnings of a USB device driver.
      - Support for building with Clang in MSVC mode.
      - Builtin modules no longer depend on libwine.
      - Support for configuring Windows version from the command line.
      - Various bug fixes.
    The source is available from the following locations:
    Binary packages for various distributions will be available from:
    You will find documentation on
    You can also get the current source directly from the git
    repository. Check for details.
    Wine is available thanks to the work of many people. See the file
    AUTHORS in the distribution for the complete list.
  • Wine 5.7 is out with more WineD3D Vulkan work, a start on a USB device driver

    The Wine compatibility layer has another development release out today with Wine 5.7 adding in some new features.

  • Wine 5.7 Released With More Progress On D3D Vulkan Backend, USB Device Driver

    Wine 5.7 is out as the newest bi-weekly development release and it's a fun one with multiple interesting advancements.

    As reported a few days ago, there has been progress on the WineD3D Vulkan back-end for allowing D3D9/D3D10/D3D11 calls to go through Vulkan rather than OpenGL. It's similar aim to DXVK but not nearly as mature. The Vulkan support for WineD3D is still being brought up and isn't yet ready for end-users/gamers but progress is being made.

Wine-Staging 5.7 Fixes Support For Applications Built Using .NET

  • Wine-Staging 5.7 Fixes Support For Applications Built Using .NET CoreRT

    Built off yesterday's exciting Wine 5.7 release that brought more WineD3D Vulkan bits and the start of a USB driver, Wine-Staging 5.7 is out with a number of its patches upstreamed into yesterday's release plus a bit of new functionality.

    Wine-Staging 5.7 is down to less than 850 patches atop the upstream Wine code-base. Wine 5.7 upstreamed a number of the staging patches around Windows Codecs, NTDLL, and other bits to lighten the delta carried in the staging area.

    But in addition to Wine-Staging 5.7 updating their NTDLL syscall emulation and raw input mouse handling code, there is a fix in this release for running Windows applications built using .NET CoreRT.

Wine Patches Cleaned Up, Out For Review On Very Early POWER...

  • Wine Patches Cleaned Up, Out For Review On Very Early POWER 64-Bit Support

    With the Raptor Blackbird popular among open-source enthusiasts for a libre 64-bit Linux desktop compute and that getting more POWER9 hardware out in the wild, more users are interested in seeing Wine work for 64-bit POWER hardware. Last year was some early porting work done by Raptor Computing Systems but now a cleaned up patch series has been sent out with this very primitive PPC64 work.

    Besides these patches out for review being very primitive and far from a complete POWER Wine port, it does lay the foundation for more work to happen. But it's also important to note the focus here is on Winelib support for POWER due to Wine itself not handling CPU emulation for say directly running x86_64 Windows binaries from a shiny POWER9 Blackbird desktop.

Wine-Staging 5.9 Picks Up A Patch...

  • Wine-Staging 5.9 Picks Up A Patch In The Effort To Deal With Denuvo Anti-Cheat

    Just hours after the release of Wine 5.9, the latest staging release is now available that is re-based to the latest upstream while continuing to toss in over eight hundred extra patches.

    Wine-Staging 5.8 was losing weight thanks to upstreaming a number of patches and that trend continued with the new Wine-Staging 5.9. The Wine-Staging 5.9 release is around a 820 patch delta, compared to around ~850 patches generally being around the common delta size for staging. Over the past two weeks some of the staging work upstreamed were around USB support with timestamp updates, various NTDLL functions being implemented, PE handling improvements, and more.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Sunsetting XRandR Brightness

One of the first features I added back then was smooth brightness changes. PowerDevil supports three ways of changing screen brightness: through XRandR configuration, through DDC (display data channel, for desktop monitors, experimental and not built by default), and by writing to sysfs (/sys/class/backlight or /sys/class/leds). Since the latter requires privileges and uses a helper binary through KDE’s KAuth framework, I only implemented the animation for the XRandR code path, which was executed in the same process. Obviously, XRandR doesn’t work on Wayland, and it seems that modern graphics drivers don’t support changing brightness through it anymore either. I recently sat down and wrote a patch to have the helper binary execute a similar animation. KAuth works quite magically by exposing methods defined in an .actions file through DBus and then calling them as slots through Qt’s meta object. Unfortunately, the way it is designed doesn’t allow for delayed replies, which I wanted to use so the job only finished once the animation was completed in order to keep PowerDevil’s state consistent. I then found that KAuth randomly keeps its helper running for 10 seconds, more than enough for a 250ms animation. Read more

Python Programming

  • Reporting Exceptions in Python Scripts with Sentry

    Python scripts are the glue that keep many applications and their infrastructure running, but when one of your scripts throws an exception you may not know about it immediately unless you have a central place to aggregate the errors. That's where adding Sentry can solved this distributed error logging problem. In this tutorial, we'll see how to quickly add Sentry to a new or existing Python script to report errors into a centralized location for further debugging.

  • Luke Plant: Keyword-only arguments in Python

    Keyword-only arguments are a feature that has been around since Python 3.0. But I’ve seen and used them much less use that I could have. They are described in PEP 3102, which is pretty readable, but I think they could benefit from more exposure with examples and rationale.

  • Creating and Modifying PDF Files in Python

    The PDF, or Portable Document Format, is one of the most common formats for sharing documents over the Internet. PDFs can contain text, images, tables, forms, and rich media like videos and animations, all in a single file. This abundance of content types can make working with PDFs difficult. There are a lot of different kinds of data to decode when opening a PDF file! Fortunately, the Python ecosystem has some great packages for reading, manipulating, and creating PDF files.

  • Will McGugan: Rich gets Richer

    Since my last post on Rich there have been a number of improvements. [...] Coverage has reached 97% which is not bad at all. To be honest though it is the use of type annotations throughout which gives me the most confidence.

Linux 5.8 Kernel: Qualcomm Adreno, MacBooks and AMD

  • Qualcomm Adreno 650 + 640 GPUs To Be Supported By Mainline Linux 5.8 Kernel

    The crew working on the MSM DRM driver from Freedreno / Google / Code Aurora (Qualcomm) have an interesting batch of changes for this open-source GPU driver for Qualcomm Adreno hardware come Linux 5.8. New hardware to be supported by this open-source MSM driver in Linux 5.8 include Qualcomm's Adreno 405, 640, and 650 series. The Adreno 405 is an old, low-end part from the 400 series and used by the Snapdragon 415/615/616/617 SoCs. The Adreno 405 support isn't particularly exciting but it's there for those interested along with the relevant MSM8x36 changes to the MDP5 code.

  • Linux 5.8 Picking Up A Quirk For Being Able To Reboot The 2009 MacBook Without Hangs

    With the upcoming Linux 5.8 cycle a quirk is being added to be able to reboot the 2009 era Apple MacBook without needing to boot with any special flags. Up to now the 2009 Apple MacBook (Macbook6,1) required a reboot=pci boot parameter added to the kernel otherwise when rebooting the system there would be a hang. This late 2009 MacBook (MC207LL/A) with Core 2 Duo CPU is very slow by today's standards and hopefully many of you still aren't using it in production, but should you be doing so and running new kernel releases, with Linux 5.8 the kernel can reboot without hanging or needing to manually add the flag.

  • AMD Energy Driver Queued Ahead Of Linux 5.8 For Core/Package Power Sensors

    Landing this weekend in hwmon-next ahead of the upcoming Linux 5.8 kernel cycle is the recently reported on "amd_energy" driver for supporting AMD Zen/Zen2 core and package energy sensors. This is the recently reported on work of a Google engineer allowing AMD Zen CPUs to expose power usage on Linux via the Runtime Average Power Limiting (RAPL) framework. The amd_energy driver is making it to the Linux 5.8 kernel by way of the hardware monitoring "hwmon" subsystem thanks to this Google open-source contribution.

today's howtos