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 does not support alsa 1.1.0, no audio #4139
Comments
Same problem here. |
Deleting/renaming alsa-lib folde and libasound.so.* in the steam-runtime folder should fix the problem. ~/.steam/steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/ |
You can also just launch steam like this: EDIT (2015.11.23, added 64-bit version of lib):
And not need to delete files that will come back each time steam updates. 🎉 |
You could also create a wrapper for steam using that EDIT (2015.11.23, added 64-bit version of lib): #!/bin/sh
LD_PRELOAD="/usr/lib/libasound.so.2:/usr/lib64/libasound.so.2" /usr/bin/steam Call it |
Same problem here, I've downgraded to 1.0.29 because it was causing crashes. Additionally, Transistor game stopped working when you launched it on Steam due to this problem. Edit: I've got PulseAudio installed too. |
@ChuckDaniels87 have you tried launching steam like this (from the command line)?
|
@ryanpcmcquen It works launching steam that way (both Steam audio and Transistor game). |
@ChuckDaniels87 to make it permanent, create a file named Put this in it: #!/bin/sh
LD_PRELOAD="/usr/lib/libasound.so.2:/usr/lib64/libasound.so.2" /usr/bin/steam UPDATE (2015.12.02): #!/bin/sh
LD_PRELOAD='/usr/$LIB/libasound.so.2' /usr/bin/steam P.S. The single quotes are important! |
Thanks for the tip but this bug should be fixed sooner or later. I don't like to make this kind of fixes permanent because I always forgot that I did it in a couple of days (making it really permanent 😜). Thank you for the fix anyways! 👍 |
@ryanpcmcquen When I try launching Steam with |
@Zekario, did you actually see if sound was working? Here is the thing. Steam is 32-bit, some games (like XCOM: Enemy Unknown), are 64-bit, therefore you need both libraries. That 'error' is innocuous, sound will work. Don't just assume it won't because of that output. |
@ikokostya the problem with that fix, is that any Steam update is going to bring those files back. The |
I assumed it didn't work because nothing happened after I tried it in the terminal. It went back to the prompt and didn't open Steam. |
Try launching it like this:
|
Just in case someone will get the same issue: the "delete Launching steam as @ryanpcmcquen said ( Alsa 1.1.0, Arch Linux rolling x86_64. |
@ryanpcmcquen That seems to have worked after a restart, I think I already had Steam running. Thanks! |
Is there any way to get sound while streaming to Arch working without downgrading alsa-lib? Doesn't seem like this bug will get fixed anytime soon. Setting LD_PRELOAD only works for local games. Okay, this is strange: |
The fix seems to have stopped working, at least on my laptop. Sound doesn't work, despite launching it via the above methods. There was a pretty big Arch update recently, and Steam updated as well. |
@ryanpcmcquen now steam doesn't want to launch at all :/ EDIT: It launches after a restart, still no sound. |
@Zekario I still have sound after the Steam update, but I am on Slackware. Do you have pulseaudio installed? On a side note, #!/bin/sh
export LD_PRELOAD='/usr/$LIB/libasound.so.2'
/usr/bin/steam |
@ryanpcmcquen I don't have pulseaudio installed. Is it better with Steam? If I switch to it I'll have to change a few key bindings, but probably not too much. |
No, I wouldn't recommend pulseaudio. I don't have it installed.
What errors is Steam giving when you launch from the terminal?
|
@ryanpcmcquen I changed my steam to export libasound.so.2 like you did a few comments above, then ran steam in a terminal. It gave this, then stopped (went back to command line input):
|
I tried installing pulseaudio, rebooted and found my headphones not working properly anymore. So I think the best "solution" might be to downgrade lib-alsa since Alsa 1.1.0 seems buggy. / btw: Can someone confirm the headphones bug? Can't seem to find a working bugtracker for Alsa |
@Zekario I use ArchLinux and still got sound after both Steam and CS:GO updated recently. But I've not updated system for a while. I'm launching steam as @ryanpcmcquen said (LD_PRELOAD='/usr/$LIB/libasound.so.2' /usr/bin/steam &). |
When this problem happens (with an unmodified runtime), are any alsa libraries accidentally loaded from the host system? The output of "info shared" in GDB after a crash occurs, or the output of /proc/$pid/smaps during execution of a game that doesn't have sound are both useful data to help us understand this problem. |
We just traced my friend's Borderlands 2 and Borderlands: The PreSequel not starting, and the workaround with this: LD_PRELOAD='/usr/$LIB/libasound.so.2' ${LD_PRELOAD} steam got it working again. He's using Pulseaudio on a fully up to date Arch Linux. |
Is it fixed with this update? |
I just tested 3 games (with pulseaudio): So... it got a little better. |
Transistor starts now but still no sound. |
The source of the problem is a Steam Runtime leak into the system configuration related to the ALSA sound system. I've found in one of the affected 32-bit games (Broken Age) that it was reading system's
(A few system calls later was when the process crashed with a SIGABRT or SIGSEGV) The problem in this case is that the version of the linker loaded
You can try patch that file and see if it fixes the problem for you, instead of the LD_PRELOAD workaround (that preloads the 1.1.0 version of |
Not crashing now but there is still no sound in some games. I think this issue should stay open. |
I agree. The patch did nog solve the problem. The crash is gone but so is my audio. |
+1 for re-opening this issue: I'm still affected by it when running latest Steam on 64bit Ubuntu 16.04.1 |
I suspect that might be a different issue, especially if it's only affecting /some/ games. I'm not familiar with Ubuntu and the likes though (Gentoo Linux here), nor am I familiar with PulseAudio, so I could be completely wrong. In short though: which games? Longer version: Applications that use FMOD tend to behave in unexpected ways with set-ups that have more than one audio device available for use. They don't seem to care about a user's configuration, and rather pick whatever seems 'default' to them instead. It may be that the FMOD developers intended that the ones implementing FMOD in their applications would do what's necessary to make it play nice with ALSA. While I've had this issue for years with Outlast and the one streaming video that I bought before I realised it's a stream (grrr), I bumped to it with several more recently. A complete list of which I have experienced issues like this with:
Day of the Tentacle Remastered is what made me finally actually look into this issue. While doing some testing for Cheeseness (the AWESOME! person doing the porting of Day of the Tentacle Remastered to Linux), I noticed that all of the applications were actually making sounds, it was just that they were ignoring my configuration, and used an incorrect device! I've been doing some testing with the FMOD recording example program, and while it seems it might be possible to make FMOD use a user-specified device via the least(?) work (adding a command-line switch for the application), it has issues with parsing some of the '.asoundrc' sections (for example, at least some years ago, it would not parse 'hint' at all). Most notably perhaps it sees '!default' as a device name, which it of course fails to find. This is probably something that should be fixed in FMOD itself, as it seems completely wrong to ignore a user's configuration. The most annoying part might be that even 'dmix' in a common ',asoundrc' seems to be ignored as well, so the applications will not be sharing the device at all. I do have some hope left in me, however, that with a particular syntax it could be possible to make FMOD do what a user wants, because 'dmix' for example does seem to work when ALSA defaults is used (empty or no ',asoundrc' at all, or something like 'defaults.pcm.card 0' defined in it). One simple way to confirm which device is being used, and by what: 'fuser -v /dev/snd/*' Like I said, though, I could be completely wrong, but I felt it was worth mentioning this here. :] |
@Chiitoo Fair enough; I will say that the symptoms I'm experiencing are remarkably similar, and the LD_PRELOAD work-arounds resolve it (see this forum post for the the exact command line I'm using). The game in question is Planetary Annihilation: Titans. |
Ah. If LD_PRELOAD helps, it does seem more likely to be a library issue still. Was hoping my guess would strike true, as I've not needed any such workarounds for a while now. I'm on 'alsa-lib-1.1.1' now, but I'm fairly sure things worked with 1.1.0 as well. Should probably test that to make sure... Thanks! |
I came here from Uberent forum too. Hopefully this will get fixed eventually. |
Factorio is currently not launching on my system with or without LD_PRELOADs |
alsa-lib 1.1.5 wine 3.0 is working fine for sound. This seems like a distro issue? Pretty sure this bug can be closed report can be closed. @jkarnesPerfectCube open a new bug for that. Check appdb |
Hello, a while back Steam's handling of the steam runtime changed to prefer system libraries over the steam runtime if they are newer, which should have resolved this scenario for most users. The more recent Factorio comment appears to be unrelated to the opening post. |
No description provided.
The text was updated successfully, but these errors were encountered: