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 searches for libasound_module_pcm_pulse.so at the wrong location #1199

Closed
ghost opened this Issue Feb 2, 2013 · 22 comments

Comments

Projects
None yet
5 participants
@ghost

ghost commented Feb 2, 2013

I am using Pulseaudio with my Xonar DG (The only way to get volume control working) and Steam looks for the libsound_module_pcm_pulse.so at the wrong location.

OS: Arch Linux x86_64

Error message:
AL lib: pulseaudio.c:612: Context did not connect: Access denied
ALSA lib dlmisc.c:254:(snd1_dlobj_cache_get) Cannot open shared library /usr/lib/i386-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so
AL lib: alsa.c:512: Could not open playback device 'default': No such device or address
Failed to open digital audio driver Couldn't open OAL device.

The libasound_module_pcm_pulse.so file is located at /usr/lib32/alsa-lib/

Starting Steam with STEAM_RUNTIME=0 steam works and I can listen to sound just fine.

@ghost ghost assigned slouken Feb 2, 2013

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 2, 2013

Does this workaround solve things for you?
If /var/lib/dbus/machine-id doesn't exist and /etc/machine-id does, try this:
sudo ln -s /etc/machine-id /var/lib/dbus/machine-id

slouken commented Feb 2, 2013

Does this workaround solve things for you?
If /var/lib/dbus/machine-id doesn't exist and /etc/machine-id does, try this:
sudo ln -s /etc/machine-id /var/lib/dbus/machine-id

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 2, 2013

/var/lib/dbus/machine-id did not exist. Sadly your workaround didn't work as well.

Here is the console output without STEAM_RUNTIME=0:
http://ompldr.org/vaGJudQ

Here with STEAM_RUNTIME=0:
http://ompldr.org/vaGJudg

Here is the system information:
http://ompldr.org/vaGJueQ

This is strange:
Operating System Version:
Linux (64 bit)

As far as a I know it should be "Arch Linux" (64 bit). Steam doesn't detect my distro it seems.

ghost commented Feb 2, 2013

/var/lib/dbus/machine-id did not exist. Sadly your workaround didn't work as well.

Here is the console output without STEAM_RUNTIME=0:
http://ompldr.org/vaGJudQ

Here with STEAM_RUNTIME=0:
http://ompldr.org/vaGJudg

Here is the system information:
http://ompldr.org/vaGJueQ

This is strange:
Operating System Version:
Linux (64 bit)

As far as a I know it should be "Arch Linux" (64 bit). Steam doesn't detect my distro it seems.

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 2, 2013

The permission denied message usually means the machine ID wasn't detected properly.
Can you attach the output from these commands?
STEAM_RUNTIME=0 strace -f steam 2>&1 | grep "open(" >/tmp/steam_runtime_disabled.txt
STEAM_RUNTIME=1 strace -f steam 2>&1 | grep "open(" >/tmp/steam_runtime_enabled.txt

Thanks!

slouken commented Feb 2, 2013

The permission denied message usually means the machine ID wasn't detected properly.
Can you attach the output from these commands?
STEAM_RUNTIME=0 strace -f steam 2>&1 | grep "open(" >/tmp/steam_runtime_disabled.txt
STEAM_RUNTIME=1 strace -f steam 2>&1 | grep "open(" >/tmp/steam_runtime_enabled.txt

Thanks!

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 2, 2013

steam_runtime_disabled.txt: http://ompldr.org/vaGJvaA
steam_runtime_enabled.txt: http://ompldr.org/vaGJvaQ

ghost commented Feb 2, 2013

steam_runtime_disabled.txt: http://ompldr.org/vaGJvaA
steam_runtime_enabled.txt: http://ompldr.org/vaGJvaQ

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 2, 2013

Can you run the full strace without the grep and look for the calls around the message "Context did not connect"? From the current traces it looks like pulseaudio finds the machine id and the cookie file and is all happy.

slouken commented Feb 2, 2013

Can you run the full strace without the grep and look for the calls around the message "Context did not connect"? From the current traces it looks like pulseaudio finds the machine id and the cookie file and is all happy.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 2, 2013

I made a full strace log and I cannot find this message at all. Is there something particular I need to look for?
I can't post here the URL because I don't know if my password is saved inside the log.

ghost commented Feb 2, 2013

I made a full strace log and I cannot find this message at all. Is there something particular I need to look for?
I can't post here the URL because I don't know if my password is saved inside the log.

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 2, 2013

I'm looking for "AL lib: pulseaudio.c:612: Context did not connect: Access denied"
It should show up if you did strace -f ... maybe the message was truncated in the log? Maybe look just for "AL lib"?

slouken commented Feb 2, 2013

I'm looking for "AL lib: pulseaudio.c:612: Context did not connect: Access denied"
It should show up if you did strace -f ... maybe the message was truncated in the log? Maybe look just for "AL lib"?

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 2, 2013

Specifically I'm looking for things right before that log message in the trace with the same process ID as that log message, anything indicating a failure to open a file, or a network message with a rejection message or something like that.

slouken commented Feb 2, 2013

Specifically I'm looking for things right before that log message in the trace with the same process ID as that log message, anything indicating a failure to open a file, or a network message with a rejection message or something like that.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 2, 2013

Sadly I can't find anything useful. I saw you made a patch for steam-runtime to fix this issue.

I will wait until the patch is deployed.

ghost commented Feb 2, 2013

Sadly I can't find anything useful. I saw you made a patch for steam-runtime to fix this issue.

