Microphone for teams on Linux not working

mjskier 46

On an HP Zbook studio G5 running Mint 19.1
Plantronics C3320 headset plugged into a USB port (on the laptop, not on the G3 docking station)

The teams_1.2.00.32451_amd64.deb package installs fine, and the test call works as expected.
However when calling a coworker, all he hears is very bad static that gets louder when I speak.
Same problem when input is set to the builtin microphone.

In sound preference:
Device set to Plantronic Blackwire 3220 Series Digital Stereo Duplex (IEC958)
Input connector set to "Digital Input (S/PDIF)

In the Teams Settings->Devices, speaker and microphone are set to Plantronic Blackwire 3220 Series Digital Stereo Duplex (IEC958)

Christian Laurent 6 Reputation points

2020-04-29T10:57:09.387+00:00

running

sudo pulseaudio -D
sudo teams

works for me on ubuntu 20.04
Emre 1 Reputation point

2020-05-19T13:54:44.027+00:00

Hi all, any permanent solution to the microphone this?
Using root does not still work for me, Teams can't use the microphone.
Theis 1 Reputation point

2020-10-21T09:13:57.527+00:00

sudo teams worked for me.
Wiktor Nowicki 1 Reputation point

2020-10-28T08:59:45.83+00:00

surprisingly, microphone input still doesn't work on Fedora 33, in the version 1.50, however it works literally everywhere else.
Franck 11 Reputation points

2020-11-19T12:54:37.187+00:00

Don't EVER run any external applications program with root privileges (sudo) - this is opening a major vulnerability on your system
Franck 11 Reputation points

2020-11-19T13:08:26.88+00:00

teams detects no audio/video devices on my kubuntu 20.10 desktop
notification sound is heard
no devices are selectable in parameters

version de Microsoft Teams est 1.3.00.25560 (64 bits) .
Guillaume R 1 Reputation point

2020-12-15T08:33:57.977+00:00

I got the same problem on my Arch Linux box. The mic was on and working with Jitsi and so on for example.

To make it work with Teams I simply add my user to the group audio this way: gpasswd -a myUser audio
MountainLogic 1 Reputation point

2021-07-08T15:22:35.313+00:00

I found that if I go into the system tray and crank-up the mic volume that I am able to get a very noisy voice from the external headset input with a standard apple white headset. It is distorted and seems to have a "helicopter" sound in the background. I have experienced similar helicopter sounds on a (different) windows box with teams several years ago. A cheap set of ear buds seem to work fine with the mic cranked-up. pavucontrol was helpful.
Mohammed Yasar Shaikh 1 Reputation point

2021-09-09T10:29:08.013+00:00

Thursday, 9 Sep, 2021.

This problem solved me when I opened sound from start menu(actually linux mint menu) open sound then application, I seen that there is a sound volume level baar at zero value for Skype app, I increased that and sone, try it, say if it was the problem, I am using Linux Mint 20.2 Cinnamon 5.0.5,

thank you
Allan Brown 1 Reputation point

2021-11-19T19:49:24.43+00:00

I'm experiencing the same issues.

I'm currently running Ubuntu 20.04 (added to all the relevant groups) and the mic doesn't work.

However - when I spin up a Windows 10 image on Virtualbox on the same hardware, Teams works perfectly.
Scott Crossen 1 Reputation point

2022-05-26T17:21:40.717+00:00

For me, the "No Device" / "Custom Setup" issue was fixed by increasing the number of inotify workers in /proc/sys/fs/inotify/max_user_watches as teams apparantly requires these to list devices

34 answers

Jens Hektor 1 Reputation point

2020-03-24T14:34:29.893+00:00

Same on a Lonovo Thinkpad T560 running Fedora Core 31
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Hervé Sylvain 16 Reputation points

2020-03-25T12:39:30.473+00:00

