[SOLVED] Steam/proton issues with some games, related to ALSA
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Steam/proton issues with some games, related to ALSA
Hi, running some games through steam, on slackware -current, many of them fail to run and provide this output;
Code:
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib64/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
INFO: OpenAudioDevice failed: ALSA: Couldn't open audio device: No such device or address
INFO: Assertion failed: 0 && "Failed to open audio device!"
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib64/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
INFO: OpenAudioDevice failed: ALSA: Couldn't open audio device: No such device or address
wine: Unhandled page fault on read access to 0000000000000000 at address 00007F5DD802B69C (thread 018c), starting debugger...
The file however does exist:
Code:
> $ ls -lah /usr/lib64/alsa-lib/libasound_module_pcm_pulse.so
-rwxr-xr-x 1 root root 35K May 31 20:15 /usr/lib64/alsa-lib/libasound_module_pcm_pulse.so
I'm not sure where to look next. So far i have tried:
* reinstalled all base packages
* deleted ~/.steam for a fresh install
* switched to pipewire
But no changes from trying all of this. Wondering is anyone else getting this issue? And anything else i could try? Thanks.
Do you have multilib installed? Are you using pulse? Also, have you tried it through proton? (linux native Steam, their implementation of WINE.)
Yes, this is only happening with some proton games as mentioned. Although it seems temperamental, as i'm now able to play one of the games https://www.protondb.com/app/1222140 , which is now running flawlessly. I think i'd only deleted the prefix in ~/.steam/steam/steamapps/compatdata/1222140
I'll mark this as solved, because it's probably not slackware related, and seems to be something up with proton/steam itself.
I use proton on Steam and I've never had this issue. Have you run
Code:
slackpkg new-config
? Did you ever use the optional replacement alsa sound server packages that replaced pulse audio for a bit on Current for those that wanted it? Is everything relevant installed in Current?
This will make steam rebuild its pins and it will also screw with steam play so you'll have to go back and enable it in settings, and then set all the games back to the version of proton you wanted to use if it isn't the one you chose in settings.
Last edited by RadicalDreamer; 11-06-2021 at 08:49 PM.
if the game works the problem is SDL2 that could be not linking to pulseaudio.
and in that case the problem could be similar to this: https://lists.opensuse.org/archives/...NG6SPGDSRLHHU/
and if its the case its related to Slackware and perhaps SDL2 would need a rebuild.
Primarily AwesomeWM, although doesn't seem desktop related, as same thing happens in xfce and kde.
It's as if 95% of the time, some games just fail to launch. But, without actually changing any settings, eventually they do run if you keep trying to launch them. And oddly, when a game fails to launch multiple times it starts thinking you've tried launching it from another machine, resulting in cloud saves being lost. Really frustrating lol.
Try launching the Game with that command in either regular or beta as the problem seems to be the same.
copy that command, go to manage, properties and paste in launch options. https://imgur.com/gkqeeak
Primarily AwesomeWM, although doesn't seem desktop related, as same thing happens in xfce and kde.
It's as if 95% of the time, some games just fail to launch. But, without actually changing any settings, eventually they do run if you keep trying to launch them. And oddly, when a game fails to launch multiple times it starts thinking you've tried launching it from another machine, resulting in cloud saves being lost. Really frustrating lol.
Did you
Code:
bash-5.1$ steam --reset
?
If that doesn't work then I have no clue. I only use Steam on one machine so I have no idea what is happening with your save files. You could remove the authorizations on other machines and see if it still does it. If that is it then you could open up an issue with Valve. https://github.com/ValveSoftware/steam-for-linux
No difference as far as i can tell, other than when the game does decide to actually launch, this only seems to stop the steam overlay from functioning.
If that doesn't work then I have no clue. I only use Steam on one machine so I have no idea what is happening with your save files. You could remove the authorizations on other machines and see if it still does it. If that is it then you could open up an issue with Valve. https://github.com/ValveSoftware/steam-for-linux
Yeah, went a step further than that and deleted the whole ~/.steam directory for a fresh profile
It seems like the pulseaudio detection code inside SDL2 fails to determine that pulseaudio is "alive and well" on the system and decides to switch to ALSA. This can be overcome by forcing the audio driver choice via the SDL_AUDIODRIVER=pulseaudio environment variable override or by making sure that the missing pulseaudio libraries (that live under /usr/lib64/pulseaudio on my system) can be found.
i have those libraries and it failed anyway until launching the game with SDL_AUDIODRIVER=pulseaudio.
i still think theres a problem with SDL2.
...I'm suspecting that the issue could be obsolete hacks made to steam rather than any problem with SDL2 (which is only minimally patched on -current).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.