[Bug 50738] New: Guild Wars 2 launcher can't login
https://bugs.winehq.org/show_bug.cgi?id=50738 Bug ID: 50738 Summary: Guild Wars 2 launcher can't login Product: Wine Version: 6.3 Hardware: x86-64 URL: https://account.arena.net/content/download/gw2/win/64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: sven.wine(a)gmail.com Regression SHA1: 8f50dde9cd3f4ea7856106f5b1691827d4cf8713 Distribution: Ubuntu Created attachment 69508 --> https://bugs.winehq.org/attachment.cgi?id=69508 Log from 8f50dde9cd3f4ea7856106f5b1691827d4cf8713 with +timestamp,+pid,+tid,+seh Since commit 8f50dde9cd3f4ea7856106f5b1691827d4cf8713 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Mon Feb 15 21:57:42 2021 +0100 ntdll: Store entire XMM context in x86_64 syscall frame. the Guild Wars 2 launcher can't reach login the server anymore. Attached is the log at 8f50dde9cd3f4ea7856106f5b1691827d4cf8713. I confirmed that with 8f50dde9cd3f4ea7856106f5b1691827d4cf8713^ everything was working as expected. -- 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=50738 Sven Baars <sven.wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, regression -- 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=50738 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com -- 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=50738 Mel <pmargeti34(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmargeti34(a)gmail.com --- Comment #1 from Mel <pmargeti34(a)gmail.com> --- Confirming this, with wine 6.3-1 guild wars 2 launcher is unable to log in (claims no network access). Downgrading the package to 6.2-1 allows it to log in normally. -- 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=50738 Stefan <linsilstef(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linsilstef(a)gmail.com --- Comment #2 from Stefan <linsilstef(a)gmail.com> --- here the same in Fedora 33 and Wine version 6.3-1 comes the message Actually starting the game. You can't log in with error 42:0:9001:4457 "can't connect to login server". -- 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=50738 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |proteve(a)mail.com --- Comment #3 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- *** Bug 50808 has been marked as a duplicate of this bug. *** -- 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=50738 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Multiple users reporting the issue, marking confirmed. 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=50738 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lambda.xy.x(a)gmail.com --- Comment #5 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 50825 has been marked as a duplicate of this bug. *** -- 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=50738 ct.gwq(a)peuc.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ct.gwq(a)peuc.net -- 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=50738 Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lvb.crd(a)protonmail.com -- 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=50738 Paul Gofman <pgofman(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgofman(a)codeweavers.com --- Comment #6 from Paul Gofman <pgofman(a)codeweavers.com> --- I've tested the issue. The effect of the patch is just tweaking the stack layout. I could reproduce the issue on top of the last good commit by just allocating a bit more data on stack in wine_syscall_dispatcher() without any other changes from the blamed commit. However, there is no stack overflow, and allocating even more memory on stack in wine_syscall_dispatcher() fixes the issue again. It appears to be the use of the memory on stack below the stack pointer which goes fine when the memory there hasn't been overwritten and break things when it had. I could also reproduce the issue by clearing some amount of stack below the stack pointer at syscall dispatcher exit and ended up finding the exact offset below the stack writing to which breaks things. I discovered that problematic memory address is passed to ws2_32.ConnectEx() as the initial data send buffer. Looks like on Windows it supposed to copy the data before returning from the function which is not necessarily the case in Wine currently. So when the game passes the on stack buffer to ConnectEx and then leaves, the consistency of data being sent are at the mercy of that stack part to be untouched (which by chance happened to be the case before the blamed commit). This patch on top of current master is fixing the issue for me: https://source.winehq.org/patches/data/202349 -- 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=50738 --- Comment #7 from Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> --- (In reply to Paul Gofman from comment #6)
This patch on top of current master is fixing the issue for me: https://source.winehq.org/patches/data/202349
This patch helps me too. I have made several tries and they have always been successful. Thanks You, Paul Gofman. -- 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=50738 --- Comment #8 from Paul Gofman <pgofman(a)codeweavers.com> --- Should be fixed by 904f7cfbae6542e9d0b3e00cc65427f8979b1770 -- 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=50738 Sven Baars <sven.wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |904f7cfbae6542e9d0b3e00cc65 | |427f8979b1770 Status|NEW |RESOLVED --- Comment #9 from Sven Baars <sven.wine(a)gmail.com> --- It is. Thanks Paul! -- 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=50738 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.5. -- 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 (1)
-
WineHQ Bugzilla