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

Question

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.

Answer 1

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)

Answer 2

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.