https://bugs.winehq.org/show_bug.cgi?id=50169
--- Comment #5 from Czcibor Bohusz-Dobosz czbd@o2.pl --- (In reply to Alistair Leslie-Hughes from comment #4)
(In reply to Czcibor Bohusz-Dobosz from comment #3)
Weird - I have just now built the preceding commit, just to make sure, and it also suffers from the same issue. I've also noticed that, for some reason, several sources in the wine directory have been untracked (they definitely weren't this way before the bisecting)...
So, apologies - looks like my git somehow got borked? Gotta bisect this one again...
The regression is caused by the disabled patchsets in staging, namely widl-winrt-support windows.gaming.input-dll windows.globalization-dll windows.media.speech.dll windows.networking.connectivity.dll
Some of the patchset in widl-winrt-support, are currently being upstream.
That would be even weirder, if I'm understanding right, because sure enough, after a second failed bisect (and a suspicion that it's actually caused by `CFLAGS="-g -O0"`; now running a third, it'll take a while), I have also checked regular, non-staging Wine 5.21 and 5.22 as packaged by Arch Linux - Wine 5.21 starts FSX just fine, 5.22 hangs.
Guess that my next step is obtaining less contaminated logs and sending 'em here ASAP. :)
Thank You!