Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Origin games fail to connect with overlay steam, but work with flatpak steam #270

Open
mgidding opened this issue Jun 23, 2020 · 4 comments

Comments

@mgidding
Copy link

Using Steam installed via the overlay will result in Origin connection errors with both Titanfall 2 and Jedi: Fallen order.

Titanfall 2 gives the error "we are unable to connect to ea servers to activate displayname field missing try again later"
Jedi: Fallen Order gives the error "we've noticed your computer is currently offline, to activate your game on this computer using your ea account you'll need to connect to the internet"

However, when using the Flatpak steam client on the same computer, both games run fine.

I have the steamruntime USE flag set, and I have also tried installing steam-runtime-openssl. It seems that some package is missing on Gentoo, but I wouldn't know where to look.

@chewi
Copy link
Collaborator

chewi commented Jun 23, 2020

I'm afraid I don't have either of these games. Running Steam from the terminal may reveal something useful in the output so please paste it.

@mgidding
Copy link
Author

Overlay steam (game boot at line 275): https://gist.github.com/mgidding/4a1434c9b1bb460b20573096ea395391

Flatpak steam (game boot at line 313): https://gist.github.com/mgidding/266f7d5e07aea72142bb0e9932ee8122

Perhaps [0624/163037.226692:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018 is relevant?

@chewi
Copy link
Collaborator

chewi commented Jun 24, 2020

Try updating app-misc/ca-certificates and dev-libs/nss if they're not on the latest. If that doesn't work, build dev-libs/nss with USE=utils and try this:

modutil -dbdir "sql:${HOME}/.pki/nssdb" -add p11-kit-trust -libfile /usr/lib64/pkcs11/p11-kit-trust.so

This is really just a hunch. It just so happens I had an NSS-related issue this week where I had to run that command to fix it.

@mgidding
Copy link
Author

Sadly that didn't change anything. I'm really not sure how to narrow down the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants