[Bug 54793] New: LeagueClient.exe get's stuck in the league of legends logo before crashing
https://bugs.winehq.org/show_bug.cgi?id=54793 Bug ID: 54793 Summary: LeagueClient.exe get's stuck in the league of legends logo before crashing Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kassin.dornelles(a)gmail.com Distribution: --- Created attachment 74287 --> https://bugs.winehq.org/attachment.cgi?id=74287 Logs from when the LoL logo starts and when it crashes. When launching the LeagueClient.exe launcher pressing "Play" in the RiotClientServices.exe window it will show up the league of legends logo but it will be stuck on it for 1 to 2 minutes before it stops trying to launch the game client, so the riotclientservices "Play" button will get re-enabled for the user to try again Steps to reproduce: - Install WINE 8.5 (upstream release) - Install corefonts (via Winetricks or System wide, i did install system wide) to get the riotclientservices.exe to actually work - Launch the game installer that you got from "https://signup.leagueoflegends.com/en-us/signup/redownload" - Press install and wait for it, when its over it will launch the riotclientservices.exe - Wait for the league client to be downloaded by the riot client, press play after it and that's it. Ive seen other issues but seems like most of them got abandoned by the author and were also using an older version of WINE (please move the issues to gitlab if possible) Some random info: I have all wine dependencies installed, i'm on arch linux, i have corefonts installed and the prefix is a new one, clear, not even dxvk or vkd3d-proton is installed, is as clear as it can be. GPU and CPU is not relevant because a bunch of people in different hardware get the same exact issue every time. i'm attaching logs -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 --- Comment #1 from Kassin Dornelles <kassin.dornelles(a)gmail.com> --- Created attachment 74288 --> https://bugs.winehq.org/attachment.cgi?id=74288 WINEDEBUG=+timestamp -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 Matías Zúñiga <matias.nicolas.zc(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matias.nicolas.zc(a)gmail.com --- Comment #2 from Matías Zúñiga <matias.nicolas.zc(a)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... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 neyl(a)tuta.io changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |neyl(a)tuta.io -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 Alexis Peypelut <iroalexis(a)outlook.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iroalexis(a)outlook.fr -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal CC| |o.dierick(a)piezo-forte.be -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #3 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I confirm the issue and that the linked patch works around it. Regards. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |winsock -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 Spyridon Passas <epicdudeness677(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |epicdudeness677(a)gmail.com --- Comment #4 from Spyridon Passas <epicdudeness677(a)gmail.com> --- Created attachment 74886 --> https://bugs.winehq.org/attachment.cgi?id=74886 Logs on the LeagueClient crashing -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 --- Comment #5 from Spyridon Passas <epicdudeness677(a)gmail.com> --- Created attachment 74887 --> https://bugs.winehq.org/attachment.cgi?id=74887 Logs on the RiotClientService crash -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 --- Comment #6 from Spyridon Passas <epicdudeness677(a)gmail.com> --- I am not sure if i would need to create a new post or not given the similarities to this post, so ill make a comment instead. I am new to linux overall and i am using Ubuntu 22.04.2 LTS. I have installed WINE (6.0.3) in preparation for the league install and i followed [0] on how to install league (it uses snap). The behaviour i am recieving is similar to OP's problem: The launcher for lol works as expected but the game crashes the second i press the Play button. I have uploaded the 2 logs that i recieve whenever i open the game (see [1]). [0]: Tutorial on installing League of Legends: https://www.youtube.com/watch?v=yh5G5QSMiMQ [1]: Uploaded Logs: "Logs on the LeagueClient crashing", "Logs on the RiotClientService crash". If any more information is required, do be kind and mention it. Ill try to provide with the given time that i have. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 --- Comment #7 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Spyridon Passas from comment #6)
If any more information is required, do be kind and mention it. Ill try to provide with the given time that i have.
Hello, You're using an unsupported wine fork & too old version (5.X - Tgk...) Please retest with recent (8.1x) plain wine or wine-staging. If you can't change wine version because it's bundled, report to the people who makes the bundle as we don't give support for bundled Wine here either. If you can change wine version, try the workarounds from comment 2. If the game starts with the workaround: It's the same issue and you can only wait for a developer to care for this bug. If not: It's a different issue and you should open a new bug with full terminal output, not just backtraces. https://wiki.winehq.org/FAQ#get_log Regards. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54793 --- Comment #8 from Spyridon Passas <epicdudeness677(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #7)
(In reply to Spyridon Passas from comment #6)
If any more information is required, do be kind and mention it. Ill try to provide with the given time that i have.
Hello,
You're using an unsupported wine fork & too old version (5.X - Tgk...)
Please retest with recent (8.1x) plain wine or wine-staging.
If you can't change wine version because it's bundled, report to the people who makes the bundle as we don't give support for bundled Wine here either.
If you can change wine version, try the workarounds from comment 2.
If the game starts with the workaround: It's the same issue and you can only wait for a developer to care for this bug.
If not: It's a different issue and you should open a new bug with full terminal output, not just backtraces. https://wiki.winehq.org/FAQ#get_log
Regards.
Greetings Oliver! I updated the wine version from 6.0.3 to 8.0.1 as instructed and the league client managed to actually open for me. At the moment, my internet connection is too slow do immediately see if the game itself is working, but given the fact that i managed to launch the league client without the workaround from the second comment [0], it seems like the latest wine version has fixed this web socket issue. Atleast for my machine. [0]: https://bugs.winehq.org/show_bug.cgi?id=54793#c2 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=54793 joaopa <jeremielapuree@yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr --- Comment #9 from joaopa <jeremielapuree@yahoo.fr> --- Does the bug still occur with wine-11.0-rc4? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=54793 Gijs Vermeulen <gijsvrm@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED --- Comment #10 from Gijs Vermeulen <gijsvrm@gmail.com> --- Reported fixed in Comment #8, but given that League of Legends has changed significantly since them, marking ABANDONED instead. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=54793 Gijs Vermeulen <gijsvrm@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Gijs Vermeulen <gijsvrm@gmail.com> --- Closing ABANDONED. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla