[Bug 47342] New: FFXIV launcher fails to connect with HTTPS error -2146697208
https://bugs.winehq.org/show_bug.cgi?id=47342 Bug ID: 47342 Summary: FFXIV launcher fails to connect with HTTPS error -2146697208 Product: Wine Version: 4.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: amathor929(a)gmail.com Distribution: --- Created attachment 64670 --> https://bugs.winehq.org/attachment.cgi?id=64670 Terminal output from when the error occurs Have tried both the 32bit and 64bit ffxivboot.exe, using Wine-staging 4.9 from the winehq repo results in the 32bit launcher giving this error and the 64bit giving a 404 error. The 404 error can be resolved by using the current wine-staging patches from git, but then it suffers the same -2146697208 error as the 32bit launcher. Have tried both 32 and 64bit prefixes, same result. I remember this being an issue for awhile, and deleting the My Games/FINAL FANTASY XIV - A Realm Reborn/Web folder would resolve it, however, I don't actually *have* that folder present as this is a fresh install of the game. The installer launches and completes fine, but the launcher dies. )have also tried setting FFXIV_BOOT.cfg: BrowserType 2 but doesn't help any. -- 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=47342 amathor929(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Fedora -- 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=47342 Sophira <wine-bugs(a)theblob.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wine-bugs(a)theblob.org --- Comment #1 from Sophira <wine-bugs(a)theblob.org> --- I'm not a WINE dev, and I hope it's okay for me to reply here, but I did want to let you know that the FFXIV community have workarounds for the game not working by default in WINE, which you can find at https://www.reddit.com/r/ffxiv/comments/bgeluh/any_other_linux_users_getting... . -- 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=47342 --- Comment #2 from amathor929(a)gmail.com --- Please actually read the entire post before replying. The thread you linked does nothing other than point me to information I already knew about solving the 404 error. The -2146697208 error isn't even mentioned in that reddit thread.. -- 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=47342 --- Comment #3 from Sophira <wine-bugs(a)theblob.org> --- It isn't mentioned in that thread because the current recommended method of playing the game involves using the IsTransgaming patch mentioned in the thread in order to force the launcher to use its built-in Chromium implementation instead of WINE's MSHTML implementation, which doesn't work currently. I didn't intend it to mean that this bug isn't worth leaving open (because it's clearly a problem with MSHTML) but rather to point you in a direction where the game is playable. I posted that thread. I didn't encounter the -2146697208 error as I'm not using an unpatched Wine (and at the time of the thread being posted, the 404 error wasn't fixed in Wine). Obviously, it's a bug and this should remain open; I just wanted to help you on your way to being able to play the game. -- 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=47342 --- Comment #4 from Sophira <wine-bugs(a)theblob.org> --- (I should mention, btw, that when I say "current recommended method", I'm referring to the method recommended by the FFXIV community; it's not intended in any way to mean that the WINE devs recommend this.) -- 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=47342 Chiitoo <escomk3(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |escomk3(a)hotmail.com --- Comment #5 from Chiitoo <escomk3(a)hotmail.com> --- Was the Wine used here built with GCC 9? I'll need to run a few more tests, but it seems I'm hitting the same issues when I build Wine using GCC 9.1.0, but not if I do it with 8.3.0 (Wine Staging 4.10). -- 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=47342 --- Comment #6 from amathor929(a)gmail.com --- gcc 9.1.1, yes -- 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=47342 --- Comment #7 from amathor929(a)gmail.com --- It should be noted, using the winehq-staging 4.10 package does work for the 64bit launcher, no 404 or -214 errors, but the 32 bit launcher still encounters the -214 error, and if I build the 4.10 staging myself, I run into the issue with both launchers -- 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=47342 --- Comment #8 from Chiitoo <escomk3(a)hotmail.com> --- You might like to try building either at git master, or apply this commit as a patch (it seems to apply cleanly on 4.10 at least): https://source.winehq.org/git/wine.git/commitdiff/9afc341c In other words, it looks like this will be fixed in 4.11. :] -- 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)
-
wine-bugs＠winehq.org