https://bugs.winehq.org/show_bug.cgi?id=54240
Bug ID: 54240 Summary: wineserver crash when calling an rpc stub Product: Wine Version: 8.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rpc Assignee: wine-bugs@winehq.org Reporter: memory.thrasher@gmail.com Distribution: ---
"M.A.R.S." game would immediately crash when attempting to launch due to a missing (stubbed) function. I implemented the function in the linked merge request. Game submitted to app db, also linked below.
https://gitlab.winehq.org/wine/wine/-/merge_requests/1888
https://appdb.winehq.org/objectManager.php?sClass=version&iId=41241&...
With the above patch, the game progresses to a splashscreen before crashing without any helpful errors, likely due to "easy anti-cheat" software. With tracing enabled, I was able to confirm the rpc endpoint generated by my patch was functioning correctly.
https://bugs.winehq.org/show_bug.cgi?id=54240
Sidney Kelley memory.thrasher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=54240
Sidney Kelley memory.thrasher@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |memory.thrasher@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=54240
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- Wineserver should never crash, even if wine programs crash, meaning there's a separate bug here. Can you get a backtrace for the server crash?
https://bugs.winehq.org/show_bug.cgi?id=54240
--- Comment #2 from Sidney Kelley memory.thrasher@gmail.com --- Created attachment 73796 --> https://bugs.winehq.org/attachment.cgi?id=73796 MaLauncher.,exe output
https://bugs.winehq.org/show_bug.cgi?id=54240
--- Comment #3 from Sidney Kelley memory.thrasher@gmail.com --- (In reply to Zeb Figura from comment #1)
Wineserver should never crash, even if wine programs crash, meaning there's a separate bug here. Can you get a backtrace for the server crash?
Unfortunately no, I was never able to get much of a backtrace. I've attached the entire output of the combined wineserver and app. The line ending in "aborting" is what prompted me to implement the rpc stub.
I launches them both like so `wineserver -f -p60 &>vanillawine.err & wine MaLauncher.exe &>>vanillawine.err` to generate the attached log, and a few seconds later, bash reports "done" on the wineserver job ('job' in the bash sense of backgrounded process), meaning it closed before it's 60 second idle time, which is the only reason I say it crashed. It's possible the bug is with the handling of the 60 second persistence flag, but my money is on the "internal crash" of winedbg breaking an assumption/contract with wineserver. Note that I'm mostly an outsider with only a vague idea how these processes fit together.
https://bugs.winehq.org/show_bug.cgi?id=54240
--- Comment #4 from Sidney Kelley memory.thrasher@gmail.com --- For the record, I've given up on getting this specific game to work. I submitted the bug report and patch to help the wine project but I am not willing to spend much more time on it. It's free to download and (attempt to) play so there's nothing stopping anybody else from picking up where I left off.
https://bugs.winehq.org/show_bug.cgi?id=54240
Bernhard Übelacker bernhardu@mailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org
--- Comment #5 from Bernhard Übelacker bernhardu@mailbox.org --- I tried to reproduce the wineserver crash.
"Unfortunately" I could not observe a crash of wineserver with vanilla wine 8.11 (or wine-staging).
I just received the unimplemented function "crash" (which is handled by the bug submitters patch).
And the crash in winedbg happens because MaLauncher.exe has some anti debugging in place and calls ExitProcess while winedbg is not yet done. To avoid the winedbg crash I created bug 55187.
With the patch by Sidney Kelley the process continues. It shows a splash screen "easy ANTI-CHEAT" and a growing progress bar. After a while the message: "Failed to launch the game(waiting time out), please start MaLauncher again."
Following logfile seems related: "~/.wine/drive_c/users/benutzer/AppData/Roaming/EasyAntiCheat/590/loader.log" Shows a download failure from: "https://download.eac-cdn.com/api/v1/games/590/client/wine32/download/?uuid=..." This looks like bug 44235.
Therefore I assume this bug should concentrate at the unimplemented function rpcrt4.dll.RpcServerUseAllProtseqsIf.
-
WineHQ Bugzilla