You are not logged in.

#1 2015-12-07 17:06:54

boes
Member
Registered: 2012-03-17
Posts: 28

[solved]alsa update makes dota 2 soundless

after system upgrade, i notice that dota 2 has no sound at all
after tracing, i found the problem: upgrading alsa-* 1.0.29 -> 1.1.0 caused this issue.
so, any solution aside of downgrading alsa?
thanks

Last edited by boes (2015-12-08 07:43:49)

Offline

#2 2015-12-07 17:13:23

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,630

Re: [solved]alsa update makes dota 2 soundless

Rebooting

Offline

#3 2015-12-07 17:30:36

boes
Member
Registered: 2012-03-17
Posts: 28

Re: [solved]alsa update makes dota 2 soundless

no it does not work. rebooting still make it soundless

Offline

#4 2015-12-08 03:17:02

smudge
Member
Registered: 2011-03-20
Posts: 158

Re: [solved]alsa update makes dota 2 soundless

mv or rm these two files:
~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/libasound.so.2.0.0
~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/lib/x86_64-linux-gnu/libasound.so.2.0.0

You'll then have two broken symlinks named libasound.so.2 in those directories which you can delete.
Be aware that Steam will probably reinstall all these files when it updates.
Worked for me, may work for you.

Offline

#5 2015-12-08 07:43:02

boes
Member
Registered: 2012-03-17
Posts: 28

Re: [solved]alsa update makes dota 2 soundless

thanks a lot. it works!
guess steam is not integrated well in linux, redundant libraries all over

Offline

#6 2015-12-08 09:22:37

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,076

Re: [solved]alsa update makes dota 2 soundless

Because this makes game devs actually want to develop for linux, steam gives a guarantee on which libraries are available and in which version. Technically you are in unsupported valley on Arch Linux anyway and especially if you are using libs that aren't provided by steam, you shouldn't expect to be  supported by gamedevs if something breaks due to switching out the underlying lib (no ones gonna go and fix an API/ABI break just because there was an update to an unsupported lib version, in this case it's just libinternal ABI breakage which is why it should be safe to swap them out, other cases might not work out that cleanly).

Offline

Board footer

Powered by FluxBB