Dota 2 and L4D2 unable to retrieve important files #103

Closed
eugeneyche opened this Issue Jul 12, 2013 · 9 comments

Projects

None yet

4 participants

@eugeneyche

Seems to only apply to primusrun users, though I also get the issue with optirun -b primus.

Throws an error when trying to retrieve a .so file:

failed to dlopen /home/david/.local/share/Steam/SteamApps/common/dota 2 test/dota/bin/server.so error=dlopen: cannot load any more object with static TLS

@amonakov
Owner

I believe this issue should be fixed at Valve's end. We are exchanging e-mails to arrive to a good solution.

@amonakov
Owner

Last update to Dota2 should have fixed that; presumably a similar update for L4D2 is also forthcoming.

I have no immediate plans to change TLS in primus.

@amonakov amonakov closed this Jul 17, 2013
@pete-h
pete-h commented Jul 18, 2013

Thanks for looking into this and you e-mail-work with valve :)
As you said it's fixed in Dota 2.
I will check with L4D2 when the next update arrives.

@pete-h pete-h referenced this issue in ValveSoftware/Source-1-Games Jul 18, 2013
Closed

[L4D2] Could not load library matchmaking #450

@alexhultman

I don't get how this is considered solved any more than before?

If I use primusrun %command%, the game crashes instantly. If I use optirun -b primus %command%, the game shows the Dota loading screen and then crashes before any main menu appears. If I run steam itself using primusrun steam, Dota 2 runs perfectly (just like before this "fix").

Sorry but I can't see the difference. My Dota 2 Test for Linux even got an update today.

@amonakov
Owner

If I use primusrun %command%, the game crashes instantly.

This problem appeared with 64-bit overlay. This issue has been fixed in primus git, but distro packages might have not been updated yet (I don't have control over that).

If I use optirun -b primus %command%, the game shows the Dota loading screen and then crashes before any main menu appears.

This is some other bug then. This bug is about the following failure: error=dlopen: cannot load any more object with static TLS

@alexhultman

So the fix lies in both primus and the games (Dota 2, L4D2) themselves?

@amonakov
Owner

Different specific bugs have required different fixes in different projects. "Dota 2 crashes" is not a specific bug.

@alexhultman

Yeah I understand that already, ofc. I mean, getting Dota 2 to run properly with primusrun was two fixes if I understand this correctly: one in primus itself and one in Dota 2 the game client? I'm wondering because if the fix was just in primus, then L4D2 and other games would automatically benefit from the fix. But if it was a two part bug fix (in game as well), other game clients needs to be updated (which is a little more time consuming, ergo my wondering).

@pete-h
pete-h commented Jul 18, 2013

@alexhultman no, not everyone needs two fixes for dota2 to run properly. I only needed one fix for dota2 to work. you have two different bugs, so you need two fixes. It's not a two part bugfix, it's two different bugs...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment