FS#66521 - [wine-staging] Freeze/crash - apply unreleased upstream patch?
Attached to Project:
Community Packages
Opened by Storm Engineer (Stormheart) - Sunday, 03 May 2020, 12:29 GMT
Last edited by freswa (frederik) - Monday, 22 June 2020, 21:21 GMT
Opened by Storm Engineer (Stormheart) - Sunday, 03 May 2020, 12:29 GMT
Last edited by freswa (frederik) - Monday, 22 June 2020, 21:21 GMT
|
Details
Description: wine-staging has a regression that causes lots
of games to crash upon start. A patch has already been
prepared but not released yet, so perhaps we should apply
the patch to Arch's package for the time being? (And if I
understand correctly it affects regular wine too?)
Additional info: * package version: 5.7 * upstream bug: https://bugs.winehq.org/show_bug.cgi?id=49011 Steps to reproduce: Try to run an affected game. In my case it's Overwatch. Clicking the Play button in the Battle.net app causes both Battle.net to freeze and Overwatch crash/freeze before it even starts. |
This task depends upon
Closed by freswa (frederik)
Monday, 22 June 2020, 21:21 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed by upstream: https://bugs.winehq.org/show_bug.cgi?id= 49011#c25
Monday, 22 June 2020, 21:21 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed by upstream: https://bugs.winehq.org/show_bug.cgi?id= 49011#c25
Divinity Original Sin 2 used to run without issues until I updated my system, including from wine-staging 5.6 to wine-staging 5.7.
The game didn't launch properly any more, instead it shows a black screen, then the desktop. The game process still remains and needs to be terminated, but the game doesn't do anything (no sound, no video, nothing).
Just updated to wine-staging 5.8 and the bug still remains.
Note that I also use dxvk to run the game, a different game (Guild Wars 2) runs properly as usual, and the update after which Divinity stopped working included a lot more than just wine-staging 5.7.
So again, I'm not certain if this is the same issue or if I should file a different bug somewhere (wine, dxvk). Feel free to ask if there is anything (logs etc.) that could help track this down.
EDIT:
I looked at the official wine bug tracker and it seems others are also still experiencing the bug.
See for example: https://bugs.winehq.org/show_bug.cgi?id=49123 or https://bugs.winehq.org/show_bug.cgi?id=49007#c11
From what I'm seeing the patch that several people mention simply reverts a specific commit in wine, but I'm not sure if that patch is actually included in 5.8 or if they are looking to create a proper fix.
Others have reported that several other games appear to be fixed now, so this might be a different issue introduced in wine-staging 5.7.
I'll report my issue upstream and see what they think about it. Meanwhile if all the other games affected are running fine again this can probably be closed, or it's at least not as critical anymore.