Battle.net gets stuck on a spinning logo and shows repeated process crash windows with regular Wine, but runs with Wine Staging 11.9 and 11.10. Is there a known reason, and could the fix make it into Wine 12 stable?
Why does Battle.net work with Wine Staging but not regular Wine?
Answers
Staging includes experimental patches that aren't necessarily in Wine's development or stable releases. That makes a Staging-only fix plausible, but it doesn't identify which patch is responsible.
The crashes might involve cef.dll or hardware acceleration, but that connection is still a guess here. Pinning it down would take logs and a comparison between builds or patches.
Reply to this answer
Don't count on the fix landing in Wine 12 stable just because it works in Staging. Staging patches can change, be merged into Wine proper, or stay separate. Without knowing the responsible patch and its status, there's no way to say.
Reply to this answer
If the goal is simply to run the launcher, Staging is worth trying when regular Wine hits this crash. Proton and other launchers such as Lutris are alternatives too, though that doesn't explain what's different under the hood.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions