MS Teams won't start ... again!

Last September we discussed in this forum a problem with MS Teams refusing to start. See this thread: Microsoft Teams stalls on start. Goes on after deleting cache and user files.

Well, earlier today I had the same problem and of course tried to solve it using the same solution we discussed in the above thread, namely deleting the cache and other related files. The trouble is that it will not work now. I uninstalled and installed again Teams again without success. I see that “is down” reports people having trouble with MS Teams today, but I tested the web interface and I could log in and book a meeting without trouble. The version of MS Teams I am talking about is the same cited last September (1.4.00.26453-1).

MS Teams worked fine yesterday.Today I run “zypper dup” and a few libraries were changed (sorry, cannot find how to list which of them). I suspect some incompatibility might have been introduced there.

Is anyone else experiencing the same troubles?

After a lot of search, trying older versions, etc I could not find any solution. I have for now resorted to using the web app. An hypothesis could be that the problem may be related to recent changes in sound/video management (pipewire, gstreamer) but I do not really know. I will keep eyes open on this.

Have you tried the unnoficial flatpak?

Not until right now. It works, and it works fine. Thanks for the pointer.

Running with the following option works for me:

teams-insiders  --no-sandbox

glibc 2.35 was updated around OP posted, it could have caused this issue. Last time glibc broke electron apps and the workaround was disabling sandbox. A fix is likely needed in electron if not fixed yet. Then Teams needs to upgrade electron and release a new version.

Thanks both. Good to know. For now I can work normally with flatpak. So I will continue so for now.

Thanks. --no-sandbox works on my Tumbleweed. Mine broke the same timing as the OP. Several updates so not sure how to track which exact one, but this work around works for now.

Workaround does the job for me too!

BTW: I upgraded to Tumbleweed 20220219 just now and whatever caused it was still broken…

Hi,

teams --disable-seccomp-filter-sandbox

also works and is perhaps not as invasive as --no-sandbox.

Just a FYI. Teams updated a couple of days ago, and the work around is no longer needed for it to work.

I saw the update but did not try to change the work around setting. Thanks for the report.