Hello I have a Problem with the Microphone in Teams on Linux: Teams is complaining, that the microphone is not working. In the device configuration I can select multiple microphones. Teams shows no level for any microphone. In the Pulse Audio Volume Control I can see level for all microphones. I also see the Recording Channel of Teams (with label "Skype" :-) ) and it receives level. Video is working fine. Thanks in advance for your help. Greetings, Anton Hattendorf

It's really annoying, please fix it asap. Where is the response from dev level to this issue? More than two months already without any progress at all.

I seem to hve gotten my BT-headset (Plantronics, voyager-focus-uc) working (on my Debian-bullseye system) for a while with: pactl load-module module-detect but some two or three months ago that stopped to be a definite, predictable solution. Now the faulty connection with Pulseaudio's stack also often coincides with not detecting my logitech webcam any more (C510) so the teams seems have trouble handling USB. Is there a flag to start teams up with some verbosity messages so that we can see what teams is looking for (and at what time/stage of it's startup)?

I'm having the same issue, the mic works fine in all other apps except Teams. Ubuntu 20.04. Teams latest version whatever that is as of the date of this comment. I can't even see an about page in the Ubuntu version of Teams.

I had the same issue on Xubuntu 18.04 with Teams 1.3.00.25560. The solution on my system was EXTREMELY simple, yet VERY hard to find (I wasted 1:30 h): Situation : ALL sound devices are connected correctly and work perfectly with other video conference software. ALL settings in the sound settings window are correct (at first glance). Nevertheless, the microphone was dead during the test call. Solution : As soon as a call is started, a new section appears in the "Recording" tab in the sound settings. Next to the drop down box (where my microphone is selected correctly!!) there is a small speaker symbol: The point is: If this symbol is dark grey, this input channel is MUTED. Click on the symbol unmutes the microphone and takes the symbol back to "normal" grey (you can hardly see the difference!!). Note that the microphone had been already unmuted in ALL the other settings – except this one! Now everything works perfectly fine. (After just 90 minutes of wasted time.) → So be aware of this hidden' muting 'feature' ;-) Unmuted (as it should be): Muted (as it was by default):

Finally "pavucontrol" and selecting the right profile there did the trick for me. I had to select "analog stereo duplex" which was not the default. Funny that skype worked anyway.

Microphone is not working

Hattendorf, Anton 51

Hello

I have a Problem with the Microphone in Teams on Linux:

Teams is complaining, that the microphone is not working.
In the device configuration I can select multiple microphones.
Teams shows no level for any microphone.
In the Pulse Audio Volume Control I can see level for all microphones.
I also see the Recording Channel of Teams (with label "Skype" :-) ) and it receives level.

Video is working fine.

Thanks in advance for your help.

Greetings,
Anton Hattendorf

Ricardo Havranek Garcia 86 Reputation points Microsoft Employee

2019-12-11T16:36:55.963+00:00

Hello Anton. What version are you using? Can you click your photo / About / Version and share?
صفاء انور عبد الرؤوف عبد الرحيم 1 Reputation point

2022-07-24T22:36:34.02+00:00

May be soft wear or or intro of mic
صفاء انور عبد الرؤوف عبد الرحيم 1 Reputation point

2022-07-24T22:39:39.893+00:00

May be program of set up

23 answers

Anonymous

2021-02-02T10:43:46.283+00:00

It's really annoying, please fix it asap. Where is the response from dev level to this issue? More than two months already without any progress at all.
Please sign in to rate this answer.
Foo Tek 0 Reputation points

2023-02-24T18:18:15.2166667+00:00

I am running Ubuntu 22.10 currently but have only upgraded from Ubuntu 22.04 LTS within the past 3 months.

Teams has never worked on this system for me. I had a job interview with a major financial institution ( I got it yayyyy) last week and I downloaded and started up teams the night before so we could do the interview over teams.

Nothing worked except joining the meeting. No video (my webcam is working just fine for all other apps I use it for) and voice was one way only - they can hear me but I cannot hear them. I tried the Arctis 7 Pro gaming headset I use daily in Linux and also my Jabra headset (which also works in all my other applications)that I use for Windows 10 at work. Both headsets were working fine in all my other Linux apps but not Teams. I am not a beginner Linux guy (call me a home power user) and I have been supporting Windows since Windows 95a (expert at Windows support) - the job interview was to run a break/fix center on a campus of 1200 users where I would be their first point of contact for hardware and software related issues (1st/2nd level software issues).

I did a quick reboot into my emergency Windows install and did the interview from there. I DID have the option to phone in using my cell phone but wanted to do the teams thing in order to allow the employer to see me.

I do not believe MS has any interest whatsoever in getting teams to work flawlessly ( or close to it) on Linux. If so, this would already be done. Web based Team,s seems to work a bit better in linux but the app is crap in my experience.

The even worse news is that WebEx has much the same attitude about Linux and nothing except MAYBE web based WebEx will work on Linux.

