Arch Linux User Repository

Talk to community members here:

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

I maintain the latest built package at:

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

FYI: it seems I'm currently the only maintainer pushing updates to the package: I'll be back from vacation tomorrow.

@Exanime

Thanks, I used the hack described here:

https://github.com/IsmaelMartinez/teams-for-linux/issues/1156#issuecomment-2022136873

@Mozo Sorry about the delay in my reply, just noticed your message.

I got a prompt as soon as I opened teams-for-linux. It logged me out and I had to re login. After that it said I was being moved to the new Teams

So will this be updated past 1.4.14? 1.4.15 was released 2 weeks ago and since then there have been quite some useful bugfixes and changes up to 1.4.18 (https://github.com/IsmaelMartinez/teams-for-linux/releases/tag/v1.4.18) (or even 1.4.21 pre-release https://github.com/IsmaelMartinez/teams-for-linux/releases/tag/v1.4.21). I'm a bit confused by the comments here over the last couple of days :D The upstream git repo has some pretty good discussion on switching between v1 and v2 (and back again). So unless I'm missing something I don't see why we wouldn't keep this at the latest release version.

@je-vv Thank you very much!

@mozo and @Examine, getting to use v2 is whether driven by your org sending the invitation directly into teams-for-linux once you are logged through teams-for-linux, and you have to accept it. The other way is through an opt-in option added to teams-for-linux on release 1.4.17, but to enable the banner for the opt-in, you have to provide the option --optInTeamsV2 true on the command line, or though the config file.

1.4.16 actually fix an ugly bug for v2 related to recurrent calls for Angular. 1.4.17 added the opt-in alternative. BTW 1.4.17 is already the latest released version. But once again the pre-release fixed some issues with the them, which currently is 1.4.18, so for those willing to voluntary move to v2, or those asked from their orgs to do so, the best is 1.4.18.

I already recommended to keep up to date with discussion:

https://github.com/IsmaelMartinez/teams-for-linux/discussions/1163

So that you get fixes and the like related to v2. teams-for-linux was not ready for changing from angular to react, and some other changes done on v2, so again, it's best to be up to date with that discussion, and test the pre-releases, which quickly become the latest releases any ways, in less than a week or similar.

At any rate, 1.4.14 is already out of date, :)

But if no one is asking you to move to v2, and you're not looking for it either, I believe it's OK to keep using current version here on AUR.

@Exanime

Where you switched to the newer version from? I don't have a ,essage, switch or something.

Just came here to say my organization moved to "new Teams" today; I received noticed when I opened teams-for-linux (v1.4.14) and after a bit of wait while things loaded, everything looks normal and working

One thing I am very happy to see working now (was not working before) is the automated Bluetooth profile switch when joining calls. I used to have a script on a shortcut I could manually use to quickly switch before picking up a call or joining a meeting. Now it does the switch automatically and have been reliable so far!

Actually 1.4.16 release is a much better target, given MS is forcing the move to v2 beyond March 31. This v2 migration will definitely be bumpy. And I'd suggest catching all pre-releases, to catch fixes for issues already found by others...

See discussion: https://github.com/IsmaelMartinez/teams-for-linux/discussions/1163