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

For me, since the last upgrade, when I start teams, the only thing I see is a white box, completely inoperant. Apparently, the app starts (I can see some rendering), and then this white box is rendered on top of it, and I can neither close it. Completely useless.

Fortunately, I can close the app by using the small icon in the taskbar, but this is all I can do with this app. I had to uninstall it and install the AUR teams-for-linux package instead, which is unofficial, but at least works. Ah .. I can also open the app log, and I noticed I have a very huge log. Maybe I have some old configuration files somewhere, which might be causing this strange behavior (white box), but I was unable to discover where it is.

The only issue for me is that after a restart it doesn't save audio settings, what mic was in use last time. So I have to set it up before the call each time. Has anyone got solution to this ? PS. it is the heaviest app on my machine :)

@luisalcarasr, thanks! I don't use pulseaudio, but running Teams 1.4.00.13653 with apulse fixes the crash when joining the meeting.

EDIT: Unfortunately, running Teams with apulse breaks my microphone. Back to 1.4.00.7556-1 I suppose.

EDIT2: However! After inspecting what exactly /usr/bin/teams does, I digged out a command that should keep apulse running together with Teams in foreground. This seems to work:

/usr/bin/apulse /usr/share/teams/teams --disable-namespace-sandbox --disable-setuid-sandbox 

My microphone is recognized in 1.4.00.13653 and it no longer crashes when joining a meeting. Yay!

Some problems when Teams crashes during the start of a call may be related to an inappropriate installation of pulseaudio.

Default Downloads location is $HOME. to change it install

pacman -S xdg-user-dirs

Set DOWNLOAD to your directory of choice:

xdg-user-dirs-update --set DOWNLOAD $HOME/Downloads/

It looks like they fix the DEB link.

This is the PKBUILD of an rpm-based version you can try while the debian one is broken (modified from this packages' original PKGBUILD and lacking license).

pkgname=teams
pkgver=1.4.00.13653
pkgrel=1
pkgdesc="Microsoft Teams for Linux is your chat-centered workspace in Office 365"
arch=('x86_64')
url="https://teams.microsoft.com/downloads"
license=('custom')
depends=("gtk3" "libxss" "alsa-lib" "libxtst" "libsecret" "nss" "glibc>=2.28-4")
makedepends=("rpmextract")
optdepends=("libappindicator-gtk3: Systray indicator support"
            "org.freedesktop.secrets: Keyring password store support")
conflicts=("ms-teams")
replaces=("ms-teams")
source=("https://packages.microsoft.com/yumrepos/ms-teams/${pkgname}-${pkgver}-${pkgrel}.x86_64.rpm")
noextract=("${pkgname}-${pkgver}-${pkgrel}.x86_64.rpm")
sha256sums=('7a9d674d6fa20094e839cf5aac157b750cb08cffcdc4498f93eccca2577518a0')
package() {
  rpm2cpio "${pkgname}-${pkgver}-${pkgrel}.x86_64.rpm" | gunzip - | (cd "${pkgdir}" && cpio -idum --quiet)

  # Permissions fix
  find "${pkgdir}" -type d -exec chmod 755 {} \;
}

If updated version does not work, just downgrade back to working version. Making more packages makes no sense. And to everyone, I would suggest to go and pressure Microsoft to fix their actual shit. Comments about something not working in user-created package threads are just unnecessary clutter imho. If it is not packaging problem, no one will actually respond to that.