[Bug 41225] New: League of Legends: Login Status randomly fails/succeeds

[wine-bugs at winehq.org]

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 at winehq.org
          Reporter: nmschulte at 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.