[Bug 49567] New: Warframe launcher ntdll dead locking since 5.10 staging, problem persists in 5.11 staging
https://bugs.winehq.org/show_bug.cgi?id=49567
Bug ID: 49567 Summary: Warframe launcher ntdll dead locking since 5.10 staging, problem persists in 5.11 staging Product: Wine-staging Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: katharine.chui@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 67707 --> https://bugs.winehq.org/attachment.cgi?id=67707 log at default log level, wine staging 5.11
Since wine 5.10 staging, warframe launher can no longer get through it's checking for new content stage and would get stuck there seemingly indefinitely with log message similar with
``` 0330:err:ntdll:RtlpWaitForCriticalSection section 0x7f0c224d64c0 "../../../dlls/ntdll/unix/virtual.c: csVirtual" wait timed out in thread 0330, blocked by 02e4, retrying (60 sec) ```
The said problem was not encountered on wine 5.9 staging, and is also observed on wine 5.11 staging
below attaches log at default log level
https://bugs.winehq.org/show_bug.cgi?id=49567
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
--- quote from attachment 67707 --- [root@Katharine-PC Tools]# $WINELOADER Launcher.exe (...) [root@Katharine-PC Tools]# ^C bash: __vte_prompt_command: command not found [root@Katharine-PC Tools]# exit logout [katharine@Katharine-PC warframe]$ bash launcher.sh bash: __vte_prompt_command: command not found [root@Katharine-PC Tools]# $WINELOADER Launcher.exe (...) --- end quote
I don't know if it relates to your issue but:
https://wiki.winehq.org/FAQ#Should_I_run_Wine_as_root.3F NEVER run Wine as root!
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49567
--- Comment #2 from Katharine katharine.chui@gmail.com --- It's a bwrap container.
https://bugs.winehq.org/show_bug.cgi?id=49567
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to Katharine from comment #2)
It's a bwrap container.
Ok. You understand that you're responsible if things breaks when you use that.
Now back to the issue:
Warframe.x64.exe is a 64-bit application. It probably depends on 64-bit syscall thunks.
I think you're facing the same issue as described in bug 49565. Please read that bug starting from that comment: https://bugs.winehq.org/show_bug.cgi?id=49565#c2
In short: The wine-staging patchset that provides 64-bit syscall thunks to 64-bit applications was temporarily disabled due to reworking of ntdll. The applications that depends on it are broken again (bug 45349). A fix was released and will be available in wine/staging 5.13.
The other bugs were reported and fixed for World of Warcraft. When it is released, it would be nice if you could confirm that wine 5.13 fixes the issue with Warframe too.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49567
--- Comment #4 from Zebediah Figura z.figura12@gmail.com --- Can this be tested again please, ideally with upstream Wine?
https://bugs.winehq.org/show_bug.cgi?id=49567
Dmitry Skvortsov (Iglu47) lvb.crd@protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lvb.crd@protonmail.com
--- Comment #5 from Dmitry Skvortsov (Iglu47) lvb.crd@protonmail.com --- Created attachment 68563 --> https://bugs.winehq.org/attachment.cgi?id=68563 wine-staging-5.20.r17.g950d7c6c.log
wine-staging 5.20 950d7c6c430c746c944ef09678e21fc73fc74311 game version (msi-installer): Warframe.2020.10.27.18.05.24
it looks like the initial issue problem is not present anymore, and everything works as before given https://bugs.winehq.org/show_bug.cgi?id=44985#c36 the launcher starts downloading some small update and then re-launching itself. all this happens successfully (I attach the terminal output)
https://bugs.winehq.org/show_bug.cgi?id=49567
--- Comment #6 from Dmitry Skvortsov (Iglu47) lvb.crd@protonmail.com --- Created attachment 68564 --> https://bugs.winehq.org/attachment.cgi?id=68564 wine-5.20.r169.gdfa4c079413.log
wine 5.20 dfa4c07941322dbcad54507cd0acf271a6c719ab game version (msi-installer): Warframe.2020.10.27.18.05.24
everything is the same on plain Wine
https://bugs.winehq.org/show_bug.cgi?id=49567
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |ntdll Product|Wine-staging |Wine Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #7 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Dmitry Skvortsov (Iglu47) from comment #5)
it looks like the initial issue problem is not present anymore, and everything works as before given https://bugs.winehq.org/show_bug.cgi?id=44985#c36
(In reply to Dmitry Skvortsov (Iglu47) from comment #6)
everything is the same on plain Wine
Hello,
Reported fixed.
I'll assume it was a dupe of bug 49565, which was fixed in wine-staging, and then a dupe of bug 45349, which was upstreamed afterwards.
Regards.
*** This bug has been marked as a duplicate of bug 45349 ***
https://bugs.winehq.org/show_bug.cgi?id=49567
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Duplicate.
-
WineHQ Bugzilla