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

@ogarcia and @pschichtel, there's no need for that makepkg option, it doesn't belong to the package. As packagers (AUR users become packagers of our own systems I guess) we control that through /etc/makepkg.conf:

#########################################################################
# GLOBAL PACKAGE OPTIONS
#   These are default values for the options=() settings
#########################################################################
#
# Makepkg defaults: OPTIONS=(!strip docs libtool staticlibs emptydirs !zipman !purge !debug !lto !autodeps)
#  A negated option will do the opposite of the comments below.
#
#-- strip:      Strip symbols from binaries/libraries
#-- docs:       Save doc directories specified by DOC_DIRS
#-- libtool:    Leave libtool (.la) files in packages
#-- staticlibs: Leave static library (.a) files in packages
#-- emptydirs:  Leave empty directories in packages
#-- zipman:     Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge:      Remove files specified by PURGE_TARGETS
#-- debug:      Add debugging flags as specified in DEBUG_* variables
#-- lto:        Add compile flags for building with link time optimization
#-- autodeps:   Automatically add depends/provides
#
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

Currently that also has the side effect of generating an extra package with debug symbols, and I guess it's not something one wants generally speaking, but again the package should not be aware of this, neither be forced to it, since that'll leave the user with no option at all. Granted the user can edit the PKGBUILD, but the same applies for either case, debug or !debug, so I don't thing that belongs in the PKGBUILD.

@ogarcia Can you refer to packaging documentation that recommends this? Otherwise I'm leaving the decision to the people building the package, whether they want -debug packages or not.

@jijojosephk or @pschichtel, please add options=('!debug') before source line to avoid the creation of the debug package (unnecessary in this case) when you makepkg :-)

The message suggesting posting in the AUR package also says at its very end:

Again, the logs can give us hints on this

So I guess perhaps they're looking for a GDB back trace with symbols instead?

There's also the flag --appLogLevels and I would set it to debug, that could be very helpful, but who knows... Besides --disableGPU how about --disableAutogain?

The suggestion to ask here doesn't seem useful, at least in my mind, since the issue reported also indicates the same happens on chromium, not sure if tested, which is sort of the same thing, electron is sort of chromium in disguise. Wondering if firefox fails the same... But if it fails in chromium, I don't see how electron would prevent such failure. Perhaps some flags...

BTW, I know indicating work for me doesn't help, but just so you know, I called my phone from teams-for-linux with no issue, and I also joined a meeting with it with no issues. The office laptop I use has camera. I use the stereo jack plug for headset (mic + audio). I use wayland though. The flags I use:

--closeAppOnCross --disableAutogain --ozone-platform-hint=auto --enable-features=WebRTCPipeWireCapturer --enable-features=WaylandWindowDecorations

I disable auto gain in an attempt to prevent teams-for-linux to change the audio volume when closing, but it insists on doing it...

Hi,

I encounter a problem with this package and the github maintainer advise to post the issue here : the app crash when I try to make or receive a phone call. Strangely enough, the same issue occur with teams in Chromium.

the issue on github for more details : https://github.com/IsmaelMartinez/teams-for-linux/issues/1388

I tried to run the app with gpu acceleration disable, but no success.

Any idea ?

Regards

@bassadin I think it would be best to install debug symbols to report it upstream. Your DE crashing might be the cause of the teams crash, difficult to say for sure without debug symbols.

Lately, I've been seemingly getting random core dumps when alt+tabbing while teams is open, making my whole DE crash/restart: https://pastebin.com/056civ0M

@gurudas I guess the debug packages are overlapping.

Arch n00b and yay user here. I'm getting this error:

error: failed to commit transaction (conflicting files)

when trying to update via yay -Syu. Full error:

/usr/lib/debug/.build-id/04/e9960947a38ced0a87421a6f198b9caf43dc3f exists in both 'teams-for-linux-debug' and 'visual-studio-code-bin-debug'
/usr/lib/debug/.build-id/04/e9960947a38ced0a87421a6f198b9caf43dc3f.debug exists in both 'teams-for-linux-debug' and 'visual-studio-code-bin-debug'

And three more objects exist in both packages. I saw the Arch Wiki page for this error but I'm not sure what to do exactly here:

I ran the recommended command and this package's page came up, so I created an account to post here for help.

$ pacman -Qo /usr/lib/debug/.build-id/04/e9960947a38ced0a87421a6f198b9caf43dc3f
/usr/lib/debug/.build-id/04/e9960947a38ced0a87421a6f198b9caf43dc3f is owned by teams-for-linux-debug 1.8.0-1

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 :)