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

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

Current makepkg options:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge debug lto)

You can change them to:

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

In order to avoid the *-debug package generation. Aurutils handles both generated packages pretty well, though generating the *-debug package for AUR purposes only is sort of overkill.

This isn't related with the AUR package BTW.

@pathief weird, as upgrad works fine here, and I don't have debug package installed.

Lately I've been having an error while updating this package with yay. It seems that teams-for-linux-debug is a build dependency but not removed after installing.

Before updating I need to run yay --clean teams-for-linux-debug, otherwise the update doesn't work. Just leaving it here in case anyone stumbles on the same problem.

Error below:

Package (2)            Old Version  New Version  Net Change

teams-for-linux        1.4.10-1     1.4.11-1       0.00 MiB
teams-for-linux-debug               1.4.11-1       8.92 MiB

Total Installed Size:  257.21 MiB
Net Upgrade Size:        8.92 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                                                                                                                           [#########################################################################################################] 100%
(2/2) checking package integrity                                                                                                                                         [#########################################################################################################] 100%
(2/2) loading package files                                                                                                                                              [#########################################################################################################] 100%
(2/2) checking for file conflicts                                                                                                                                        [#########################################################################################################] 100%
error: failed to commit transaction (conflicting files)
teams-for-linux-debug: /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1 exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/32/c8758e116376782d0e4f60faa607bd6aff96e1.debug exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596 exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/36/7482b7cf3d6ff358f57acd694a1acdd0302596.debug exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/5c/6db9b54e4ed82973661935a0eca0c1415196ff.debug exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762 exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/73/2e24a29d582f7bc4cea91594e5705a473fc762.debug exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95 exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/a2/1553c76c8c586d630a0323710633cdb676ae95.debug exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/c0/5357cf1476781478b000273e22c93a7b1911f2 exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/c0/5357cf1476781478b000273e22c93a7b1911f2.debug exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0 exists in filesystem (owned by slack-desktop-debug)
teams-for-linux-debug: /usr/lib/debug/.build-id/f4/621c3403815feaf0b0e1f04c3cd0a2aa3dddf0.debug exists in filesystem (owned by slack-desktop-debug)
Errors occurred, no packages were upgraded.
 -> error installing: [/home/xxx/.cache/yay/teams-for-linux/teams-for-linux-1.4.11-1-x86_64.pkg.tar.zst /home/xxx/.cache/yay/teams-for-linux/teams-for-linux-debug-1.4.11-1-x86_64.pkg.tar.zst] - exit status 1

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.