Package Details: teams-for-linux 1.4.37-1

Git Clone URL: https://aur.archlinux.org/teams-for-linux.git (read-only, click to copy)
Package Base: teams-for-linux
Description: Unofficial Microsoft Teams client for Linux using Electron.
Upstream URL: https://github.com/IsmaelMartinez/teams-for-linux
Licenses: GPL-3.0-only
Submitter: ivelkov
Maintainer: frealgagu (jijojosephk, pschichtel)
Last Packager: pschichtel
Votes: 72
Popularity: 3.32
First Submitted: 2018-04-03 15:36 (UTC)
Last Updated: 2024-05-05 19:51 (UTC)

Pinned Comments

pschichtel commented on 2024-04-30 20:18 (UTC) (edited on 2024-04-30 20:19 (UTC) by pschichtel)

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.

jijojosephk commented on 2024-02-05 02:42 (UTC)

Talk to community members here:

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

frealgagu commented on 2020-12-05 17:56 (UTC)

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.teams-for-linux/releases

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »

jpegxguy commented on 2021-03-18 14:07 (UTC)

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

pawelj commented on 2021-02-16 11:13 (UTC) (edited on 2021-02-16 11:27 (UTC) by pawelj)

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.

olof commented on 2021-02-07 16:02 (UTC)

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

gazza_c commented on 2021-02-07 03:23 (UTC)

Hi @frealgagu

Good job. Thank you.

frealgagu commented on 2021-02-07 01:42 (UTC) (edited on 2021-02-07 01:51 (UTC) by frealgagu)

@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.

gazza_c commented on 2021-02-06 08:39 (UTC) (edited on 2021-02-06 08:47 (UTC) by gazza_c)

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.

ismaelmartinez commented on 2021-01-29 10:59 (UTC)

1.0.6 is out there now. The screenshare issue is sorted. Check the https://github.com/IsmaelMartinez/teams-for-linux/issues/406#issuecomment-769440181 comment for an alternative workaround while the package gets ready.

PhotonX commented on 2021-01-24 13:28 (UTC)

Here is a bug report for this issue: https://github.com/IsmaelMartinez/teams-for-linux/issues/406 Looks like using the web version in Chromium is a possible workaround, it also worked for me.

allexj commented on 2021-01-19 18:18 (UTC)

This works better than the official release, but I can't share the desktop

PhotonX commented on 2021-01-12 14:37 (UTC) (edited on 2021-01-24 13:28 (UTC) by PhotonX)

Today I couldn't share my screen with this, anybody else with the same problem? I am shown as presenting (red dot with the white bar over the avatar) and see the little preview window where the presentation can be paused, but my pupils cannot see my presentation (and I cannot either from another machine). It used to work just three weeks ago, before the Christmas break...

The official MS Teams version still works but it cannot share single windows (also couldn't before)...

UPDATE: Here is a bug report for this issue: https://github.com/IsmaelMartinez/teams-for-linux/issues/406 Looks like using the web version in Chromium is a possible workaround, it also worked for me.