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

Not seeing the same as iyanmv comment. I'm using Wayland and the --disable-seccomp-filter-sandbox workaround (recommended as it disables slightly less security than --no-sandbox). Calls work fine, desktop sharing has not ever worked on Wayland anyway.

If teams has been crashing in calls its probably just normal behaviour for teams ;)

I 100% agree with the packager that we should not be adding flags that reduce security and are hacky at best to the package. If ogarcia changes their mind at least use --disable-seccomp-filter-sandbox

Those suggesting using --no-sandbox or --disable-seccomp-filter-sandbox maybe they just open the app and see that it starts as before, but is still completely broken. Video calls, sharing screen, etc. are completely broken and crash/freeze the app. So if you need Teams to join meetings DO NOT use this app until Microsoft releases a new version compatible with glibc>=2.34. Just use the web version (with Chromium, unfortunately video and screen sharing also does not work with Firefox) or the Flatpack app.

Thanks @karabaja4, --disable-seccomp-filter-sandbox works much better than --no-sandbox. No sandbox fully broke the app for me, but this one seems to be working just like before. No need to use a browser now

@ogarcia I think it would be good, if you also attach the link for the voting to the pinned comment, so it doesn't get lost over all the messages.

Also, as already mentioned using --disable-seccomp-filter-sandbox instead of --no-sandbox might have a lesser impact on weakened security, but it works just as well.

I am 100 % with @ogarcia on this one. It's upstream issue. When google-chrome-dev had almost exact same issue, it was not a job of packager to put potencialy insecure workarouds in place, it has to be done in upstream. That's the correct way. If it would be distro specific issue, I would agree in putting workarounds in place, but it's not. Please, go to Microsoft, report it, and let them know they need to react properly. If they officially do not support Arch, fedora, etc., it shows how they care about their customers, and maybe customers should look for another (potentially) better product.

@linuxninja If you dont want teams rewriting YOUR .desktop file, again, bitch at MS for putting such shitty practise in place. Or make it read only, and maybe add immunitable flag on it.

That's my 2 cents.

IMHO, adding --no-sandbox is the right thing to do for this version, as not running an up-to-date Arch install is not supported. This package should support a newly installed Arch Linux. If it doesn't then this package is broken. Adding the flag makes this package not broken. Do this at least until there is a version update for Teams that resolves the issue, then you can remove the flag.

Sure, doesn't work for every case, but does work for most cases. Add the flag. There shouldn't be a requirement that everyone who installs this package has to come here to see all the drama and what they need to manually do to make it work when it could be already done and 'just work'. Yes, there could be 'security concerns', but, this is the AUR. Making the change manually is the exact same 'security concern' as just having the package do it correctly in the first place.

BTW, Teams likes to create its own teams.desktop autostart file which DOESN'T have the flag. That's a real PITA.

Hi,

Teams (1.4.00.26453) is now not compatible with glibc 2.35. It is upstream problem (aka Microsoft has to fix it/update). Here are the workarounds, which can be unstable or insecure.

For all the people who are requesting to add the --disable-seccomp-filter-sandbox or --no-sandbox option to the package, please note that we do not do it because there are people who do not have that need (for example those who have not yet updated the system).

Anyway, if you want to avoid having to type the command with the --disable-seccomp-filter-sandbox option every time you want to start Teams you can execute the following lines.

mkdir -p "${XDG_DATA_HOME:-$HOME/.local/share}/applications"
cp -a "/usr/share/applications/teams.desktop" \
  "${XDG_DATA_HOME:-$HOME/.local/share}/applications/teams.desktop"
sed -i -e 's,teams %U,teams --disable-seccomp-filter-sandbox %U,' \
  "${XDG_DATA_HOME:-$HOME/.local/share}/applications/teams.desktop"

What this does line by line is:

1. Make sure that the applications directory exists in your XDG_DATA_HOME.
2. Copy the teams.desktop file to the applications directory of your XDG_DATA_HOME.
3. Modify this file to add the --disable-seccomp-filter-sandbox option.

This way you will have a modified .desktop file that will allow you to start Teams with the added option without touching the system files (and without root permissions).

To do it with --no-sandbox (if don't work with --disable-seccomp-filter-sandbox):

mkdir -p "${XDG_DATA_HOME:-$HOME/.local/share}/applications"
cp -a "/usr/share/applications/teams.desktop" \
  "${XDG_DATA_HOME:-$HOME/.local/share}/applications/teams.desktop"
sed -i -e 's,teams %U,teams --no-sandbox %U,' \
  "${XDG_DATA_HOME:-$HOME/.local/share}/applications/teams.desktop"

If you have Teams to start automatically at startup you must also run this:

sed -i -e 's,teams %U,teams --disable-seccomp-filter-sandbox %U,' \
  "${XDG_CONFIG_HOME:-$HOME/.config}/autostart/teams.desktop"

Or if you need do it with --no-sandbox:

sed -i -e 's,teams %U,teams --no-sandbox %U,' \
  "${XDG_CONFIG_HOME:-$HOME/.config}/autostart/teams.desktop"

In the future, when Microsoft gets wise and fixes the bug you will simply be able to delete the desktop files from your home:

rm "${XDG_DATA_HOME:-$HOME/.local/share}/applications/teams.desktop"
rm "${XDG_CONFIG_HOME:-$HOME/.config}/autostart/teams.desktop"

Vote issue in upstream here: https://feedbackportal.microsoft.com/feedback/idea/a75f6ded-438e-ec11-a81b-0022484c51ef

I also had to add --disable-seccomp-filter-sandbox to fix the issue where teams would just launch and there would be nothing but a white box. The logs showed a rendering process crashed.

Adding --disable-seccomp-filter-sandbox is sufficient to fix this issue. I don't know what the security implications are.

I used a custom teams.desktop file to add this option.