This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 90%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEF%3C/text%3E%3C/svg%3E)
Standby interrupts teams' access to devices (audio and video) in Ubuntu. There is no single audio/video device listed in the settings after standby (see screenshot).
Teams: 1.5.00.10453
Ubuntu: 22.04 (same as 20.04 before the upgrade)
Audio: description: Audio device
product: Starship/Matisse HD Audio Controller
vendor: Advanced Micro Devices, Inc. [AMD]
Webcam: Logitech HD Pro Webcam C920
So far the only solution for this problem is a reboot (!!!).
The following attempts to solve the problem were unsuccessful:
Restart Teams with clean settings:
sudo killall -9 teams
rm -rf ~/.config/Microsoft/Microsoft\ Teams/
Play with different audio settings (eg. profiles):
pavucontrol
Reinstall Teams:
sudo killall -9 teams
rm -rf ~/.config/Microsoft/Microsoft\ Teams/
sudo apt resintall teams
Audio and video (including webcam) work fine in ALL other applications even after a standby, only Teams has this problem.
Any ideas?
I guess I found the problem (high level) and the workaround.
I do use Chromium browser, and it looks like teams fails to "detect" my audio/video devices if the Chromium browser is running BEFORE teams was started or after my system is waking up from a standby. So if I kill/close the browser and restart teams the devices are detected as expected. Launching Chromium after teams is running works fine.
This is no real solution as I have to kill -9 (to be able to restore all tabs on restart) Chromium which I use heavily at work.
Could anybody from Microsoft please let the teams developers know about this finding? It should be easy to fix?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Thanks for your sharing. To make sure if it is a known issue, does anyone else have the same question in your organization?
Meanwhile, have you tried to login Teams web client to see if it can be reproduced?
looks like this was just correlation. Today after waking up from stand by teams again lost all audio/video devices and killing chromium and restarting teams did not solve the issue.
thank you for your answer. Most people in my organization do use other operating systems, so afaik this problem exists only with my setup.
I am able to use Teams via web client using chromium or chrome browser without any issue. The only reason I would like to use the "fat" client is the possibility to define a "second ringer". This allows me to use my monitor as a second ringer and I don't miss calls because I don't wear my headphones.
All the best,
Florian
Thanks for your feedback!
So do you mean you are using Teams web client and desktop client at the same time, right? And when you are only using Teams for Linux client, it could detect the device normally?
Have you tried to change another a/v device to see if it could be detected?
Is there any update on this case?
Please feel free to drop us a note if there is any update.
Have a nice day!
No Update. Changing my devices (eg unplugging my webcam and replugging it) does not change anything within Teams fat client.
I am working with the webclient now. It looks like many other Linux users have the same issue.