https://bugs.winehq.org/show_bug.cgi?id=7106
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |bc68b30d208209d749522eaba79 | |b0e124956bdde Status|STAGED |RESOLVED Resolution|--- |FIXED Staged patchset|https://github.com/wine-sta | |ging/wine-staging/tree/mast | |er/patches/krnl386.exe16-In | |valid_Console_Handles |
--- Comment #39 from Zeb Figura z.figura12@gmail.com --- As far as I can tell, this was actually fixed by https://source.winehq.org/git/wine.git/commitdiff/bc68b30d208209d749522eaba79b0e124956bdde.
The wine-staging patch was written afterwards; as far as I can tell as a response to that commit, in an attempt to be more robust. But the component it's trying to be more robust against is the server, and that already catches invalid handles and returns zero for them.
I've removed the patch set from wine-staging in commit d216d5cdb2d12336327ff157683fbed86b9289cb; a more complete explanation is given there.
The application currently works with upstream Wine. Reverting bc68b30d2 breaks it again. I didn't test with bc68b30d2 proper or its parent, but I think it's safe to conclude that that commit really did fix the program.