[Bug 46704] League Of Legends 9.4, Connection issue - We' re unable to log you in because you may be offline.

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Feb 28 04:56:39 CST 2019


https://bugs.winehq.org/show_bug.cgi?id=46704

--- Comment #35 from Farcrada <farcrada at yandex.com> ---
Created attachment 63740
  --> https://bugs.winehq.org/attachment.cgi?id=63740
League hangs before Splashscreen is even loaded

(In reply to Jonathan Preston from comment #27)
> I made some progress, I think. I am now able to successfully log in in all
> cases, assuming the game launches to the login screen (which it doesn't
> about 50% of the time, but I think that's an unrelated issue).
> 
> Essentially, what I did is bypass systemd-resolved.
> 
> <SNIP>
> 
> Hopefully this is helpful information.

I didn't feel like using Google's DNS nor changing loads of network stuff so I
figured: If changing systemd-resolved is the issue, does using WireGuard
(wg-quick up <insertVPN>) fix it? Apparently it does. It seems to resolve this
issue consistently. I can even log in normally without issue. The only issue I
run into now is that after it installs the first time and you close it after it
won't boot at all (splash screen's just stuck).

000001.327|   WARN|           rcp-be-lol-lobby| Can't check registration
status, not connected
000006.612| ALWAYS|             Plugin Manager| Initializing plugin
rcp-be-lol-account-verification: 1.0.8
000011.413|   OKAY|           rcp-be-lol-lobby| Set ready retry backoff time:
10.000000

This last line just repeats every 10 seconds until you kill LeagueClient.exe
via system monitor. Even closing from Lutris doesn't always work. I will attach
the log to the attachments. I wonder if it's stuck on account-verification or
something else.

Maybe it isn't as sure fire as I thought. Though instead of just getting an
empty launcher screen that's supposed to download the client, I could
consistently download the 1.5GB each time, log in (and probably play) and
message friends. So the connection is solid, given that I don't exit.

In other words this means that whatever WireGuard does to systemd-resolved (and
it's config) fixes what WINE either can't or doesn't for League, but for me
another issue arises, anyone else care to try?

-- 
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.



More information about the wine-bugs mailing list