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

Talk to community members here:

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

@wooptoo, you can use the switch --disableAutogain

You can also talk to community members in matrix chat as well.

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

Since 1.4.3-1 I have been getting the following error on build:

Unknown Syntax Error: Unsupported option name ("--pure-lockfile").

I have yarn 1.22.21-1 installed from the extras repo (yarn version 3.6.4) and there is no pure-lockfile argument in that version.

Edit: While I was messing with the PKGBUILD, I found that also both the --non-interactive and --cache-folder arguments are now deprecated. I ended up needing to export YARN_GLOBAL_FOLDER using the cache directory and then just run yarn install. I am not sure if this is the best way to handle installs on newer versions of yarn, but at least I got it working on my end. Keep in mind that this approach migrates the project from yarn 1 before proceeding with the install.

First of all, apologies in advance if this is not the place for this.

Is there a way to disable the Automatic Gain Control for this build? AGC will turn the microphone gain up or down automatically during a call – this is sometimes highly undesirable as it can make some mics very quiet or very loud (which leads to clipping and distortion).

On plain Chromium you can install an extension called 'Disable Automatic Gain Control' to turn this behaviour off. However these extensions will not work on Electron apps as far as i know.

But I think there's a chromium-flags parameter you can set to toggle this behaviour. Is there any way to set the chromium-flags for this build?

Thanks

@pschichtel I did test DNS on my system and both github and the usercontent.github URL did resolve, but for some reason were failing when inside of the makepkg build process. Since then this package has successfully built so I'm assuming I lucked out and hit a rare moment where some other library or package was slightly out of whack. DNS was resolving fine for any other application / makepkg build on my machine at the time. I'll reach out to the github project in the future, but I figured since this was directly related to the ArchLinux AUR build process that this would be the best place to document the issue. Thanks for your help.

I noticed problems with do-not-disturb mode. When i'm in call and i receive new messages, i receive the popup and the sound from every new message...i'm under Gnome DE, and also if i enable "Do Not Disturb" system mode, teams ignore it.

Actually by applying patches for those 3 commits, the one for electron28, and the prior and post commits to it, there's no segfault. Copying the commits patches is too much I believe, but see the prepare method I added:

prepare() {
  cd "${srcdir}/${pkgname}-${pkgver}"
  patch -Np1 < ../pre_electron_28.patch
  patch -Np1 < ../electron_28.patch
  patch -Np1 < ../post_electron_28.patch
}

From here: https://github.com/IsmaelMartinez/teams-for-linux/issues/1001 It's mentioned electron28 fixes the current electron issue on teams-for-linux, and also was the reason for the commit already merged. Who knows when there will be a new release...

Maybe missing

https://github.com/IsmaelMartinez/teams-for-linux/commit/8adcb6e10695b87baf77e3fcbd735997662eeac7

That moves to use electron28... Only thing it requires the commit before, and also the commit after (which fixes the commit before).

teams-for-linux just segfaults with:

teams-for-linux --closeAppOnCross --ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations

Using gdb, doesn't show much, :(

teams-for-linux --closeAppOnCross --ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations

Is there a tip to make teams-for-linux work natively on wayland, and with screen sharing? Also, not using gnome, wyafire instead.

@lisu_ml it seems they pulled the release and indeed it didn't start up for me either. I reverted it back to 1.3.26 until they release 1.4.1