Sound stops working with releases 1.9 and up on Ubuntu 16.04 LTS
Opened this issue · 7 comments
When connecting with the client, the sound subsystem bombs and no sound works. I went back to 1.7b and sound works as expected.
Does it only stop working after connecting to the game? Not really sure. Only thing that i can think of is maybe your highlights are triggering too many audio cues simultaneously and causing a crash in the sound engine? There's been a few changes to highlighting in the last couple of versions. Can you try testing it with a clean settings profile?
Sure, can try. However, no sounds are set to trigger.
Ok, i doubt it then.
I actually have the same exact version of ubuntu and audio seems to be functional both before and after connecting to the game.
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
The other big changes did involve a complete audio engine update and volume slider/mute button.
What does your volume settings look like?
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
You want the volume from within FB?
Yes, just wondering if everything checks out from the settings side? Audio is not muted etc? It's possible that after new audio settings were added there could be compatibility issues with old settings. It's just a guess though. I'm not seeing anything from my side, it could as well be driver/hardware related.
Sound does not work for other programs, such as Youtube, with the latest version either. Audio works before opening Frostbite but once it is open audio for the computer stops working with an error. I will grab the error message in a bit.
I don't know what to say, i can't reproduce this on my system and i can't find any bug reports or any other info on this at all. As far as i know there's been a few users reporting other issues on linux but all non audio related. Are you sure that it crashes even when you download a clean package and run it without making any changes to settings or adding any audio files etc? It sounds like there's a system wide audio device/driver crash happening and since it's currently running on qt5 audio api, maybe you have some old remnants of qt4 libraries around that could be causing some kind of a conflict (older version of the client was running on qt4)?