Arch Linux User Repository

Before marking the package out of date, please first check that the new version is not a pre-release. I'm tracking releases, not pre-releases.

Talk to community members here:

https://matrix.to/#/#teams-for-linux_community:gitter.im

For those who want to have a functional screen sharing version of teams-for-linux

Feel free to download the built package from: https://github.com/frealgagu/archlinux.teams-for-linux/releases/tag/1.0.7.issue.432-1

There is an existing pull request (from which I have taken). I will update the package as soon as the pull request is merged and a new version is released.

In order to make joining a meeting work from Firefox I had to adjust the /usr/share/applications/teams-for-linux.desktop and rerun update-desktop-database

-Exec=teams-for-linux
+Exec=teams-for-linux %U
+MimeType=x-scheme-handler/msteams;

At least it's mentioned in the description

The executable name in the official teams binary is just "teams". and this one has always been "teams-for-linux" I see nothing confusing here.

Honestly I think the name is confusing. Teams for Linux is the actual product that Microsoft provides, and there's this unofficial client. Maybe it should be made clear from the pkgname

I am having trouble joining a meeting in an app with a link.

When I select the link in Firefox, it shows 2 buttons "Download the linux app" and "Try opening again". The try opening again has no effect. Trying with chrome brings 3 options, "Continue on this browser", "Download the linux app" and "Open Your Teams App". Selecting "Continue in this browser" works, but it is in the browser. At least, the link can be validated. Selecting "Open Your Teams App" brings an error:

Failed to open URI. The specified location is not supported. msteams:/l/meetup-join/19:meeting_YzhlMzRhZGMtMTc....f7f8dfca3&launchAgent=join_launcher&type=meetup-join&directDl=true&msLaunch=true&enableMobilePage=true&suppressPrompt=true&fqdn=teams.microsoft.com

I also tried to start it directly, from command line:

teams-for-linux 'msteams:/l/meetup-join/19:meeting_Yzhl...thread.v2/0?context=%7b%22Tid%22%3a%22ba52c71f-fea9-41ae-812c-41215749ab52%22%2c%22Oid%22%3a%22cf2ea543-befa-4568-af97-4f0d5f360f48%22%7d&anon=true&deeplinkId=0ae47fca-a862-46ca-8668-0d4f7f8dfca3&launchAgent=join_launcher&type=meetup-join&directDl=true&msLaunch=true&enableMobilePage=true&suppressPrompt=true&fqdn=teams.microsoft.com'

This time, the "Failed to open URI, shows up", followed by 3 options as in chrome. This time selecting "Continue on this browser" finally opens the link in the app.

Now, I suspect there is some configuration missing. Any hints where to start digging are appreciated.

For anyone coming here after a failed upgrade: the required node.js version is 12.13.0.

Hi @frealgagu

Good job. Thank you.

@gazza_c I've just checked, for each CARCH the installation folder is different.

aarch64:linux-arm64-unpacked

armv7h:linux-armv7l-unpacked

i686:linux-ia32-unpacked

x86_64:linux-unpacked

for x86_64 the folder doesn't contain the name of arch because that is the default.

I've update the PKGBUILD but the pkgrel was not bumped up because there were no changes in the resulting package.

Not certain on the arch of ia32 and x86_64 but to get this working on ARM distro's i added the following to PKGBUILD - can you consider adding this

package() {
  if [[ ${CARCH} == "aarch64" ]]; then
    package_arch_dir="arm64"
  elif [[ ${CARCH} == "armv7h" ]]; then
    package_arch_dir="armv7l"
  fi

  cd "${srcdir}/${pkgname}-${pkgver}"
  install -dm755 "${pkgdir}/opt" "${pkgdir}/usr/bin"
  cp -r --preserve=mode "${srcdir}/${pkgname}-${pkgver}/dist/linux-${package_arch_dir}-unpacked" "${pkgdir}/opt/${pkgname}"
  install -Dm644 "${srcdir}/${pkgname}.desktop" "${pkgdir}/usr/share/applications/${pkgname}.desktop"
  for _file in "${srcdir}/${pkgname}-${pkgver}/build/icons/"*.png
  do
    _filename="$(basename ${_file})"
    install -Dm644 "${_file}" "${pkgdir}/usr/share/icons/hicolor/${_filename%.png}/apps/${pkgname}.png"
  done
  ln -sf "/opt/${pkgname}/${pkgname}" "${pkgdir}/usr/bin/${pkgname}"
}

You will of course have to deal with the ia32 and x64 architectures, i am not even sure how it was working for you? It must just ignore making a folder for the x86_64 and/or ia32 architectures? Not sure.