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(256, 45%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
I would like here to get some attention to a bug that exists for a while and has yet not been fixed. This bug occurs with the latest Teams ver. 1.3.00.25560 64bit on several versions of Linux, including Ubuntu 20.04, 18.04 and Mint.
During a call click Settings > Device Settings. The device settings tab will open on the right side. Keep the tab open while somebody in the call is talking. Although you may not speak at all, working with headphones and being in a very quite space, the volume indicator of your microphone will appear full for a few seconds, and then there will be a message that your microphone will be disabled because it is not working properly.
After that, the microphone remains disabled forever and the only possibility to turn it back on, is to get out of the call, restart teams and log back in.
It would be great if Microsoft could fix this bug, because flawless communication with voice calls is critical for our work.
Do other people in the same environment have the same issue?
Thanks for your sharing. I am testing this issue in my lab. If there is any update, I will share with you.
Your time, understanding and cooperation will be highly appreciated.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@lefterav ,
Sorry for late response. This issue is still in investigating. Any update I will share with you.
Thanks for your understanding.
@lefterav ,
Now, I could only test in Ubuntu 16.04. The result is well.
I will build the same Linux version as yours to verify if this issue is a bug.
@lefterav ,
I have reported this issue to Microsoft development team. Any update I will share with you.
@lefterav
Sure, this is a bug.
I was told that it will be fixed in the next release.
@lefterav
Now, the new update for Teams Linux is released. The version is 1.3.00.30857.
You could try to update to this version and check if this issue is fixed.
![](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(176, 47%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERP%3C/text%3E%3C/svg%3E)
@Sharon Zhao-MSFT
I'm using the Insiders 1.3.00.30857 and I have the same issue
Hi, I just managed to test it in release 1.3.00.30857 and the problem still occurs. I was forcefully muted in the video call and nobody could hear me. I had to restart and rejoin the call so that I can speak. So the issue is still not fixed.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Currently, unfortunately, I can't imagine that they'll get the problems fixed in the near future. We've been waiting for over a year for the client to drop its preview status and become a full-featured client. Unfortunately, this has not changed until today. Accordingly, this is also developed with the lowest prio.
Check the nice UserVoice voting they've been aksing for. Over 3,900 votes and still no comment from Microsoft. They've told us we will see some progress once the SNAP packages have been released, but that was already a month ago. I have lost faith in this company by now.
Any idea when we can expect a bugfix release?
@Anonymous
It has no exact time to fix this issue now.
If there is any update, I will share here.
Thanks for your patience and understanding.