https://bugs.winehq.org/show_bug.cgi?id=52103
--- Comment #38 from Rémi Bernon rbernon@codeweavers.com --- (In reply to Gerry from comment #37)
(In reply to Rémi Bernon from comment #36)
I tried reverting that commit but it didn't help for me, I re-run the bisect and found that 7d2a7b94aad8a776a2ee3031a18bb3b53d5925cd is the actual culprit. Reverting this one fixes the game.
If I thought I'd understand the answer I'd ask for a bit of explanation why the bad bisect I found was the wrong one.
Well there's many reasons it can happen, especially if you're not used to doing it. Sometimes the crash is a little bit random and you one bisect step is wrong, some other time some modules aren't rebuilt correctly, and you run on an old version of wine, or the wine prefix was still running with an old version, etc...
It's not completely bulletproof, and the best way to do it is generally to wipe out everything in the build tree or the prefix on every step. It's more time consuming though.
Note that it then also already has been fixed with 220b0a7c060e71a7a414cd89542769451274e873.
Thank you. Do we have a clue when it might appear in e.g., Tumbleweed?
I don't know when the Linux distribution will decide to update their packages, but the fix should be available in tomorrow release (Wine 6.23).