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@winehq.org Reporter: winehq.eloelo@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.
https://bugs.winehq.org/show_bug.cgi?id=47069
Ole Erik Brennhagen winehq.eloelo@spamgourmet.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://github.com/ValveSof | |tware/Proton/issues/580
https://bugs.winehq.org/show_bug.cgi?id=47069
--- Comment #1 from Ole Erik Brennhagen winehq.eloelo@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)"
https://bugs.winehq.org/show_bug.cgi?id=47069
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com
--- Comment #2 from Jacek Caban jacek@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.
https://bugs.winehq.org/show_bug.cgi?id=47069
Andrew Church achurch+wine@achurch.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |achurch+wine@achurch.org
https://bugs.winehq.org/show_bug.cgi?id=47069
--- Comment #3 from Ole Erik Brennhagen winehq.eloelo@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?
https://bugs.winehq.org/show_bug.cgi?id=47069
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #4 from Jacek Caban jacek@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.
https://bugs.winehq.org/show_bug.cgi?id=47069
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=47069
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47069
Steffen envil@vexar.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |envil@vexar.de
--- Comment #5 from Steffen envil@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.
https://bugs.winehq.org/show_bug.cgi?id=47069
Jacek Caban jacek@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@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.
https://bugs.winehq.org/show_bug.cgi?id=47069
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |d535df42f665a097ec721b10fb4 | |9d7b18f899be9 Resolution|--- |FIXED Status|NEW |RESOLVED
--- Comment #7 from Jacek Caban jacek@codeweavers.com --- Fixed in Git, thanks for the report.
https://bugs.winehq.org/show_bug.cgi?id=47069
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |4.0 CC| |focht@gmx.net
--- Comment #8 from Anastasius Focht focht@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
https://bugs.winehq.org/show_bug.cgi?id=47069
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.10.
https://bugs.winehq.org/show_bug.cgi?id=47069
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.0.x
https://bugs.winehq.org/show_bug.cgi?id=47069
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.0.x |---
--- Comment #10 from Michael Stefaniuc mstefani@winehq.org --- Removing the 4.0.x milestone from bug fixes included in 4.0.3.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla