https://bugs.winehq.org/show_bug.cgi?id=43518
Bug ID: 43518 Summary: Titanfall2.exe crashes immediately upon splash screen Product: Wine-staging Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: jdally987@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Created attachment 58908 --> https://bugs.winehq.org/attachment.cgi?id=58908 Most recent backtrace (using Windows 7 setting)
I used wine-staging 2.13 from the AUR and using the default (64-bit) prefix, installed Origin using this test result and the linked instructions:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=26175&...
Origin works well enough, and downloads Titanfall. It's playable at 45% so I hit play, and it usually gets to the "Respawn" splash screen with the logo (sometimes not at all) before it stops responding and wine throws an error.
I've attached the backtrace and terminal output, from the latter it looks like it might be a .dll error, which the first couple lines of the backtrace corroborate (bcrypt.dll?)
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #1 from jdally987@gmail.com --- Created attachment 58909 --> https://bugs.winehq.org/attachment.cgi?id=58909 Older backtrace, using Windows 10 setting in winecfg
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #2 from jdally987@gmail.com --- (In reply to jdally987 from comment #0)
Forgot to add for reproducibility, that I downloaded the legacy OriginThinClient.exe installer from the link; and also didn't bother setting winecfg to Windows XP for these tests. I tried that originally but it didn't make a difference, especially since you HAVE to set it to Windows 7 later, as TF2 will only run on a 64-bit Windows 7 and up system.
Also I'm using the default amdgpu mesa open-source drivers that install with Manjaro. A commenter on the linux_gaming subreddit said this DX11 game should work better with the gl_arb_compatibility in the proprietary AMDGPU-PRO drivers, but those aren't supported by my distro yet.
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #3 from jdally987@gmail.com --- Created attachment 58910 --> https://bugs.winehq.org/attachment.cgi?id=58910 Output when trying to open Titanfall2.exe in wine from terminal
https://bugs.winehq.org/show_bug.cgi?id=43518
jdally987@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=43518
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Titanfall2.exe crashes |Titanfall2 needs |immediately upon splash |bcrypt.dll.BCryptExportKey |screen |
--- Comment #4 from Austin English austinenglish@gmail.com --- (In reply to jdally987 from comment #3)
Created attachment 58910 [details] Output when trying to open Titanfall2.exe in wine from terminal
Fyi, that looks like you have a messed up prefix, probably manually cooped DLLs from Windows to the wrong wine directory.
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #5 from jdally987@gmail.com --- (In reply to Austin English from comment #4)
(In reply to jdally987 from comment #3)
Created attachment 58910 [details] Output when trying to open Titanfall2.exe in wine from terminal
Fyi, that looks like you have a messed up prefix, probably manually cooped DLLs from Windows to the wrong wine directory.
Yeah, I was wondering about the MSVCP120.dll and msvcr120.dll stuff but Origin opens up and works fine from command line despite the errors, and Titanfall too (until it crashes a couples seconds in).
I've reinstalled wine multiple times and only ever set up a fresh prefix by running winecfg, so all the default options always end up in giving me that error. Not sure if it's part of the problem or not.
If I had to guess I'd say the real problem is the lack of a BCryptExportKey implementation in bcrypt.dll, as seen at the top of the backtrace.
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #6 from jdally987@gmail.com --- Created attachment 59103 --> https://bugs.winehq.org/attachment.cgi?id=59103 First crash log after hitting "play" (wine-staging 2.15)
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #7 from jdally987@gmail.com --- Created attachment 59104 --> https://bugs.winehq.org/attachment.cgi?id=59104 First crash log after hitting "play" (wine-staging 2.15)
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #8 from jdally987@gmail.com --- (In reply to jdally987 from comment #7)
Created attachment 59104 [details] First crash log after hitting "play" (wine-staging 2.15)
Whoops, that second one was meant to say "second crash log", I just copied that line when I uploaded the second attachment :----)
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #9 from jdally987@gmail.com --- Update:
So now since the wine-staging 2.15-2 patch is out, I tried this again.
Wine 2.15 broke Origin starting up after installing it for some reason, but it looks like this most recent patch fixed it. So, installed Titanfall2 again, booted it up.
First wine crashes with "The program (unidentified) has encountered a serious error and needs to close". I hit close and then it does it once again. I've attached the backtraces for these 2 errors; they look pretty similar but I can't tell if they're exactly the same.
Anyway after that, it does indeed start up; it still gets to the "RESPAWN" text & logo splash screen, fades in & flickers for a second, then crashes with an Engine Error: "**** Error 0xc000000d returned by BCryptExportKey".
I know a BCryptExportKey was included in wine-staging 2.15 which got me excited since this seemed to be the problem before. Now at least it doesn't crash with an entire fatal error providing a backtrace and everything, but only a small error code. Looked it up & couldn't find anything though. That's all I've got for now.
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #10 from jdally987@gmail.com --- Created attachment 59105 --> https://bugs.winehq.org/attachment.cgi?id=59105 Screenshot of the error that actually crashes the game after it successfully starts
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #11 from Michael Müller michael@fds-team.de --- The crashes you encountered were most probably caused by ArchLinux passing unsupported build flags to configure (see bug 43530).
Can you post a WINEDEBUG=+bcrypt log with wine-staging 2.15-2?
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #12 from jdally987@gmail.com --- Created attachment 59147 --> https://bugs.winehq.org/attachment.cgi?id=59147 Log when running Titanfall2.exe preceded by WINEDEBUG=+bcrypt command
See my comments right about in the middle of the file, that marks the point at which, after Origin opened itself (which was everything before that), Titanfall started to throw out the errors I talked about previously. I see a couple lines of bcrypt stuff in there so that might hold a clue.
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #13 from jdally987@gmail.com --- (In reply to Michael Müller from comment #11)
The crashes you encountered were most probably caused by ArchLinux passing unsupported build flags to configure (see bug 43530).
Can you post a WINEDEBUG=+bcrypt log with wine-staging 2.15-2?
Sure thing, see my attachment. Not sure if I got everything, terminal cut off the top since the program dumped a million lines in terminal all at once. Also worth noting I'm not on Arch, on Manjaro (17.0.4).
https://bugs.winehq.org/show_bug.cgi?id=43518
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine-staging |Wine
--- Comment #14 from Michael Müller michael@fds-team.de --- The implementation of BCryptExportKey is also missing in the development version and the bug is therefore not specific to Wine Staging. Moving the bug into the Wine product.
https://bugs.winehq.org/show_bug.cgi?id=43518
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Titanfall2 needs |Titanfall2 needs |bcrypt.dll.BCryptExportKey |bcrypt.dll.BCryptExportKey | |(OpaqueKeyBlob format)
https://bugs.winehq.org/show_bug.cgi?id=43518
jdally987@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|2.13 |2.15
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #15 from jdally987@gmail.com --- Michael, that makes sense, but Origin doesn't open in the non-staging version of Wine, rendering Titanfall2 incapable of running in the first place.
https://bugs.winehq.org/show_bug.cgi?id=43518
John Chaney jdally987@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |bcrypt
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #16 from John Chaney jdally987@gmail.com --- Created attachment 59467 --> https://bugs.winehq.org/attachment.cgi?id=59467 backtrace3 - page fault on write access, in wine-staging 2.18
https://bugs.winehq.org/show_bug.cgi?id=43518
--- Comment #17 from John Chaney jdally987@gmail.com --- Updated to wine-staging 2.18. So now instead of the bcrypt error, titanfall doesn't start to the splash screen or anything at all, but immediately exits with the "page fault on write access..." error in the attached backtrace3.txt.
I'm not sure what the procedure for updating this bug is if it's now not related to bcrypt anymore, and since this is 3 versions of wine above when I first filed the bug. Anyway though this seems like progress, maybe.
https://bugs.winehq.org/show_bug.cgi?id=43518
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |f352837868192907ef2ac6ad0d7 | |7f40700479581
--- Comment #18 from Hans Leidekker hans@meelstraat.net --- Should be fixed by f352837868192907ef2ac6ad0d77f40700479581.
https://bugs.winehq.org/show_bug.cgi?id=43518
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #19 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.5.
-
wine-bugs＠winehq.org