https://bugs.winehq.org/show_bug.cgi?id=42741
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|STAGED |NEW CC| |z.figura12@gmail.com
--- Comment #74 from Zebediah Figura z.figura12@gmail.com --- This bug is not the regression you think it is. The relevant games never worked in upstream wine, only in wine-staging. Recently many fixes were made upstream which were intended to address exactly this bug (and other similar ones). As a result the wine-staging patch was removed, because it had either been obviated or could not be easily fixed. In fact it had not entirely been obviated, at least for Blizzard games, so we debugged and fixed it anyway, resulting in the "winebuild-pe_syscall_thunks" patch set.
In short, this bug was never fixed upstream. It was fixed in wine-staging, then broken, and then fixed again, and as far as I'm aware it should still work.
I anticipate a demand that applications such as this be tested when removing the patch sets that are supposed to fix them. Of course it would be nice, but the fact is that we wine-staging maintainers simply do not have the time (or, in many cases, money, or hardware).
Separately, this bug should hopefully be *entirely* fixed *upstream* after https://source.winehq.org/git/wine.git/commitdiff/043489456c1f633f86f8dd1fde6b32c48c90c6f4. It would be nice for someone to test with upstream wine and confirm this.