protonscr

Setting category of a game causes steam to crash

steamclosed
ValveSoftware/steam-for-linux#3491 · opened 2014-09-18 by HalosGhost · updated 2014-09-19 · 4 comments · github
HHalosGhost 2014-09-18 github

I can find no logical explanation for this, nor is there a helpful error message (as far as I can tell) to help point me in the right direction. You can find the full terminal output from steam as this happens on my machine here.

TTele42 2014-09-19 github

This appears to be the critical detail:

libGL error: dlopen /usr/lib32/xorg/modules/dri/nouveau_dri.so failed (/home/halosghost/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /usr/lib32/xorg/modules/dri/nouveau_dri.so))
libGL error: unable to load driver: nouveau_dri.so

which leads to:

Error: OpenGL GLX context is not using direct rendering, which may cause performance problems.

This usually means that the libstdc++.so.6 in the steam runtime is too old for your opengl driver (nouveau).

HHalosGhost 2014-09-19 github

Those are both issues that have caused me some pain, but they have been present for me for a lot longer than the problem this issue concerns. Furthermore, I have the latest libstdc++ that my OS offers (Archlinux).

TTele42 2014-09-19 github

@HalosGhost Just because you have a newer userspace does not mean steam is using it because steam pulls it's libraries from the steam runtime (ment for ubuntu 12.04) before it checks the system libraries. You can either manually remove the offending libraries from the steam runtime or provide all the dependencies and use the STEAM_RUNTIME=0 env variable. I recommend the first choice.

HHalosGhost 2014-09-19 github

Okay, how would I go about explicitly removing a particular library from the runtime so it uses my system library?

[edit]: nevermind, I figured it out, and it appears the issue has been resolved. Sorry for the noise!

Nothing extracted yet.