https://bugs.winehq.org/show_bug.cgi?id=54800
Matías Zúñiga matias.nicolas.zc@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matias.nicolas.zc@gmail.com
--- Comment #8 from Matías Zúñiga matias.nicolas.zc@gmail.com --- Hi!
Contrary to what some indicate, these is no need to "use various patches on top of wine" to replicate this.
Previously, patches for just 2 bugs were needed to get the game working: Bug 47198 and Bug 49412. Since the latest version switched from a 32bit to a 64bit client, and those bug were 32bit-specific, there is no need for these patches now.
This bug can be replicated using the wine-staging 8.6 (with the winegstreamer patches disabled, since the latest commit doesn't compile c:), and running "League of Legends.exe" directly. There is no need to have an account, just the game installed. Because of this bug, it will open a window saying that a critical error had happened.
The command line show no errors, and when running with WINEDEBUG=trace+all the bug fixes itself (when it works, the game just complains that you are launching it incorrectly, and opens a window saying that it should be started from the LeagueClient)
The fix:
There is a patch from @moonshadow565 that fixes this bug on the AUR wine-lol package [0], and I can confirm that applying it over wine-staging is enough to make the game run. (there is another bug when launching the LeagueClient (Bug 54793), but that one has been known for some time and has a working workaround).
Here [1] is his explanation for this bug, and why he thing it fixes itself when using WINEDEBUG=trace+all.
[0]: https://aur.archlinux.org/cgit/aur.git/tree/0008-ntdll-nopguard-call_vectore... [1]: https://github.com/kyechou/leagueoflegends/issues/83#issuecomment-1502431738