-
Notifications
You must be signed in to change notification settings - Fork 48
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
No sound after upgrade to 5.1 #27
Comments
I did a little bit of digging and found out that playing sounds via Pulse inside the container actually works. So it looked like something changed in Zoom itself. But then I rolled back to 3.5 image and was surprised to see the same problem there. Any ideas what it could be? |
I've tried the latest build on Docker Hub You may find something by displaying Zoom's stdout/stderr by using the following command: docker logs zoomus There's also a logs file in |
In the log I find a line saying PA ist running and can be accessed by pacmd outside the container. |
I still have no solution for this problem but a new observation to share: When opening a shell in the container I can access PulseAudio as root by giving the
whereas trying the same as the zoom user it fails:
|
In an strace I found this lines:
|
I'll run zoom als root inside the container as a workaround for now but I#m not happy with it ... I played around with settings, permissions, running Only running zoom als root makes it work as expeced |
Looks like the newest version crashes entirely due to the same issue:
@mlo-poc could you share what you did exactly to make it work? What do you mean by "running zoom als root"? |
The 3.5 version worked just fine until recently, when joining conferences required upgrade. So I did that and now there's no audio / mic.
On the audio settings page the "Test speaker" button as well as other controls are disabled. Setting "Speaker" to either "Same as system" or "Built-in…" doesn't change anything. Microphone dropdown is disabled and empty.
How can I help to diagnose this?
The text was updated successfully, but these errors were encountered: