Arch Linux User Repository

@mluque Yes, it seems that Microsoft is doing the wrong thing and has deleted the packages from the repository. There are several open threads on this topic.

The truth is that since the announcement that Microsoft was going to withdraw the Teams client, one does not know what is going to happen. I hope they restore the files, but in the meantime I have uploaded the binaries here (they are the Arch packages, I don't have the original .deb packages but if someone passes them to me I can include them).

Please, before flag as Out-of-date perform a double check in versions. Version 1.4.00.4855 is higher than 1.3.00.30857, 1.3.00.5153 or 1.3.00.958.

If you doubt, please remember the math classes and perform a count 1, 2, 3, 4, ..., 958, 959, ..., 5152, 5153, 5154, ..., 30856, 30857, 30858, etc.

You can go to HERE, download DEB or RPM and compare versions

@jvybihal: I pick some of your summary to add in the pinned comment ;-)

@jvybihal: thanks for the resume. Adding the --disable-seccomp-filter-sandbox option makes everything work again. Web browser is not a viable alternative for me, I use Firefox and voice calls don't work with it. I'll try to report to Microsoft as well.

@snack in short: teams is now not compatible with glibc 2.35. It is upstream problem (aka Microsoft has to fix it/update). There are workarounds, which can be unstable or insecure. If possible use webbrowser version instead of an app. And ofcourse, report to Microsoft. If only few people will report it, it will always be low priority for them (at least that is my perception).

To everyone: please keep the comments helpful, kinds and informative. If your message does not bring anything constructive to the table, maybe don't post it? Thanks.

@sarvasana I did, and honestly I did not understand if it is related at all with my problem. The pinned comment does not state what's about, and I got lost going back through the endless discussion. So I'm sorry to bother people who are up-to-date with the discussion, but I did my best. I'll go back again and try to sort the endless discussion out. Thanks for your contribution.

@snack

Maybe you can read the endless discussion here before posting your question?
There is even a pinned message...

I don't use teams often but today I tried to open it using the menu entry and it does not start anymore. The icon keeps appearing in the system tray and then disappearing, until it appears definitively but no window is visible. Right click and then Open does not produce any result.

It used to work up to a couple of weeks ago, not sure what I did in the meantime that might broke it (maybe updating Plasma desktop to 5.23?). Any KDE user (X11 session) experiencing the same? Any hint about how to investigate/solve? Thanks.

I can confirm that for me, on X11, --disable-seccomp-filter-sandbox works better than --no-sandbox. No sandbox presents a random behaviour in my system, allowing the application to start on only a fraction of the attempts.