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

Steam can't find libpulsecommon.so #27260

Closed
chilledfrogs opened this issue Dec 18, 2020 · 4 comments
Closed

Steam can't find libpulsecommon.so #27260

chilledfrogs opened this issue Dec 18, 2020 · 4 comments

Comments

@chilledfrogs
Copy link
Contributor

chilledfrogs commented Dec 18, 2020

System

  • xuname: Void 5.9.14_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFF
  • package: steam-1.0.0.68_1

Expected behaviour

Steam launches

Actual behaviour

Fatal error on launch:

Error: You are missing the following 32-bit libraries, and Steam may not run:
libpulsecommon-14.0.so

Succeeded eventually by:

Failed to load steamui.so - dlerror(): libpulsecommon-14.0.so: wrong ELF class: ELFCLASS64

So it seems to somehow (only?) see the 64-bit shlib even though I have the 32-bit one as well in /usr/lib32/pulseaudio/libpulsecommon-14.0.so.

I can work around this in the meantime by prepending (well really just setting here since I don't have anything in this variable by default) /usr/lib32/pulseaudio to LD_LIBRARY_PATH when launching steam from the command line.

Steps to reproduce the behaviour

Just launch Steam
(Tried steam --reset just in case, no dice)

@Acetsetebos
Copy link

I'm having the same problem except the second error reads:
Failed to load steamui.so - dlerror(): libpulsecommon-14.0.so: cannot open shared object file: No such file or directory
I checked and /usr/lib32/pulseaudio/libpulsecommon-14.0.so does exist.

@ericonr
Copy link
Member

ericonr commented Dec 18, 2020

The package is being rebuilt and should be fixed soon.

@sburris0
Copy link
Contributor

Just tested with pulseaudio-14.0_2 and it works for me

@Johnnynator
Copy link
Member

Johnnynator commented Dec 18, 2020

fixed with e496c56

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

5 participants