[Bug 47069] New: Final Fantasy XIV Launcher renders black
https://bugs.winehq.org/show_bug.cgi?id=47069 Bug ID: 47069 Summary: Final Fantasy XIV Launcher renders black Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: winehq.eloelo(a)spamgourmet.com Distribution: --- Hi! I saw that no issue had been created here, so I figured it was the right place. The final fantasy XIV launcher no longer renders correctly through wine, and it might seem to be caused by multiple bugs. https://github.com/ValveSoftware/Proton/issues/580 There is a lot of information to dig through, so I'll make a summary here. Since last game-patch the launcher stopped working. The launcher is somehow trying to access https://frontier.ffxiv.com/version_4_0_win/version_4_0_win/ instead of just https://frontier.ffxiv.com/version_4_0_win/. This is a potential wine parsing bug? You can however bypass this issue and make it load the correct url. At which point the launcher renders nothing. It is theorized that this might be due to mshtml issues, but nothing is confirmed. This would be the main issue here, in my eyes. -- 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=47069 Ole Erik Brennhagen <winehq.eloelo(a)spamgourmet.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://github.com/ValveSof | |tware/Proton/issues/580 -- 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=47069 --- Comment #1 from Ole Erik Brennhagen <winehq.eloelo(a)spamgourmet.com> --- More information here: https://forums.lutris.net/t/final-fantasy-14-wont-start-after-latest-update-... Essentially, if you use mitmproxy to work around the url parsing problem you'll get stuck on "0030:fixme:mshtml:OleInPlaceActiveObject_TranslateAccelerator (0x1212de8)->(0x32f658)" -- 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=47069 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com --- Comment #2 from Jacek Caban <jacek(a)codeweavers.com> --- Created attachment 64251 --> https://bugs.winehq.org/attachment.cgi?id=64251 hacks The attached patch should take care of wrong URL. I looked at this some time ago and AFAIR the next problem is IWebBrowser2::get_Busy implementation, but I can't test it right now. -- 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=47069 Andrew Church <achurch+wine(a)achurch.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |achurch+wine(a)achurch.org -- 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=47069 --- Comment #3 from Ole Erik Brennhagen <winehq.eloelo(a)spamgourmet.com> --- (In reply to Jacek Caban from comment #2)
Created attachment 64251 [details] hacks
The attached patch should take care of wrong URL. I looked at this some time ago and AFAIR the next problem is IWebBrowser2::get_Busy implementation, but I can't test it right now.
Interesting! Is there anything a layman can do to help test/troubleshoot here? -- 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=47069 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #4 from Jacek Caban <jacek(a)codeweavers.com> --- Not really, what we really need is a proper fix. I attached it as a hint in case someone else wants to take a look before I get to it. It would be nice to confirm that it helps, but anyone working on it will have to do it himself anyway. -- 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=47069 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch -- 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=47069 pattietreutel <katyaberezyaka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka(a)gmail.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=47069 Steffen <envil(a)vexar.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |envil(a)vexar.de --- Comment #5 from Steffen <envil(a)vexar.de> --- Using the hacks patch from Jacek does make the Launcher work for the most part and we can actually login this way. Clicking the login button gives an error due to JSProtocolFactory_CreateInstance not being implemented. However pressing Enter instead of clicking the button does work to successfully login.
From what i can tell there is three different issues here:
1. The incorrect URL being accessed 2. WebBrowser_get_Busy preventing the Launcher from continuing 3. JSProtocolFactory_CreateInstance (and perhaps more) not implemented I guess it would make sense to make individual bug reports for each issue as they don't seem to be directly related to each other. -- 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=47069 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|mshtml |ieframe Summary|Final Fantasy XIV Launcher |Final Fantasy XIV Launcher |renders black |renders black (needs better | |get_Busy implementation) --- Comment #6 from Jacek Caban <jacek(a)codeweavers.com> --- Incorrect location.pathname is already covered by bug 37279 and I sent a patch for that. Let's keep this one for get_Busy() problem. BTW, we most likely don't need JSProtocolFactory_CreateInstance() implementation. We should use different code path for navigation earlier, which would not use it. -- 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=47069 Jacek Caban <jacek(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |d535df42f665a097ec721b10fb4 | |9d7b18f899be9 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #7 from Jacek Caban <jacek(a)codeweavers.com> --- Fixed in Git, thanks for the report. -- 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=47069 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |4.0 CC| |focht(a)gmx.net --- Comment #8 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, please always specify the used Wine version in bug reports - even if it's a non-vanilla/hacked variant (base version should be ok). 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=47069 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 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=47069 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.0.x -- 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=47069 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.0.x |--- --- Comment #10 from Michael Stefaniuc <mstefani(a)winehq.org> --- Removing the 4.0.x milestone from bug fixes included in 4.0.3. -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla