https://bugs.winehq.org/show_bug.cgi?id=40907
Bug ID: 40907 Summary: League of Legends alpha client does not create a window Product: Wine Version: 1.9.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: hevanen@googlemail.com Distribution: ---
Created attachment 55003 --> https://bugs.winehq.org/attachment.cgi?id=55003 Console output
The alpha client does not create a window. When running it for the first time, the client needs to patch itself - the patching process actually seems to complete in the background, but no progress window is shown. The console output for subsequent runs is attached. Like before, no window is created.
https://bugs.winehq.org/show_bug.cgi?id=40907
David K. hevanen@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://euw.leagueoflegends. | |com/en/client-update/downlo | |ad
https://bugs.winehq.org/show_bug.cgi?id=40907
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #1 from winetest@luukku.com --- Well I was about to test this bug but it needs the game already installed. It's too big download so I lost interestest.
You should test meanwhile if newer wine fixes the issue.
https://bugs.winehq.org/show_bug.cgi?id=40907
Roberto Sten_Gun benfi@hotmail.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |benfi@hotmail.it
--- Comment #2 from Roberto Sten_Gun benfi@hotmail.it --- you should install vcrun2013 with winetricks, because doing that made the launcher window appear.
https://bugs.winehq.org/show_bug.cgi?id=40907
David K. hevanen@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.9.13 |1.9.22
--- Comment #3 from David K. hevanen@googlemail.com --- Still does not work with 1.9.22-staging. Having vcrun2013 installed seems to make no difference. Keep in mind this is about the new client that is currently under development - the old one works fine.
This new client is based on Chromium (CEF), which is known to make problems with Steam due to its sandboxing. So it seems quite possible that this is the problem here.
However, since the new client will soon be the only way to play the game, it might be good to find a fix or at least a workaround.
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #4 from Sten_Gun robenfi@gmail.com --- (In reply to David K. from comment #3)
Still does not work with 1.9.22-staging. Having vcrun2013 installed seems to make no difference. Keep in mind this is about the new client that is currently under development - the old one works fine.
I know is the alpha client, but I use it and I start it with success under wine.
This new client is based on Chromium (CEF), which is known to make problems with Steam due to its sandboxing. So it seems quite possible that this is the problem here.
However, since the new client will soon be the only way to play the game, it might be good to find a fix or at least a workaround.
I forgot to mention that you have to disable cef sandbox, otherwise the client will not start. This is how I start the alpha client
WINEPREFIX=~/.wineLOL wine LeagueClient.exe --no-sandbox
vcrun2013, dotnet2 and dotnet4 installed on this prefix, plus the required stuff to run the main game.
https://bugs.winehq.org/show_bug.cgi?id=40907
David K. hevanen@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #55003|0 |1 is obsolete| |
--- Comment #5 from David K. hevanen@googlemail.com --- Created attachment 56135 --> https://bugs.winehq.org/attachment.cgi?id=56135 Console output with 1.9.22-staging
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #6 from Sten_Gun robenfi@gmail.com --- (In reply to David K. from comment #5)
Created attachment 56135 [details] Console output with 1.9.22-staging
you have to start it with wine LeagueClient.exe --no-sandbox, otherwise it won't start
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #7 from David K. hevanen@googlemail.com --- Created attachment 56136 --> https://bugs.winehq.org/attachment.cgi?id=56136 Console output with 1.9.22-staging and --no-sandbox
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #8 from David K. hevanen@googlemail.com --- Ah, thanks. I didn't know the --no-sandbox parameter existed.
With the parameter, the client immediately crashes in Windows XP mode, in Windows 7 mode it sometimes shows the "Updating..." window, however it stays at 0/0 MB downloaded and nothing else happens (the client should already be up-to-date, so technically this isn't supposed to appear anyway).
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #9 from Sten_Gun robenfi@gmail.com --- (In reply to David K. from comment #8)
Ah, thanks. I didn't know the --no-sandbox parameter existed.
With the parameter, the client immediately crashes in Windows XP mode, in Windows 7 mode it sometimes shows the "Updating..." window, however it stays at 0/0 MB downloaded and nothing else happens (the client should already be up-to-date, so technically this isn't supposed to appear anyway).
with the latest update the main window will cause a bugsplat, but I can update easily the alphaclient and the game from there. I used to play with this client, but as long as it is in alpha, we are subject to schizophrenic behaviors from the program itself. I use a wine profile in 32bit mode, and is the same profile I use to play the game with the old client, if this helps for you.
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #10 from Sten_Gun robenfi@gmail.com --- (In reply to David K. from comment #7)
Created attachment 56136 [details] Console output with 1.9.22-staging and --no-sandbox
Regarding this, you need this library
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #11 from winetest@luukku.com --- (In reply to Sten_Gun from comment #10)
(In reply to David K. from comment #7)
Created attachment 56136 [details] Console output with 1.9.22-staging and --no-sandbox
Regarding this, you need this library
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
I haven't personally seen any bugs getting fixed installing winbind. Ubuntu based distros its sudo apt-get install winbind.
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #12 from Sten_Gun robenfi@gmail.com --- (In reply to winetest from comment #11)
(In reply to Sten_Gun from comment #10)
(In reply to David K. from comment #7)
Created attachment 56136 [details] Console output with 1.9.22-staging and --no-sandbox
Regarding this, you need this library
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
I haven't personally seen any bugs getting fixed installing winbind. Ubuntu based distros its sudo apt-get install winbind.
Indeed, but the main difference is that I don't have that error, and downloading (the step where David is now) works for me, so I think is worth investigating. I'm on arch linux.
https://bugs.winehq.org/show_bug.cgi?id=40907
--- Comment #13 from David K. hevanen@googlemail.com --- Ah, perhaps my install broke during my experiments, because it launches when I use the LoL install I have on my Windows partition.
Now I'm at the bugsplat you mentioned, which is also already detailed in bug 41695: wine: Call from 0x7b43cd7c to unimplemented function api-ms-win-crt-math-l1-1-0.dll.nearbyint
https://bugs.winehq.org/show_bug.cgi?id=40907
David K. hevanen@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #14 from David K. hevanen@googlemail.com --- The fact that the Chromium sandbox doesn't work is likely already tracked in a separate Steam bug, so this can be considered a duplicate with or without --no-sandbox.
*** This bug has been marked as a duplicate of bug 41695 ***
https://bugs.winehq.org/show_bug.cgi?id=40907
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Bruno Jesus 00cpxxx@gmail.com --- Closing duplicate bugs.
-
wine-bugs＠winehq.org