https://bugs.winehq.org/show_bug.cgi?id=48373
Bug ID: 48373 Summary: WriteProcessMemory? - Project Reality fails linking Launcher and Game Executable Product: Wine Version: 5.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: consolelogger@rhyta.com Distribution: ---
When running Project Reality, past the game menu and the loading in, an error shows up where it says: "Failed linking to the Launcher"
https://old.reddit.com/r/ProjectReality/comments/eg3xfu/lets_try_to_get_pr_w...
We have the luxury of being able to ask the devs about what might be going on there:
"If he joined a server, the Launcher has succeeded in opening the process and writing to it. These sort of issues are usually an anti virus not liking this kind of cross-process communication. In your case wine is probably incapable of WriteProcessMemory [...] Wine has both ReadProcessMemory and WriteProcessMemory, not sure what exactly the issue is but it shouldn't be that unless an odd bug has been hit [...] I suspect that or PR is triggering an unandlhed edge case or the failure reason is actually another one."
I was hoping to post a report with logs here, but couldn't find out what arguments are needed on WINEDEBUG= to have instances of ReadProcessMemory and WriteProcessMemory and adjacant "stuff" show up in the logs. How would I go about optaining a log that contains info helpful for solving this? I will do so as soon as I can and am happy to do testing and further research. Cheers.
https://bugs.winehq.org/show_bug.cgi?id=48373
consolelogger consolelogger@rhyta.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.realitymod.com/ | |downloads Distribution|--- |Debian
https://bugs.winehq.org/show_bug.cgi?id=48373
--- Comment #1 from consolelogger consolelogger@rhyta.com --- quoting a Project Reality developer about what the executables are doing: AlonTavor: "syscall-wise, can't think of anything other than open process and tons of Read/WriteProcessMemory... Which are already a pretty unusual thing to do in C#."
Still trying to figure out how to log this properly.
https://bugs.winehq.org/show_bug.cgi?id=48373
Lorenzo Ferrillo lorenzofer@live.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lorenzofer@live.it
--- Comment #2 from Lorenzo Ferrillo lorenzofer@live.it --- (In reply to consolelogger from comment #1)
quoting a Project Reality developer about what the executables are doing: AlonTavor: "syscall-wise, can't think of anything other than open process and tons of Read/WriteProcessMemory... Which are already a pretty unusual thing to do in C#."
Still trying to figure out how to log this properly.
For clarity, which version of Project Reality this is tested? ecouse for the last 1.5.5.x update I'm encountering bug 47480 and after that a wbemprox crash.
https://bugs.winehq.org/show_bug.cgi?id=48373
--- Comment #3 from Lorenzo Ferrillo lorenzofer@live.it --- Also for start the default wine log trace may show some information.
https://bugs.winehq.org/show_bug.cgi?id=48373
--- Comment #4 from consolelogger consolelogger@rhyta.com --- Created attachment 66150 --> https://bugs.winehq.org/attachment.cgi?id=66150 log (+trace) of PR 1.5.5.3 on wine5.0~rc2 failing linking to the Launcher
Above is a log of PR getting started through the launcher, navigating the main menu, starting a local coop game and deploying. Black overlay with the linking failure message.
I am doing all testing without network so far. Therefore I don't have opportunity to encounter issues from updating. I tested with PR 1.5.5.3 and 1.5.5.2 which were copied over from windows. I also will test with 1.5.0.0 and 1.3.0.0 installed on linux.
Also this might (or might not at all) be in part a regression, as people have reported no linking errors running PR locally in 2016 on wine versions 1.9.20 and earlier. https://www.realitymod.com/forum/showthread.php?t=143163 https://appdb.winehq.org/objectManager.php?sClass=version&iId=32379&... I couldn't test this yet, as dotnet fails to work for me on wine 2.0
https://bugs.winehq.org/show_bug.cgi?id=48373
--- Comment #5 from consolelogger consolelogger@rhyta.com --- I am comitted to provide all that is needed to allow good work on this.
Would anyone mind reviewing the log posted above to see if anything more can/needs to be logged? If so please change to NEEDSINFO and I will provide. Otherwise with the reddit discussion and others having tested aswell we can call this NEW.
When working on this make sure you install and test without network or decline all offers to update, otherwise the launcher will try to update the game and you will be blocked by unrelated Bug 47480.
https://bugs.winehq.org/show_bug.cgi?id=48373
bronze.alibi@startmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bronze.alibi@startmail.com
--- Comment #6 from bronze.alibi@startmail.com --- bug still there on wine 5.5