https://bugs.winehq.org/show_bug.cgi?id=47198
Matías Zúñiga matias.nicolas.zc@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #66892|0 |1 is obsolete| |
--- Comment #107 from Matías Zúñiga matias.nicolas.zc@gmail.com --- Created attachment 70550 --> https://bugs.winehq.org/attachment.cgi?id=70550 Alternative patch by using a fake cs segment
(In reply to Manuel from comment #106)
With the last update of the LoL client the Wine version, used so far, no longer is able to run the client. Most probably because they updated to CEF-91.
A up to date wine-staging can start the client but then will not allow to actually play the game. So this issue seems to have been fixed with later wine-staging versions.
I also tried with regular Wine (GIT-version from today) and this also fails to start the client. So whatever fixes this has to be a staging patch.
So maybe that's a good point where someone with the required knowledge could try to port the patches to a more modern Wine version?
The only alternative, I can think of, would be backporting whatever wine-staging patch is needed. But, so far, I haven't found the correct one and I'm not sure if backporting will be possible at all.
As i commented recently in Bug 49412, I'm able to start a game using the last posted "Restore original Staging 32 bit syscall thunks format" patch, and the attached "Alternative patch by using a fake cs segment" patch.
Keep in mind that, while i can start the client and play a game, I can not update the riot client: "Update failed: Failed getting path to current executable: File path could not be found in a mapped drive: ??\C:\Riot Games\Riot Client\RiotClientServices.exe"... but that probably something not-so-difficult to fix if is a wine bug (and not something with my configuration), and someone has time to debug it.