Differential D3352

Update wine to 3.13
ClosedPublic
Actions

Authored by debug on Jul 20 2018, 7:04 PM.

Details

Reviewers

JoshStrobl

Group Reviewers

Triage Team

Commits

R3169:bad9322a5829: Update wine to 3.13

Summary

Updated wine to the latest version 3.13.

Initial support for performance data in the registry.
Mono engine updated with some bug fixes.
Support for fetching BIOS information on Linux.
Improvements in the standard Task Dialog.
Various bug fixes.

Full changelog available here.

Test Plan

Installed wine.
Ran 'wine64 --version' which reports the correct version.
Ran 'wine64 notepad' which correctly setup and ran notepad.
Ran 'winecfg' which opened the wine config editor correctly.
Installed and ran Battle.Net and successfully logged into my account.

Diff Detail

Repository

R3169 wine

Branch

master

Lint

No Lint Coverage

Unit

No Test Coverage

Event Timeline

debug created this revision.Jul 20 2018, 7:04 PM

Herald added a reviewer: Triage Team. · View Herald TranscriptJul 20 2018, 7:04 PM

debug requested review of this revision.Jul 20 2018, 7:04 PM

Please also validate using something more advanced than notepad. A good candidate is Blizzard Battle.net. If you do so, you'll have to install the corefonts (I usually do this with winetricks). Just install it, run it, create a dummy account (unless you have one) and try to connect.

debug edited the test plan for this revision. (Show Details)Jul 20 2018, 9:11 PM

I will point out that although I am able to login to Battle.Net using this wine version I do get a 'program error' popup. Battle.Net seems to run perfectly fine anyway though. I have tried it with Wine 3.12 and 3.13 and I get the same error.

In D3352#53524, @debug wrote:

I will point out that although I am able to login to Battle.Net using this wine version I do get a 'program error' popup. Battle.Net seems to run perfectly fine anyway though. I have tried it with Wine 3.12 and 3.13 and I get the same error.

If you can login, that's fine. If you get error with SystemSurvey.exe or Battle.net Helper.exe, you can ignore them, these are known issues that requires some workarounds that are not relevant for this check.

Ah okay that's good to hear. In that case the testing was successful. I was able to login to Battle.Net.