Works well with root user on fedora 31. Not with normal user. Pavucontrol shows chromium a while at startup, not after.
Please sign in to rate this answer.
Hervé Sylvain 16 Reputation points

2020-03-25T12:55:01.45+00:00

Found the answer for fedora 31 : you have to had your user to video and pulse groups.

RuebeSoft 6 Reputation points

2020-04-29T06:09:58.697+00:00

My headset-mic works only as normal user with F31, if I connect the headset and set it as default in the Audio Settings of Gnome BEFORE starting Teams . Only then I can use the mic in Teams. Hope that helps someone.

DAVID ROJAS 1 Reputation point

2020-06-11T02:52:19.283+00:00

Excelente amigo, funcionó ejecutando la aplicación como root desde la consola. Usé en Linux Mint el comando #sudo teams y se ejecutó con Microfono y camara que antes no funcionaba.

Reinier Post 11 Reputation points

2020-11-05T13:09:37.07+00:00

Ubuntu 18.04 here - adding the user to the audio and video groups fixed the issue. (I'm not sure what video group membership is needed for.)

Ales Zacharie 1 Reputation point

2020-11-24T15:33:57.417+00:00

That was the problem for me.

An additional step was required to make it work since teams does not completely close when I close the teams window.

I had to go in "Settings > General" and untick the option "On close, keep the application running". It then worked when I restarted teams.
Sign in to comment
Jens Hektor 1 Reputation point

2020-03-26T14:44:46.003+00:00

Grr.

HervSylvain is right. Running Teams as root lets team find the mic. Tststs.
Please sign in to rate this answer.
Jonathan Neufeld 6 Reputation points

2021-05-04T17:20:19.387+00:00

Try adding yourself to the "audio", "video", "pulse" and "pulse-access" Linux groups. I don't have to run Teams as root and I get all the devices enumerated.
Sign in to comment
Hervé Sylvain 16 Reputation points

2020-03-26T15:59:35.487+00:00

You have to had your user to video and pulse groups. add video pulse fedora
Please sign in to rate this answer.
Anonymous

2020-07-10T14:21:40.367+00:00

Adding my user to the video and pulse groups does not solve the issue for me. Seems like this may be a deeper bug that Microsoft is in no hurry to fix.

Jonathan Neufeld 6 Reputation points

2021-05-04T17:23:32.48+00:00

Try adding to "pulse-access" group as well. You also need to open a new sub-shell for the permissions to take effect (or logout / login again), there's a more elegant way to do that as well but I do not recall right now.
Sign in to comment
Dane Seelen 81 Reputation points

2020-03-26T19:49:28.253+00:00

This sounds like a permission issue on Linux, I would test with root vs standard user to see if the issue is resolved. If so you could then narrow down the difference on the permissions level to correct it.
Please sign in to rate this answer.
Hervé Sylvain 16 Reputation points

2020-03-27T08:25:39.103+00:00

Again, you just have to add your user to pulse and video groups. Maybe it's possible to ad this to the RPM?

Rusty Weise 6 Reputation points

2020-04-23T06:40:13.273+00:00

Bang on @Hervé Sylvain , thanks! I would have not guessed that one ;-) +1 adding the rule to the package

Reinier Post 11 Reputation points

2020-11-05T12:08:31.307+00:00

It is no solution to add the user to those groups automatically:

The installer runs as root, it doesn't know which user(s) to add. Linux is a multiuser OS!

More users may be added to the system later. What about them?

This gives the users other rights that have nothing to do with Teams. Installing a package must not grant a user's general permissions that affect permissions to use other software than just the software being installed.

A better solution would be to somehow make it work without the user being in these groups; Chrome can do it, too.

Jonathan Neufeld 6 Reputation points

2021-05-04T17:26:38.337+00:00

Zoom Video Conferencing, Discord, OBS Studio, Element all have no issues with audio / video recording / playback on Linux.
This issue is very Microsoft-specific.
Sign in to comment