https://bugs.winehq.org/show_bug.cgi?id=37893
Bug ID: 37893 Summary: League of legends : can't connect if TCP timestamps aren't disabled Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: scrimekiler@yahoo.fr Distribution: ---
Hi, since a few days, a bit than a week, it seems all Wine users have this problem : they can't connect to the server if TCP timestamps aren't disabled :
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
I tried using wineinet override, (tried both native and builtin) which doesn't help.
Wine-staging is also affected.
I will post the logs soon with both timestamps enabled and disabled
https://bugs.winehq.org/show_bug.cgi?id=37893
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com Summary|League of legends : can't |League of legends : can't |connect if TCP timestamps |connect if TCP timestamps |aren't disabled |are enabled
https://bugs.winehq.org/show_bug.cgi?id=37893
fischer.j.42@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fischer.j.42@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=37893
fepf.tuc@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fepf.tuc@web.de
https://bugs.winehq.org/show_bug.cgi?id=37893
bsldur@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bsldur@gmx.de
--- Comment #1 from bsldur@gmx.de --- I can confirm this. But – at least for me – this seems to only be the case for the EUW region server. (Only other one I tested was NA, but that worked fine for me.) However, as all this coincides with general ping problems my provider seems to be having with connections to EUW right now, the root cause might not lie with WINE at all. What's certain is that disabling the TCP timestamps makes logging in work again.
https://bugs.winehq.org/show_bug.cgi?id=37893
--- Comment #2 from Someone scrimekiler@yahoo.fr --- The strange thing is the fact I have a ".update-timestamp" file in my wineprefix containing League of Legends...
It's true that should only be related to their server configuration and shouldn't have any relationship with wine, but what make me think it could have a link with wine is that timestamp file...
Also I don't know if some of the wine component have any notion of timestamp or not...
If someone know this and can't be 100% sure it can't come from wine, it should be marked as closed/invalid and I'm sorry for this report.
https://bugs.winehq.org/show_bug.cgi?id=37893
--- Comment #3 from User bsldur@gmx.de --- Sorry, I don't really know that much about the whole TCP/IP thing. It might very well be WINE. I was just guessing around.
For reference, here's my console output for failed login attempts:
(...) fixme:wininet:IsDomainLegalCookieDomainW (L"riotgames.com", L"lq.euw1.lol.riotgames.com") semi-stub fixme:imm:ImmReleaseContext (0x1006c, 0x6981868): stub fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 10000 fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 10000 fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 10000 fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 10000 err:wininet:open_http_connection create_netconn failed: 12029 err:wininet:open_http_connection create_netconn failed: 12029
The first two lines are normal, I just included them to give context. I'm running the "stefand" github-fork of WINE, with patched resource.c.
https://bugs.winehq.org/show_bug.cgi?id=37893
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=37893
Riccardo c10ud.dev@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |c10ud.dev@gmail.com
--- Comment #4 from Riccardo c10ud.dev@gmail.com --- This is not a wine bug, also it has been fixed upstream
https://bugs.winehq.org/show_bug.cgi?id=37893
--- Comment #5 from Austin English austinenglish@gmail.com --- (In reply to Riccardo from comment #4)
This is not a wine bug, also it has been fixed upstream
In the kernel or in the game?
https://bugs.winehq.org/show_bug.cgi?id=37893
--- Comment #6 from User bsldur@gmx.de --- I can confirm that Riot or some ISP seem to have fixed the issue on their end and disabling TCP timestamps is no longer required.
Still, thanks for posting the workaround here. Could not find anything useful anywhere else on the internet.
https://bugs.winehq.org/show_bug.cgi?id=37893
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM
--- Comment #7 from Austin English austinenglish@gmail.com --- (In reply to User from comment #6)
I can confirm that Riot or some ISP seem to have fixed the issue on their end and disabling TCP timestamps is no longer required.
Still, thanks for posting the workaround here. Could not find anything useful anywhere else on the internet.
Upstream then.
https://bugs.winehq.org/show_bug.cgi?id=37893
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=37893
--- Comment #9 from Bruno Jesus 00cpxxx@gmail.com --- Actually invalid because it was a problem in the game itself or its network infrastructure. Upstream would be the case if the problem was in the kernel, driver or some other library required by wine, right?
https://bugs.winehq.org/show_bug.cgi?id=37893
--- Comment #10 from Austin English austinenglish@gmail.com --- (In reply to Bruno Jesus from comment #9)
Actually invalid because it was a problem in the game itself or its network infrastructure. Upstream would be the case if the problem was in the kernel, driver or some other library required by wine, right?
I used upstream since a bug was verified and fixed. Granted, in proprietary code, but so are binary drivers.
-
wine-bugs＠winehq.org