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

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.

Please don't suggest adding --no-sandbox permanently in the package. This should be an ephemeral workaround used with caution, as --no-sandbox itself carries many security risks.

Please add the following line at the end of package():

sed -i -e 's,--disable.*sandbox,--no-sandbox,' "${pkgdir}/usr/bin/teams"

to add the --no-sandbox flag to the /usr/bin/teams invocation script.

The --no-sandbox flag worked for me. Just make sure you kill any non-working teams processes if you are still having issues.

If you don't want to start teams from the terminal all the time, there is no need for a custom AUR package. Just open your favorite editor on /usr/share/applications/teams.desktop or teams-insiders.desktop and edit the "Exec" line in "[Desktop Entry]" to contain the argument. If you're using KDE Plasma and have teams in autostart, also edit ~/.config/autostart/teams.desktop or teams-insiders.desktop or just remove the autostart entry through GUI settings and add it again.

Also make sure to revert and test again after the teams package has been updated.

Is it worth someone releasing a new AUR version, with --no-sandbox added to the command line options in /usr/bin/teams? Would save us from having to launch teams from the terminal each time, and would allow teams to start on login. I'm going to do that on my local machine anyway...

Teams work well with --no-sandbox. However, unable to run and terminated with SIGILL or SIGSYS without --no-sandbox. Strange.

Teams work well with --no-sandbox. However, unable to run and terminated with SIGILL or SIGSYS without --no-sandbox. Strange.