I will wait until the patch is deployed.

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 2, 2013

I don't think the patch will fix your issue. Everyone else was fixed by the machine-id symbolic link.
If you want you can send the log to slouken@libsdl.org

Or you can just wait and see if the update fixes it. :)

slouken commented Feb 2, 2013

I don't think the patch will fix your issue. Everyone else was fixed by the machine-id symbolic link.
If you want you can send the log to slouken@libsdl.org

Or you can just wait and see if the update fixes it. :)

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 2, 2013

I sent you the log file. I hope you can find something useful.

ghost commented Feb 2, 2013

I sent you the log file. I hope you can find something useful.

@nikod

This comment has been minimized.

Show comment
Hide comment
@nikod

nikod Feb 3, 2013

Same problem here, happened after the last update, a workaround is make a symlink of alsa-lib from lib32 on lib/i386-linux-gnu

nikod commented Feb 3, 2013

Same problem here, happened after the last update, a workaround is make a symlink of alsa-lib from lib32 on lib/i386-linux-gnu

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 3, 2013

@nikod This is a terrible idea. @slouken found out what is the problem and I guess it will get fixed soon. Until then, use this command instead: ln -s /run/user/1000/pulse/native /var/run/pulse/native

ghost commented Feb 3, 2013

@nikod This is a terrible idea. @slouken found out what is the problem and I guess it will get fixed soon. Until then, use this command instead: ln -s /run/user/1000/pulse/native /var/run/pulse/native

@nikod

This comment has been minimized.

Show comment
Hide comment
@nikod

nikod Feb 3, 2013

I know is not the best idea but is a workaround if you need the sound... anyway I did the symlink to /var/run/ but didn't do anything for me, no sound at all.

nikod commented Feb 3, 2013

I know is not the best idea but is a workaround if you need the sound... anyway I did the symlink to /var/run/ but didn't do anything for me, no sound at all.

@disiu

This comment has been minimized.

Show comment
Hide comment
@disiu

disiu Feb 3, 2013

I've got this issue too after the last update. 1 February.
running STEAM_RUNTIME=0 gave me the audio.

@vorenon what that command do ?

I'm using Manjaro Linux which is Arch based.

disiu commented Feb 3, 2013

I've got this issue too after the last update. 1 February.
running STEAM_RUNTIME=0 gave me the audio.

@vorenon what that command do ?

I'm using Manjaro Linux which is Arch based.

@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 3, 2013

We found a better workaround until the next update. If you have XDG_RUNTIME_DIR set, you can do this:
export PULSE_RUNTIME_PATH=$XDG_RUNTIME_DIR/pulse

slouken commented Feb 3, 2013

We found a better workaround until the next update. If you have XDG_RUNTIME_DIR set, you can do this:
export PULSE_RUNTIME_PATH=$XDG_RUNTIME_DIR/pulse

@onoffleftright

This comment has been minimized.

Show comment
Hide comment
@onoffleftright

onoffleftright Feb 3, 2013

@slouken That did not work for me on Arch Linux 64, and yes I have the XDG_RUNTIME_DIR set:

➜  ~  echo $XDG_RUNTIME_DIR
/run/user/1000

onoffleftright commented Feb 3, 2013

@slouken That did not work for me on Arch Linux 64, and yes I have the XDG_RUNTIME_DIR set:

➜  ~  echo $XDG_RUNTIME_DIR
/run/user/1000
@slouken

This comment has been minimized.

Show comment
Hide comment
@slouken

slouken Feb 3, 2013

@JKelsey, you may have to do both the PULSE_RUNTIME_PATH workaround and the /etc/machine-id symlink workaround. If you do both, does sound start working?

slouken commented Feb 3, 2013

@JKelsey, you may have to do both the PULSE_RUNTIME_PATH workaround and the /etc/machine-id symlink workaround. If you do both, does sound start working?

@pavanky

This comment has been minimized.

Show comment
Hide comment
@pavanky

pavanky Feb 3, 2013

@slouken I was having the same issues on Arch Linux 64. I can confirm that setting PULSE_RUNTIME_PATH and symlinking /etc/machine-id to /var/lib/dbus/machine-id works.

pavanky commented Feb 3, 2013

@slouken I was having the same issues on Arch Linux 64. I can confirm that setting PULSE_RUNTIME_PATH and symlinking /etc/machine-id to /var/lib/dbus/machine-id works.

@disiu

This comment has been minimized.

Show comment
Hide comment
@disiu

disiu Feb 3, 2013

Yes, I confirm that too. On Manjaro Linux x64 (which btw is identified by the runtime script ) symlink + path works.

disiu commented Feb 3, 2013

Yes, I confirm that too. On Manjaro Linux x64 (which btw is identified by the runtime script ) symlink + path works.

@nikod

This comment has been minimized.

Show comment
Hide comment
@nikod

nikod Feb 3, 2013

@slouken That is the same as veronon said, pretty much... didn't work for me sadly, I did the symlink of machine-id too... if I run steam with STEAM_RUNTIME=0 does work.

nikod commented Feb 3, 2013

@slouken That is the same as veronon said, pretty much... didn't work for me sadly, I did the symlink of machine-id too... if I run steam with STEAM_RUNTIME=0 does work.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 3, 2013

I just realized that this bug report is a duplicate of #1179. I am going to close this.

ghost commented Feb 3, 2013

I just realized that this bug report is a duplicate of #1179. I am going to close this.

@ghost ghost closed this Feb 3, 2013

This issue was closed.

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