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(185.6, 33%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPR%3C/text%3E%3C/svg%3E)
What is your reliable Microsoft Teams Linux App setup with multiple mics and frequent screen sharing?
Mine is not working. Here's my configuration:
Latest Version of Microsoft Teams using Xorg as the backend
Ubuntu 20.04 with latest updates
Gnome with Dash-To-Panel plugin ( https://extensions.gnome.org/extension/1160/dash-to-panel/ )
Recent Logitech USB Headset with Mic (2 years old)
Recent Logitech USB Webcam with Mic (2 years old, HD)
10th Generation Intel Processor with Intel Video Output
Most of the time if I have a long meeting and switch audio outputs or inputs any mic input completely breaks. No one can hear me anymore no matter what input I select. The mic volume is all the way up. I've tried adjusting with Pulse Audio's pavucontrol as well with no luck.
Just recently I had a meeting and was sharing one of my screens when I could no longer switch between applications using the key combo Alt+Tab or the panel at the bottom of the screen.
I use both Zoom and Teams several times a week (for hours) and it does not do this in Zoom or any other app. Restarting Teams fixes the audio problems but doing that in the middle of a meeting is obviously not a good idea. The last time I shared my screen the window manager was left in a completely broken state and I had to reboot my PC. I wonder if this is because of the Dash-To-Panel Gnome extension but even Alt+Tab would not work.
According to this post on reddit: https://www.reddit.com/r/Fedora/comments/mbk435/f33_pipewireteams_desktop_sharing/
"Screensharing works well in the web app with chromium though, if you enable the pipewire feature flag chrome://flags/#enable-webrtc-pipewire-capturer"
I will have to try that later.
![](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(284.8, 17%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYS%3C/text%3E%3C/svg%3E)
Hi @Paul Richards ,
I tried searching around and also noticed in some other threads that it might work better in Teams web client. So agree with you that it's worth having a go and see if there would be any improvement when using Teams via the web browser.
Hi @Paul Richards ,
Just checking in to see how things are going on with this issue. Does it work better in Teams web app?
![](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(211.20000000000002, 20%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP2%3C/text%3E%3C/svg%3E)
Unfortunately with Chromium it is worse. After trying it for the first day people where sending me messages and it wasn't showing them in the browser. I had to sign off and sign back in. There was no error or anything in the Window.