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

liborc from steam-runtime is too old for newer pulseaudio #2924

Closed
arichardson opened this issue Oct 16, 2013 · 5 comments
Closed

liborc from steam-runtime is too old for newer pulseaudio #2924

arichardson opened this issue Oct 16, 2013 · 5 comments

Comments

@arichardson
Copy link

I have no sound in most games. The following line is printed to the

/usr/bin/pulseaudio: symbol lookup error: /usr/lib64/libpulsecore-4.0.so: undefined symbol: orc_program_new_from_static_bytecode

steam runtime has 0.4.16 of liborc, however that function was only introduced in 0.4.17. Deleting those libs from the steam runtime makes the sound work again since it then uses the system libs

Is this the right place to report this issue, or should it be ValveSoftware/steam-runtime?

@johndrinkwater
Copy link
Contributor

Had another user in #steamlug report the issue,

Unbeerable> Hi guys. My sound in games has gone after steam update. Is there a common way to resolve an issue? Maybe a point to start from.
Unbeerable> johndrinkwater, Fedora 19
Unbeerable> i see an error about pulseaudio, "PulseAudio connect failed (used only for Mic Volume Control) with error: Access denied"
Unbeerable> I can listen the music
Unbeerable> well, now I have new error "/usr/bin/pulseaudio: symbol lookup error: /lib64/libpulsecore-3.0.so: undefined symbol: orc_program_new_from_static_bytecode"
Unbeerable> and google says almost nothing about it

@josefbacik
Copy link

I'm seeing the same error as well

/usr/bin/pulseaudio: symbol lookup error: /lib64/libpulsecore-3.0.so: undefined symbol: orc_program_new_from_static_bytecode

@ghost ghost assigned slouken Oct 28, 2013
@FelixSchwarz
Copy link

actually this is a duplicate of #2834

@Plagman
Copy link
Member

Plagman commented Mar 11, 2014

This is fixed and will be rolled out in a future version of the runtime. Thanks!

@tpruzina
Copy link

Hm, I guess fellas should be able to fix this via LD_PRELOAD hacks.

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

No branches or pull requests

7 participants