Is there a fix coming for how Teams handles audio in Linux?

Andrew 56 Reputation points
2020-12-08T19:17:47.053+00:00

Every 3rd or 4th time that I use Teams, my audio settings end up totally screwed up. The most annoying one is that the list of available output devices drops the listing for the aux output, and sound is piped out the aux jack and the internal speakers at the same time. I can follow the steps in the following troubleshooting article to reset everything and get the options back to configure things how I would like them, however I have to use the steps in #1B which requires a full reboot. That is insanely annoying when you have multiple tmux sessions and countless tabs open. Aside from this problem I usually go a month or more without needing to restart my machine.

https://help.ubuntu.com/community/SoundTroubleshootingProcedure

I reset everything and rebooted last night. After a single Teams meeting today, the ability to change my microphone amplifier setting is already lost. At least it isn't outputting on both devices yet and the current mic setting is OK.

I am currently stuck at 16.04 for a little while longer due to dependencies surrounding software that I use at work.

I am on a Dell Precision 7510 with the following chipset if the hardware is related. I am not currently using any external USB attached microphones or webcams:
Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)

Insanely annoying.

Microsoft 365 and Office | Skype for Business | Linux
Microsoft 365 and Office | Skype for Business | Linux

A Microsoft communications service that provides communications capabilities across presence, instant messaging, audio/video calling, and an online meeting experience that includes audio, video, and web conferencing.

13 answers

Sort by: Newest
Most helpful Newest Oldest
  1. BYERS, SIMON D 0 Reputation points
    2026-03-16T16:28:34.15+00:00

    2026-03-16 Ubuntu 24.04.4 LTS, Google chrome browser, random HP desktop machine.

    I am using pulseaudio and have system audio, wired headset and DECT wireless headset.

    I have this problem on and off, when I make a teams call it will randomly switch over to another audio device creating confusion.

    Was this answer helpful?

    0 comments
  2. ExistingDude 1 Reputation point
    2022-01-22T04:26:19.097+00:00

    For Arch Linux users using pavucontrol, changing the profile to High Fidelity Playback from the configuration tab fixed it. Worked for me in EndeavorOS i3.

    Was this answer helpful?

  3. TURGUT KALFAOGLU 1 Reputation point
    2021-10-11T13:02:08.023+00:00

    Same problem here -- fedora 34 - all updates applied, X11, KDE..
    It hangs for a minute or so, then resumes as if nothing had happened..
    Disabling hardware acceleration does not help.
    Interestingly sometimes it survives for 2 hours of video group chats, then dies after it finishes.
    I edited its /usr/bin/teams so it shows the errors etc on the console, and here is what it wrote:

    [turgut@tk-minilaptop bin]$ teams
    Error while parsing hooks JSON. Error: "ENOENT: no such file or directory, open '/home/turgut/.config/Microsoft/Microsoft Teams/hooks.json'"
    (node:137752) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
    (node:137752) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ecsSettingsUpdated listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
    (node:137752) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 appInitialized listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
    (node:137752) UnhandledPromiseRejectionWarning: Error: LocalStorageService: key or value not defined
    at m.<anonymous> (/usr/share/teams/resources/app.asar/main.bundle.js:1:401202)
    at Generator.next (<anonymous>)
    at /usr/share/teams/resources/app.asar/main.bundle.js:1:399460
    at new Promise (<anonymous>)
    at i (/usr/share/teams/resources/app.asar/main.bundle.js:1:399205)
    at m.setValue (/usr/share/teams/resources/app.asar/main.bundle.js:1:401144)
    at t.AppLevel.set (/usr/share/teams/resources/app.asar/main.bundle.js:16:681777)
    at /usr/share/teams/resources/app.asar/main.bundle.js:16:689507
    at Array.forEach (<anonymous>)
    at t.appPreferenceKeys.reduce.n (/usr/share/teams/resources/app.asar/main.bundle.js:16:689454)
    (node:137752) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
    (node:137752) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    (node:137752) UnhandledPromiseRejectionWarning: Error: LocalStorageService: key or value not defined
    at m.<anonymous> (/usr/share/teams/resources/app.asar/main.bundle.js:1:401202)
    at Generator.next (<anonymous>)
    at /usr/share/teams/resources/app.asar/main.bundle.js:1:399460
    at new Promise (<anonymous>)
    at i (/usr/share/teams/resources/app.asar/main.bundle.js:1:399205)
    at m.setValue (/usr/share/teams/resources/app.asar/main.bundle.js:1:401144)
    at t.AppLevel.set (/usr/share/teams/resources/app.asar/main.bundle.js:16:681777)
    at /usr/share/teams/resources/app.asar/main.bundle.js:16:689507
    at Array.forEach (<anonymous>)
    at t.appPreferenceKeys.reduce.n (/usr/share/teams/resources/app.asar/main.bundle.js:16:689454)
    (node:137752) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

    Was this answer helpful?

    0 comments
  4. Spurný Jan 1 Reputation point
    2021-09-13T16:30:26.423+00:00

    This happened to me (debian10, dell laptop) because I use laptop and basicaly NEVER shutdown unless I have to - I always suspend/hibernate if I can - but I do upgrade my system, which means, after some time, my running kernel is out of sync with what is actually installed - I was trying everything to avoid reboot, but the reboot was what I really needed (I had uptime of 150 days) - after reboot, everything was working perfectly.

    So I don't exactly recommend rebooting, but if you suspend/hibernate a lot and your system may be out of sync with what is installed/upgraded, reboot actually IS a good solution..

    Was this answer helpful?

    0 comments
  5. Stephen Phillips 1 Reputation point
    2021-08-19T16:23:55.777+00:00

    I'm having the same problem and have had it for a while.

    Version:

    You have Microsoft Teams Version 1.4.00.13653 (64-bit).

    OS

    $ uname -a
    Linux ---- 5.11.0-31-generic #33-Ubuntu SMP Wed Aug 11 13:19:04 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
    $ lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 21.04
    Release: 21.04
    Codename: hirsute

    One user mentioned restarting Teams. You can easily do that using the icon by the clock. Closing the Teams window may leave it running in the background, but if choose "Quit" from the menu by the clock, it will fully close it. I've had lots of screen artifacts and crashing issues after suspend even without the sound issues, so it's gotten to be a normal thing for me.

    I also noticed Teams doesn't like changing the sound inputs. When I plug my laptop into my dock, it sees the new input right away for some reason. But, when I connected my bluetooth headset it wouldn't see it. I could set my system to use the headset and tell Teams to use the default system device. It would ring in my headset and then switch to the main speakers for the call. Crazy! When I closed and reopened Teams while the headset was already connected, the headset was in the device list in Teams settings, and it worked great.

    I have also found that doing a test call seems to fix the sound somehow. It's annoying ,but I've gotten in the habit of doing a test call to check the sound before every call. I think that fixes things as much as it checks them.

    I'm thinking about trying to configure a loopback sound device to see if I can pipe things to that device and just have teams restricted to that device. I'll comment back if I can get that working.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.