[Bug 41225] New: League of Legends: Login Status randomly fails/succeeds
https://bugs.winehq.org/show_bug.cgi?id=41225 Bug ID: 41225 Summary: League of Legends: Login Status randomly fails/succeeds Product: Wine Version: 1.9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nmschulte(a)gmail.com Distribution: --- Created attachment 55493 --> https://bugs.winehq.org/attachment.cgi?id=55493 stderr + stdout amd64 Debian Sid, multi-arch (Intel Haswell) wine-development version wine-1.9.17 (Debian 1.9.17-1) wine-stable version wine-1.8.3 (Debian 1.8.3-3) When logging in to the game, sometimes the login works immediately (rare), sometimes the login seems to timeout multiple times in a row and fails after 3 re-attempts, and sometimes it succeeds after a few re-attempts. I have attached a log where my first "login" failed after three request attempts; I then pressed the button again (second "login"), which was re-attempted twice but succeeded after the second re-attempt. Please see the screenshots for reference. After having dealt with this issue for a while (since I've ever been playing League of Legends on Wine, which was v1.5 or v1.6; definitely same issue w/ v1.7), I've noticed a few quirks: I have a hunch this has to do w/ SSL/TLS (HTTPS) or part of the certificate chain. It seems that having iexplore.exe open in the background/prior makes the login more likely to succeed. Just a feeling, not 100% certain this helps. If I enter a bad password, the responses seem to _always_ come back right away (or very, very quickly). I have had decent success "working around" this issue by: 1) copying my correct password to the clipboard (usually by CTRL+X'ing it after typing it in the username field) 2) issuing a rapid succession of "logins" with incorrect passwords, until the (login failed) response comes back _very quickly_, usually after 3 or 4 "logins" 3) quickly pasting my correct password and logging in Usually, this signs me in on the very first "login" request/response (no "attempt #" re-attempts). -- 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=41225 --- Comment #1 from nmschulte(a)gmail.com --- Created attachment 55494 --> https://bugs.winehq.org/attachment.cgi?id=55494 Login Status after "login" -- 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=41225 --- Comment #2 from nmschulte(a)gmail.com --- Created attachment 55495 --> https://bugs.winehq.org/attachment.cgi?id=55495 Login Status after "login," first retry -- 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=41225 --- Comment #3 from nmschulte(a)gmail.com --- Created attachment 55496 --> https://bugs.winehq.org/attachment.cgi?id=55496 Login Status after "login," failed this is after three attempts to retry -- 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=41225 --- Comment #4 from nmschulte(a)gmail.com --- Created attachment 55497 --> https://bugs.winehq.org/attachment.cgi?id=55497 Login Status after "login," succeeded presented when a request succeeds -- 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=41225 --- Comment #5 from nmschulte(a)gmail.com --- I believe this bug is related: https://bugs.winehq.org/show_bug.cgi?id=39375 -- 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=41225 --- Comment #6 from nmschulte(a)gmail.com --- I started w/ a fresh Wine prefix and copying my (league of legends) installation from a Windows VM, the issues w/ login have gone away. $ rm -rf ~/.wine/ $ winetricks vcrun2005 ie8 d3dx9 corefonts adobeair $ winecfg # change Windows version to Vista $ virtualbox # copy C:\Riot Games\ to ./.wine/drive_c/ $ wine ./.wine/drive_c/Riot\ Games/League\ of\ Legends/lol.launcher.exe The pre-game store works now as well, though I am prompted a few times to accept invalid certificates, and at one time to enter my credentials. I'm not sure how to resolve this... the issue clearly existed w/ my old prefix, but is clearly gone w/ my new one. I cannot confirm or deny that wininet component was installed in my old prefix. -- 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=41225 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #7 from winetest(a)luukku.com --- It's just that wine cant support thatkind of method for fixing bugs in wine. Nothing is fixed in wine source code. -- 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=41225 --- Comment #8 from nmschulte(a)gmail.com --- I'm not sure I understand; what is "it?" Good or bad? Is there anything to be had from this bug report then? I wish I hadn't deleted my old prefix in anger... but I'm glad the new one works! If anything, I think this report could be closed as "resolved; fixed" or "resolved; unreproducible." If I could find a game setting that causes the issue, or a winetricks component that causes the issue, would that make this useful? I may have an old copy of the/a wineprefix that presents this issue. -- 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=41225 --- Comment #9 from winetest(a)luukku.com --- (In reply to nmschulte from comment #8)
I'm not sure I understand; what is "it?" Good or bad?
Is there anything to be had from this bug report then? I wish I hadn't deleted my old prefix in anger... but I'm glad the new one works!
If anything, I think this report could be closed as "resolved; fixed" or "resolved; unreproducible."
If I could find a game setting that causes the issue, or a winetricks component that causes the issue, would that make this useful? I may have an old copy of the/a wineprefix that presents this issue.
Solve invalid, or abandoned. Bugs need to be fixed in wine source code for the bugs to be marked fixed. Game updates fixing bugs stll don't count that wine got fixed. Also workarounds like winetricks recipes don't count as fixed. -- 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=41225 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED CC| |o.dierick(a)piezo-forte.be --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, I'll go ahead and mark this abandoned. The launcher has been replaced since anyway and the issue didn't arise again. 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=41225 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing. -- 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)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla