Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 731670 - net-im/teams-<version?> fails to start(?)
Summary: net-im/teams-<version?> fails to start(?)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Andreas K. Hüttel
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-08 07:34 UTC by nvaert1986
Modified: 2020-09-29 09:52 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nvaert1986 2020-07-08 07:34:52 UTC
The package net-im/teams does not launch. I've tried both to start the application from the GUI and from the terminal, but the application just does not launch. I don't see any messages or logs on the terminal, nor any entries in the journal.

The weird thing is that if I download Teams manually it actually does launch, by simply unpacking the deb file and running ./Downloads/data/usr/bin/teams 

Reproducible: Always

Steps to Reproduce:
1.Launch Microsoft Teams
Actual Results:  
Nothing happens.

Expected Results:  
The Microsoft Teams application that launches.

Running gnome-3.34 on a systemd based desktop
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2020-07-09 16:31:35 UTC
Which version of net-im/teams is installed and failing?
Comment 2 nvaert1986 2020-07-10 06:40:27 UTC
Both versions 1.3.00.5153 and 1.3.00.16851 do not work. Initially I didn't report it with version 1.3.00.5153 as I thought it was a bug in Teams or something wrong with my configuration, but since the problem still persists with version 1.3.00.16851 I decided to file a bug report.

Version 1.3.00.958 did work when it was initially released and I emerged it. After the upgrade to version 1.3.00.5153 is when the problem started. 

It's not a critical bug for me, as I currently just download the updates manually and start it manually using the Terminal, but it would be nice if it would properly integrate into my system of course.
Comment 3 Sven Eden 2020-09-17 06:14:38 UTC
(In reply to nvaert1986 from comment #2)
> Both versions 1.3.00.5153 and 1.3.00.16851 do not work.

Just out of curiosity: Does app-office/teams-insiders from my overlay "seden" (via layman) work?
Because if so, then it just might be a slight difference in the installation routines.
Comment 4 nvaert1986 2020-09-17 06:44:07 UTC
(In reply to Sven Eden from comment #3)
> (In reply to nvaert1986 from comment #2)
> > Both versions 1.3.00.5153 and 1.3.00.16851 do not work.
> 
> Just out of curiosity: Does app-office/teams-insiders from my overlay
> "seden" (via layman) work?
> Because if so, then it just might be a slight difference in the installation
> routines.

I just gave it a try and it gives the exact same problem unfortunately. It doesn't show anything, besides a spinning waiting icon, when I hover over my main bar in Gnome.

I'm currently using the downloaded and unpacked .deb file from the Microsoft website by running ./Documents/teams/usr/bin/teams. This is the only way to get it to work so far and works with any version, including the latest.
Comment 5 Sven Eden 2020-09-17 16:04:02 UTC
(In reply to nvaert1986 from comment #4)
> (In reply to Sven Eden from comment #3)
> > Just out of curiosity: Does app-office/teams-insiders from my overlay
> > "seden" (via layman) work?
> > Because if so, then it just might be a slight difference in the installation
> > routines.
> 
> I just gave it a try and it gives the exact same problem unfortunately. It
> doesn't show anything, besides a spinning waiting icon, when I hover over my
> main bar in Gnome.

That sounds like it is waiting for something.

> I'm currently using the downloaded and unpacked .deb file from the Microsoft
> website by running ./Documents/teams/usr/bin/teams. This is the only way to
> get it to work so far and works with any version, including the latest.

Unfortunately I am completely at sea here. Without more information, I am afraid, we won't find out what the matter is.

Could you please be so kind and upload both outputs from
  emerge --info
and
  strace /usr/bin/teams-insiders 2>/tmp/teams-strace.log
as attachments here?
Comment 6 Jordi 2020-09-20 10:51:45 UTC
The issue happened to me upgrading to version 1.3.00.16851-r1 where dependency from gnome-base/libgnome-keyring has been changed in favor of app-crypt/libsecret

emerge --info:
Portage 3.0.4 (python 3.7.8-final-0, default/linux/amd64/17.1, gcc-10.2.0, glibc-2.32-r1, 5.8.5-gentoo x86_64)
=================================================================
System uname: Linux-5.8.5-gentoo-x86_64-AMD_Ryzen_5_3600_6-Core_Processor-with-gentoo-2.7
KiB Mem:    16351108 total,  12125552 free
KiB Swap:    5241852 total,   5241852 free
Head commit of repository gentoo: 1106fa28ab21bcb48c8476039eeeb99851d96c5c

sh bash 5.0_p18
ld GNU ld (Gentoo 2.34 p6) 2.34.0
app-shells/bash:          5.0_p18::gentoo
dev-java/java-config:     2.3.1::gentoo
dev-lang/perl:            5.30.3::gentoo
dev-lang/python:          2.7.18-r2::gentoo, 3.7.8-r2::gentoo
dev-util/cmake:           3.16.5::gentoo
dev-util/pkgconfig:       0.29.2::gentoo
sys-apps/baselayout:      2.7::gentoo
sys-apps/openrc:          0.42.1::gentoo
sys-apps/sandbox:         2.18::gentoo
sys-devel/autoconf:       2.13-r1::gentoo, 2.69-r5::gentoo
sys-devel/automake:       1.16.1-r1::gentoo
sys-devel/binutils:       2.34-r2::gentoo
sys-devel/gcc:            10.2.0-r1::gentoo
sys-devel/gcc-config:     2.3.1::gentoo
sys-devel/libtool:        2.4.6-r6::gentoo
sys-devel/make:           4.2.1-r4::gentoo
sys-kernel/linux-headers: 5.4-r1::gentoo (virtual/os-headers)
sys-libs/glibc:           2.32-r1::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: git
    sync-uri: https://gitweb.gentoo.org/repo/gentoo.git/
    priority: -1000

x-portage
    location: /usr/local/portage
    masters: gentoo
    priority: 0

ArtSoftware
    location: /var/lib/layman/ArtSoftware
    masters: gentoo
    priority: 50

ROKO__
    location: /var/lib/layman/ROKO__
    masters: gentoo
    priority: 50

erayd
    location: /var/lib/layman/erayd
    masters: gentoo
    priority: 50

pentoo
    location: /var/lib/layman/pentoo
    masters: gentoo
    priority: 50

riru
    location: /var/lib/layman/riru
    masters: gentoo
    priority: 50

vifino-overlay
    location: /var/lib/layman/vifino-overlay
    masters: gentoo
    priority: 50

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=znver2 -O2 -pipe -fomit-frame-pointer -fgraphite-identity -floop-nest-optimize"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-march=znver2 -O2 -pipe -fomit-frame-pointer -fgraphite-identity -floop-nest-optimize"
DISTDIR="/usr/portage/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://ftp-stud.hs-esslingen.de/pub/Mirrors/gentoo/ http://mirrors.evowise.com/gentoo/"
LANG="en_GB.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en_GB"
MAKEOPTS="-j12"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X acl alsa amd64 berkdb bzip2 cli crypt cups dbus dri elogind eselect-ldso evdev ffmpeg fortran gdbm iconv jpeg lame libglvnd libnotify libtirpc mp3 multilib ncurses nls nptl nvidia opengl openmp pam pcre png policykit readline seccomp smp split-usr ssl symlink tcpd threads tiff truetype udev unicode xml zlib" ABI_X86="64" ADA_TARGET="gnat_2018" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sha sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" GRUB_PLATFORMS="emu" INPUT_DEVICES="evdev wacom" KERNEL="linux" L10N="en-GB" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-2 php7-3 php7-4" POSTGRES_TARGETS="postgres10 postgres11" PYTHON_SINGLE_TARGET="python3_7" PYTHON_TARGETS="python3_7" QEMU_SOFTMMU_TARGETS="x86_64" QEMU_USER_TARGETS="x86_64" RUBY_TARGETS="ruby25" USERLAND="GNU" VIDEO_CARDS="nvidia" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 7 Geoff Leach 2020-09-21 11:23:35 UTC
(In reply to Jordi from comment #6)
> The issue happened to me upgrading to version 1.3.00.16851-r1 where
> dependency from gnome-base/libgnome-keyring has been changed in favor of
> app-crypt/libsecret

Yes, libgnome-keyring dependency is part of the binary blobs that teams installs


>ldd /usr/share/teams-insiders/resources/app.asar.unpacked/node_modules/keytar3/build/Release/keytar.node	

libgnome-keyring.so.0 => /usr/lib64/libgnome-keyring.so.0 (0x00007fa6595e0000)

I think unmasking and reinstalling libgnome-keyring will allow to work, but retrograde step. 

MS been particularly quiet about updated Linux Teams. Despite big pronouncements re open source when Teams was first released for Linux. But there probably will be an update soon, which might remove that dependency.

As far as I can figure, after looking in to it just a bit, Teams is not actually open source.
Comment 8 Ken Cuvelier 2020-09-21 18:43:28 UTC
I can confirm that unmasking and installing gnome-base/libgnome-keyring allowed teams to work on my computer. Taking it one step further, allowing gnome-base/libgnome-keyring to be removed via emerge --depclean leaves behind the key shared object file, with the only annoyance being repeated reminders about preserved libraries which cannot be resolved via emerge @preserved-rebuild.
Comment 9 Larry the Git Cow gentoo-dev 2020-09-22 08:01:26 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9f5f45e3bd224822083a2cde9af84d0d0b9c51f

commit a9f5f45e3bd224822083a2cde9af84d0d0b9c51f
Author:     Andreas K. Hüttel <dilfridge@gentoo.org>
AuthorDate: 2020-09-22 07:58:34 +0000
Commit:     Andreas K. Hüttel <dilfridge@gentoo.org>
CommitDate: 2020-09-22 08:01:09 +0000

    Revert "net-im/teams: Remove dep on libgnome-keyring"
    
    Didnt work as planned, see bug 731670
    This reverts commit e8f8cb5dd48ac39e69d7eb4214063cc98c741d68.
    
    Closes: https://bugs.gentoo.org/731670
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 .../teams/{teams-1.3.00.16851-r1.ebuild => teams-1.3.00.16851-r2.ebuild} | 1 +
 1 file changed, 1 insertion(+)

Additionally, it has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=86a1550e053c136316eb30216fac89ca142e1b49

commit 86a1550e053c136316eb30216fac89ca142e1b49
Author:     Andreas K. Hüttel <dilfridge@gentoo.org>
AuthorDate: 2020-09-22 08:00:19 +0000
Commit:     Andreas K. Hüttel <dilfridge@gentoo.org>
CommitDate: 2020-09-22 08:01:12 +0000

    package.mask: Drop mask of libgnome-keyring again, bug 731670
    
    Bug: https://bugs.gentoo.org/731670
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 profiles/package.mask | 6 ------
 1 file changed, 6 deletions(-)
Comment 10 Sven Eden 2020-09-22 08:49:08 UTC
I have updated my app-office/teams-insiders ebuild ("seden" overlay) to no longer depend on libgnome-keyring, and instead remove the entire
 /usr/share/teams-insiders/resources/app.asar.unpacked/node_modules/keytar3
directory.

Then I removed libgnome-keyring, re-emerged teams-insiders, and it works just fine since then.

Could you please have a look and test whether this works for you, too?

Note: When keytar3 is removed, keytar4 is used by teams, which is linked against libsecret.
Comment 11 Thibaud CANALE 2020-09-22 11:32:00 UTC
Hello,

TL;DR: "ldconfig" needs to be run after installation, we can completely get ride of gnome-base/libgnome-keyring.

(In reply to nvaert1986 from comment #0)
> The package net-im/teams does not launch. I've tried both to start the
> application from the GUI and from the terminal, but the application just
> does not launch. I don't see any messages or logs on the terminal, nor any
> entries in the journal.

The file you are looking for is "~/.config/Microsoft/Microsoft Teams/logs/teams-startup.log".

I had the same issue (still talking about net-im/teams-1.3.00.16851-r1, i.e without gnome-base/libgnome-keyring) with this content:
> /usr/share/teams/teams: error while loading shared libraries: libffmpeg.so: cannot open shared object file: No such file or directory

I noticed the ebuild deletes the libffmpeg.so library provided by the package, and then creates the environment file "/etc/env.d/99teams":
> LDPATH=/usr/lib64/chromium

which will modify (through env-update) the file "/etc/ld.so.conf" to add the entry for "/usr/lib64/chromium", where the libffmpeg.so file exists thanks to media-video/ffmpeg[chromium].

However -- which is the reason of this issue -- after I install this package, Microsoft’s Teams doesn’t start, because even ldd doesn’t see the update of /etc/ld.so.conf:
> % ldd /usr/share/teams/teams | grep -Fe 'libffmpeg' -
> 	libffmpeg.so => not found

I noticed the cache, /etc/ld.so.cache, is _not_ updated, hence why "ldd" doesn’t find the required library.

Solution: I ran "ldconfig" (as root, of course).

Results: Microsoft’s Teams works!
> % ldd /usr/share/teams/teams | grep -Fe 'libffmpeg' -         
> 	libffmpeg.so => /usr/lib64/chromium/libffmpeg.so (0x00007fd26a169000)

So, I guess we could definitively get ride of gnome-base/libgnome-keyring, once and for all; this issue was not about it, the problem was the /etc/ld.so.cache content which was not updated.

I saw from its man page than env-update(1) is called after each emerge, and by default will run "ldconfig" too (except with "--no-ldconfig"). Is there an issue with Portage about it?

Please reopen this bug, removes once again gnome-base/libgnome-keyring, and just call "ldconfig".
Comment 12 Joakim Tjernlund 2020-09-22 12:05:04 UTC
Just add an symlink in Teams:
	
        dest=/usr

	insinto /
	doins -r usr
	fperms +x $dest/bin/teams-insiders
	fperms +x $dest/share/teams-insiders/teams-insiders
	fperms +x $dest/share/teams-insiders/libffmpeg.so
	fperms +x $dest/share/teams-insiders/libEGL.so
	fperms +x $dest/share/teams-insiders/libGLESv2.so
	fperms +x $dest/share/teams-insiders/swiftshader/libEGL.so
	fperms +x $dest/share/teams-insiders/swiftshader/libGLESv2.so
	#use system ffmpeg, needs USE=chromium and a symlink: /usr/lib64/libffmpeg.so -> chromium/libffmpeg.so
	rm -f "${D}"/$dest/share/teams-insiders/libffmpeg.so
	dosym "../../$(get_libdir)/chromium/libffmpeg.so" "$dest/share/teams-insiders/libffmpeg.so"
Comment 13 Sven Eden 2020-09-22 12:09:30 UTC
Please be aware that >=media-video/ffmpeg-4.3 might crash MS Teams.
The same applies to >=media-libs/mesa-20.1 if you want to unbundle those as well.
Comment 14 Sven Eden 2020-09-22 12:12:44 UTC
How about this with system-ffmpeg and system-mesa USE flags?

--------
        # Use system ffmpeg, if wanted. Might crash MS Teams!
        if use system-ffmpeg; then
                rm -f "${D}"/${dest}/share/${PN}/libffmpeg.so
                dosym "${dest}/$(get_libdir)/chromium/libffmpeg.so" "${dest}/share/${PN}/libffmpeg.so"
        else
                # Otherwise keep the executable bit on the bundled lib
                doexe "${S}"${dest}/share/${PN}/libffmpeg.so
        fi

        # Use system mesa, if wanted. Might Crash MS Teams!
        if use system-mesa; then
                rm -f "${D}"/${dest}/share/${PN}/libEGL.so
                rm -f "${D}"/${dest}/share/${PN}/libGLESv2.so
        else
                # Otherwise keep original executable flag
                doexe "${S}"/${dest}/share/${PN}/libEGL.so
                doexe "${S}"/${dest}/share/${PN}/libGLESv2.so
        fi
--------
Comment 15 Thibaud CANALE 2020-09-22 20:21:30 UTC
Ok, I found why the file /etc/ld.so.cache is not updated by the call of portage.util.env_update: the variable "makelinks" becomes False at line 303, because the "libdir" content didn’t change, which is True: Teams doesn’t push a new library in libdirs.

I guess we could fix this issue once and for all, and for other package relying too on libffmpeg, by moving the creation of the new LDPATH content inside /etc/env.d inside the source, FFMPEG’s ebuild.

For me, it doesn’t make sense to rely on other packages -- net-im/teams -- to provide access to a library installed by its main package -- media-video/ffmpeg.

Meanwhile, the solution is to call env-update (or directly ldconfig).
Comment 16 Jordi 2020-09-26 09:34:40 UTC
Teams-1.3.00.16851 downloaded from Microsoft website works without libgnome-keyring. 

Why the solution here is to include back again the dependency?

OTOH, the ffmpeg situation is also resolved using the deb package from Microsoft, so I guess a USE à la "system-ffmpeg" could be beneficial to either use the bundled ffmpeg or the system one.
Comment 17 Sven Eden 2020-09-28 19:17:53 UTC
(In reply to Jordi from comment #16)
> Teams-1.3.00.16851 downloaded from Microsoft website works without
> libgnome-keyring. 
> 
> Why the solution here is to include back again the dependency?

I have the same question. As I wrote in comment #10:

(In reply to Sven Eden from comment #10)
> I have updated my app-office/teams-insiders ebuild ("seden" overlay) to no
> longer depend on libgnome-keyring, and instead remove the entire
>  /usr/share/teams-insiders/resources/app.asar.unpacked/node_modules/keytar3
> directory.
> 
> Note: When keytar3 is removed, keytar4 is used by teams, which is linked
> against libsecret.

So by simply removing keytar3, there is no linker issue any more, and libsecret is used just fine.

I have installed using my ebuild a week ago, and no issues arrised. And we use Teams heavily at work, with much homeoffice and many video conferencing, organizing tasks in Planner and even have a GitLab connector in place.

However, I just saw this in the Microsoft repo at
https://packages.microsoft.com/repos/ms-teams/pool/main/t/teams-insiders/ :
  teams-insiders_1.3.00.25560_amd64.deb  25-Sep-2020 11:49  71799998

Yay! Ebuild updated. ("seden" overlay)

Currently it does not work with USE="system-ffmpeg" with ffmpeg-4.3.1. Maybe ffmpeg-4.2.4 works, haven't tried that, yet, but I have adapted the dependencies accordingly.

However, USE="system-mesa" with mesa-20.1.8 works pretty well.
Comment 18 Sven Eden 2020-09-28 19:44:56 UTC
(In reply to Sven Eden from comment #17)
> Currently it does not work with USE="system-ffmpeg" with ffmpeg-4.3.1. Maybe
> ffmpeg-4.2.4 works, haven't tried that, yet, but I have adapted the
> dependencies accordingly.

Currently running with both system-ffmpeg (downgraded ffmpeg for that) and system-mesa. No problems so far.
Comment 19 Thibaud CANALE 2020-09-28 20:49:11 UTC
(In reply to Sven Eden from comment #17)
../..
> Currently it does not work with USE="system-ffmpeg" with ffmpeg-4.3.1. Maybe
> ffmpeg-4.2.4 works, haven't tried that, yet, but I have adapted the
> dependencies accordingly.

Did you try to see if /etc/ld.so.cache was up-to-date after emerging Microsoft’s Teams as I explained in comment 11?
The correct way to see if it works is to execute this command: ldd /usr/share/teams/teams | grep -Fe ffmpeg -

In case it says not found, execute as root `env-update` (or `ldconfig`, but the first one also runs `ldconfig` in most case).

Anyway, if we want gnome-base/libgnome-keyring to get discarded, we better open up a new bug report; as this one is marked resolved, no dev will read its content.
Comment 20 Sven Eden 2020-09-29 09:52:37 UTC
(In reply to Thibaud "thican" CANALE from comment #19)
> (In reply to Sven Eden from comment #17)
> ../..
> > Currently it does not work with USE="system-ffmpeg" with ffmpeg-4.3.1. Maybe
> > ffmpeg-4.2.4 works, haven't tried that, yet, but I have adapted the
> > dependencies accordingly.
> 
> Did you try to see if /etc/ld.so.cache was up-to-date after emerging
> Microsoft’s Teams as I explained in comment 11?
> The correct way to see if it works is to execute this command: ldd
> /usr/share/teams/teams | grep -Fe ffmpeg -

Of course I did. I used
  ebuild teams-insiders-1.3.00.25560.ebuild install
and then checked ldd output on _ALL_ executables and libraries.

Currently I have:
 ~ $ eix -xlcnI "(media-libs/mesa|media-video/ffmpeg|teams)"
[I] app-office/teams-insiders [1] (1.3.00.25560@28.09.2020): Microsoft Teams Linux Client (Insiders Build)
[I] media-libs/mesa (20.1.8@28.09.2020): OpenGL-like graphic library for Linux
[U] media-video/ffmpeg (4.2.4(0/56.58.58)@28.09.2020 -> (~)4.3.1(0/56.58.58)^td): Complete solution to record/convert/stream audio and video. Includes libavcodec
[1] "seden" /var/lib/layman/seden

Works like a charm