You can sign up to get a daily email of our articles, see the Mailing List page.
We do often include affiliate links to earn us some pennies. See more here.

Windows compatibility layer Wine 5.20 development release is out now

By - | Views: 19,800

Breaking down barriers towards closer Windows compatibility, the Wine compatibility layer team have released the Wine 5.20 development release along with new features and fixes.

Need to know what Wine is? Here's our quick primer: it's a constantly improving compatibility layer that allows the running of Windows-only applications and games on Linux and other operating systems. It's one of the driving forces behind Steam Play Proton. Helping you to get whatever you need done on Linux, or perhaps so you don't have to give up that favourite game.

Here's the highlights:

  • More work on the DSS cryptographic provider.
  • A number of fixes for windowless RichEdit.
  • Support for FLS callbacks.
  • Window resizing in the new console host.

On top of that the usual assortment of bug fixes are here, with 36 getting the tick this time around. Some old solved in previous releases, some newer. These include: Metro Exodus, PS Remote Play, The Sims Complete Collection, Dungeons & Dragons Online, Saints Row 2 and lots more games seeing fixes across a few releases now being found to work better.

See the full release notes for Wine 5.20 here.

If you need help running multiple Wine versions, Lutris is good for that. You can also get help in our Forum any time.

Article taken from GamingOnLinux.com.
Tags: Open Source, Update, Wine | Apps: Wine
17 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly came back to check on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly. Find me on Mastodon.
See more from me
The comments on this article are closed.
10 comments

BielFPs Oct 24, 2020
Does this also help Fsync? or not yet?
Avehicle7887 Oct 24, 2020
It's also worth pointing out that the Staging patchset has also been released and esync has now also been re-enabled.

I've compiled 5.20 Staging this morning, esync is definitely back to working. I tried to apply Fsync from Tk-Glitch's github but it wouldn't compile. For now, I'm happy to have esync + mfplat support on without needing too much work, I'll work on the Fsync issue.

As per my usual biweekly mfplat tests, I've yet to run those but I won't leave this post empty handed:

Aquanox: Deep Descent - FMV's are working out of the box, no workarounds required. I ran into a weird memory leak with 5.19 but 5.20 is smooth sailing and dxvk is also working fine.

Shadows: Awakening - I've previously reported FMV's working out of the box already with previous Wine releases, adding Esync provided me a solid 25+ fps increase in some areas. Have yet to test it for any instabilities.

Darksiders 1: Warmastered Edition - Crashes on startup. Works fine with Wine 5.8 + Microsoft mfplat dll's.


More to come....


Last edited by Avehicle7887 on 24 October 2020 at 2:39 pm UTC
PublicNuisance Oct 24, 2020
Quoting: BielFPsDoes this also help Fsync? or not yet?

I just tried to enable Fsync and Esync through Lutris on prey with Wine 5.20 and both still gave me the error about uncompatible Wine version so I don't think that is fixed yet.


Last edited by PublicNuisance on 25 October 2020 at 4:50 am UTC
Xpander Oct 25, 2020
Quoting: BielFPsDoes this also help Fsync? or not yet?
no idea if that helps, but fsync has always worked for me with the tkg builds. he probably backported though?
i have been using fsync with all the versions since 5.9 till now with no problems.
andy155 Oct 25, 2020
Wow Classic is still broken


Last edited by andy155 on 25 October 2020 at 9:03 am UTC
mickski56 Oct 25, 2020
@Avehicle7887

Both of
autoreconf -f
tools/make_requests

are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.

HTH
Avehicle7887 Oct 25, 2020
Quoting: mickski56@Avehicle7887

Both of
autoreconf -f
tools/make_requests

are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.

HTH

Not sure I understood that correctly. Do I have to run "autoreconf -f" and "tools/make_requests" after I apply the fsync patch?

Another thing I'm confused about, with 5.20 do I just have to apply the "fsync-unix-staging.patch" file only now?

I'm using this repo: https://github.com/Frogging-Family/wine-tkg-git/tree/54d209fc9370492c3daf754e7a7c27ff3edccece/wine-tkg-git/wine-tkg-patches/proton

Correct me if I'm wrong, but the other fsync patches are for older Wine versions right?


Last edited by Avehicle7887 on 25 October 2020 at 9:58 am UTC
mickski56 Oct 25, 2020
Quoting: Avehicle7887
Quoting: mickski56@Avehicle7887

Both of
autoreconf -f
tools/make_requests

are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.

HTH

Not sure I understood that correctly. Do I have to run "autoreconf -f" and "tools/make_requests" after I apply the fsync patch?

Yes that is correct apply all patches you require i.e staging + fsync then run

autoreconf -f
tools/make_requests

in your build dir then continue to build as you normally do.

Another thing I'm confused about, with 5.20 do I just have to apply the "fsync-unix-staging.patch" file only now?

I'm using this repo: https://github.com/Frogging-Family/wine-tkg-git/tree/54d209fc9370492c3daf754e7a7c27ff3edccece/wine-tkg-git/wine-tkg-patches/proton

Correct me if I'm wrong, but the other fsync patches are for older Wine versions right?

Yes all other fsync patches are for older versions and will not apply to 5.20
I'm hoping some of the other patches will be updated as upstream wine settles down, but it hasn't happened yet.
Avehicle7887 Oct 25, 2020
Quoting: mickski56
Quoting: Avehicle7887
Quoting: mickski56@Avehicle7887

Both of
autoreconf -f
tools/make_requests

are required before configure and make.
autoreconf because staging patches touch configure.ac
and make_requests because fsync-unix-staging.patch touches server/protocol.def so server/protocol.h needs to be regenerated.

HTH

Not sure I understood that correctly. Do I have to run "autoreconf -f" and "tools/make_requests" after I apply the fsync patch?

Yes that is correct apply all patches you require i.e staging + fsync then run

autoreconf -f
tools/make_requests

in your build dir then continue to build as you normally do.

Another thing I'm confused about, with 5.20 do I just have to apply the "fsync-unix-staging.patch" file only now?

I'm using this repo: https://github.com/Frogging-Family/wine-tkg-git/tree/54d209fc9370492c3daf754e7a7c27ff3edccece/wine-tkg-git/wine-tkg-patches/proton

Correct me if I'm wrong, but the other fsync patches are for older Wine versions right?

Yes all other fsync patches are for older versions and will not apply to 5.20
I'm hoping some of the other patches will be updated as upstream wine settles down, but it hasn't happened yet.

It worked, thanks :)

In case anyone is also self compiling, steps I took:

Unpacked Wine source
Applied Staging patches
Applied 'fsync-unix-staging.patch'
Ran 'autoreconf -f'
Ran './tools/make_requests'

And the usual './configure' and 'make' commands. Can confirm FSync is working (Outward benefits a lot from this).

Happy Sunday everyone :)
TheRiddick Oct 25, 2020
This release should fix Fallout76 launch crash also.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon. Plain Donations: PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
The comments on this article are closed.