https://bugs.winehq.org/show_bug.cgi?id=54793
Matías Zúñiga matias.nicolas.zc@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matias.nicolas.zc@gmail.com
--- Comment #2 from Matías Zúñiga matias.nicolas.zc@gmail.com --- Hi! This has been a known bug for the league community for some time, so I'll add some extra information in case it helps someone debug it to properly fix it:
- The RiotClientServices.exe process should start-up and expose a TLS socket so the LeagueClientUx.exe process can connect to it and show the interface. - Because of some bug on the socket code of wine, RiotClientServices.exe takes too long to expose the socket. LeagueClientUx.exe gives up trying to connect to the port, and kills itself.
There has been some known workarounds for this: the simplest one is to just SIGSTOP the LeagueClientUx.exe process, wait for the port to be available, and then SIGCONT. This makes it take some minutes to launch (5~10?).
There is also a hacky workaround [0] that involves playing with some timeout on the socket code from ws2_32.dll, obviously not a good solution.
[0]: https://aur.archlinux.org/cgit/aur.git/tree/0005-LoL-client-slow-start-fix.p...