Package Details: teams-for-linux 1.8.0-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: jijojosephk (pschichtel)
Last Packager: pschichtel
Votes: 78
Popularity: 4.34
First Submitted: 2018-04-03 15:36 (UTC)
Last Updated: 2024-07-15 21:32 (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

1 2 3 4 5 6 .. 23 Next › Last »

lyndog commented on 2024-06-26 08:55 (UTC) (edited on 2024-06-30 22:08 (UTC) by lyndog)

Release 1.7.4 fixes the issue with screen sharing. If you need this before the AUR is updated you can change the pkgver=1.7.3 to pkgver=1.7.4 and the sha256 sum to f787704cb9cb25b6e01db2ba544125cb1901fe06b3340960b4e594344f70452f

Edit: 1.7.4 came out the evening of this comment so there should be no need to do any kind of manual fixing now :)

lounges commented on 2024-06-25 16:59 (UTC)

Also running into issues sharing screen in this latest version.

jrd commented on 2024-06-25 10:21 (UTC) (edited on 2024-06-25 14:35 (UTC) by jrd)

I cannot share my screen anymore with this new update/version. The button is not responsive. (X11 under Xfce)

Seems to be fixed in version 1.7.4 https://github.com/IsmaelMartinez/teams-for-linux/issues/1313

[Edit] Yes, 1.7.4 fixed it (sha256: f787704cb9cb25b6e01db2ba544125cb1901fe06b3340960b4e594344f70452f)

Blu3wolf commented on 2024-06-15 01:21 (UTC) (edited on 2024-06-15 06:35 (UTC) by Blu3wolf)

Reported at https://github.com/IsmaelMartinez/teams-for-linux/issues/1302

Edit: Closed as its tracked further upstream: https://github.com/eslint/eslint/issues/18573

pschichtel commented on 2024-06-07 09:52 (UTC)

@Blu3wolf: please report this upstream

Blu3wolf commented on 2024-06-07 05:54 (UTC)

I get some warnings from npm when building this, one of which explicitly says not to use the module: ==> Starting build()... npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

armadillo commented on 2024-06-06 20:54 (UTC) (edited on 2024-06-06 22:41 (UTC) by armadillo)

New version fails to build until npm is installed. New dependency needed?

EDIT: this has apparently now been addressed.

Helios commented on 2024-06-03 11:03 (UTC) (edited on 2024-06-03 11:10 (UTC) by Helios)

For anyone having the following issue with yarn v1.22.22 and kernel 6.9.2-arch1-1, you can export UV_USE_IO_URING=0 before performing the package update. It seems to be related with the latest kernel version. Take a look here: https://github.com/nodejs/node/issues/48444

==> Starting build()... Unknown Syntax Error: Unsupported option name ("--pure-lockfile").

$ yarn install [--json] [--immutable] [--immutable-cache] [--refresh-lockfile] [--check->cache] [--check-resolutions] [--inline-builds] [--mode #0] ==> ERROR: A failure occurred in build(). Aborting... -> error making: teams-for-linux-exit status 4 -> Failed to install the following packages. Manual intervention is required: teams-for-linux - exit status 4

bogzao commented on 2024-06-03 11:00 (UTC)

It worked. The kernel version 6.9.3 was updated at the same time.. I needed to perform a reboot to overcome this problem! Thank you :)

pschichtel commented on 2024-06-03 10:52 (UTC)

@bogzao: it's literally in the last few comments. Upgrade your kernel to at least 6.9.3.