AS an aside, for anyone who is interested. I completely swapped out all my PC needs to Linux using Kubuntu. I have 5 legal copies of MS Windows 10 home (1 copy) and professional (4 copies) and I do not want to use any of them daily specifically because of MS's strategy to take away administrators abilities (albeit slowly) to troubleshoot the OS by hiding or outright elimination some administrative technical tools and abilities and finally and MOST importantly their raping of all my telemetry/data.

The telemetry thing was the straw that broke the camels back for me. I do not trust MS anymore than I trust google or face-book with my personal data and I believe them not one bit when they say "no personal data" is collected.

With the advent of Steam OS I can run literally all my games (windows native or not) under Linux. I have found open source Linux alternatives to every single piece of software I use (except teams - so far) and pay for yearly except the VPN client. I pay for VPN access yearly like I did on windows - same VPN company.

All the game sI run (Far Cry 3-6, Hogwarts Legacy, CyberPunk2077, Red Dead Redemption 2, God Of War, Assassins Creed Odyssey, Forza Horizon 4, GuildWars2, Elden Ring, DOOM Eternal, BioShock Infinite, Borderlands 3, The ElderScrolls Oblivion, FallOut4 and 76, GTA5, Horizon Zero Dawn, the Witcher and Wallenstein and Ghost Recons and Sniper series I mean they all just work now. In the Steam Linux client I enabled the proton driver for all non-Linux native games and when I install them from steam all the proper convert from Windows to Linux files are just installed configured. One may have to add a game launch switch or three within the game steam properties but the are literally shown within the protondb webpage. Go there, look up a game you are interested in and see if it can play on Linux. Chance are it will play very well on Linux and in some cases with better fps than on Windows.

All the games that have the capability to use NVIDIA DLSS and Ray Tracing are using hem just fine in Linux, no better or worse than in Windows.

If one is a technical person there is literally zero reason to NOT change to Linux except personal preference.

If one is NOT a technical person there is STILL little reason not to change to Linux as the learning ncurve is FAR less steeper than it was even 5 years ago and things are MUCH better as far as gaming on Linux goes than they were even 2-3 years ago.
Sign in to comment
Hans 1 Reputation point

2021-02-01T09:01:49.19+00:00

I seem to hve gotten my BT-headset (Plantronics, voyager-focus-uc) working (on my Debian-bullseye system) for a while with:
pactl load-module module-detect
but some two or three months ago that stopped to be a definite, predictable solution.
Now the faulty connection with Pulseaudio's stack also often coincides with not detecting my logitech webcam any more (C510) so the teams seems have trouble handling USB.

Is there a flag to start teams up with some verbosity messages so that we can see what teams is looking for (and at what time/stage of it's startup)?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Nathan McKaskle 1 Reputation point

2021-01-25T14:43:58.863+00:00

I'm having the same issue, the mic works fine in all other apps except Teams. Ubuntu 20.04. Teams latest version whatever that is as of the date of this comment. I can't even see an about page in the Ubuntu version of Teams.
Please sign in to rate this answer.
Carl Shubitowski 1 Reputation point

2021-02-01T15:31:10.207+00:00

Same issue here. Last week I had an interview for a job on Teams. I assumed it would work because I interviewed on Google Meet and it worked fine. Much to my surprise, I could hear them but they could not hear me. My microphone was grayed out and I could not select it. This was on Ubuntu 20.04 and use the we. I could not get the downloaded app to connect to the meeting. It was kind of embarrassing and I ended up calling in and they were still there, so I had the interview. I have another one today on Teams and have been working all morning trying to figure this one out with no luck.
Sign in to comment
Markus 1 Reputation point

2020-11-20T09:37:14.3+00:00

I had the same issue on Xubuntu 18.04 with Teams 1.3.00.25560. The solution on my system was EXTREMELY simple, yet VERY hard to find (I wasted 1:30 h):
Situation: ALL sound devices are connected correctly and work perfectly with other video conference software. ALL settings in the sound settings window are correct (at first glance). Nevertheless, the microphone was dead during the test call.
Solution: As soon as a call is started, a new section appears in the "Recording" tab in the sound settings. Next to the drop down box (where my microphone is selected correctly!!) there is a small speaker symbol: The point is: If this symbol is dark grey, this input channel is MUTED. Click on the symbol unmutes the microphone and takes the symbol back to "normal" grey (you can hardly see the difference!!). Note that the microphone had been already unmuted in ALL the other settings – except this one!
Now everything works perfectly fine. (After just 90 minutes of wasted time.) → So be aware of this hidden' muting 'feature' ;-)

Unmuted (as it should be):

Muted (as it was by default):
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Jens Hektor 6 Reputation points

2020-11-10T10:16:55.387+00:00

Finally "pavucontrol" and selecting the right profile there did the trick for me. I had to select "analog stereo duplex" which was not the default. Funny that skype worked anyway.
Please sign in to rate this answer.

1 person found this answer helpful.
John Veitch 1 Reputation point

2021-07-14T12:36:59.703+00:00

Thank you @Jens Hektor ! I had the same issue but switching the device mode in pavucontrol to one of the "Duplex" options (instead of Mono Input + Mono Output) solved it for me!
Sign in to comment