Teams fails to load on Linux (teams-1.4.00.26453-1.x86_64.rpm)

Question

question

GrigoryMilev-2783 asked Feb 15, '22 DaveMacias-8300 commented Jul 18, '22

Teams fails to load on Linux (teams-1.4.00.26453-1.x86_64.rpm)

I had problem same as described here (https://docs.microsoft.com/en-us/answers/questions/548771/teams-fails-to-load-on-linux.html#answer-728433)
Only one difference - that's on latest teams version after system update. List of packages, may depends to teams:

I read, that is can be because of glibc version, i use glibc-2.35.0.6.491f2e

Other libc linked to teams on:
ldd /usr/share/teams/teams
linux-vdso.so.1 (0x00007fffd5589000)
libffmpeg.so => /usr/share/teams/libffmpeg.so (0x00007fbf31626000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fbf315e0000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fbf315db000)
librt.so.1 => /lib64/librt.so.1 (0x00007fbf315d6000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007fbf3157a000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fbf31442000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007fbf3126f000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007fbf3112b000)
libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007fbf31126000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007fbf310fb000)
libxcb-dri3.so.0 => /usr/lib64/libxcb-dri3.so.0 (0x00007fbf310f4000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007fbf310ef000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007fbf310e0000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007fbf310db000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007fbf310c6000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007fbf310bd000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007fbf310a9000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007fbf3109c000)
libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007fbf31092000)
libnss3.so => /usr/lib64/libnss3.so (0x00007fbf30f58000)
libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007fbf30f26000)
libsmime3.so => /usr/lib64/libsmime3.so (0x00007fbf30efb000)
libnspr4.so => /usr/lib64/libnspr4.so (0x00007fbf30eb1000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007fbf30e85000)
libatk-bridge-2.0.so.0 => /usr/lib64/libatk-bridge-2.0.so.0 (0x00007fbf30e4c000)
libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007fbf30df6000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007fbf30dcc000)
libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007fbf305b9000)
libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007fbf304b8000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007fbf304a7000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007fbf30450000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007fbf30312000)
libm.so.6 => /lib64/libm.so.6 (0x00007fbf30233000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007fbf30226000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fbf301f6000)
libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007fbf301e0000)
libgbm.so.1 => /usr/lib64/libgbm.so.1 (0x00007fbf301cc000)
libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007fbf300c6000)
libatspi.so.0 => /usr/lib64/libatspi.so.0 (0x00007fbf3008a000)
libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007fbf2ffef000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fbf2ffd5000)
libc.so.6 => /lib64/libc.so.6 (0x00007fbf2fdce000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbf39abf000)
libffi.so.8 => /usr/lib64/libffi.so.8 (0x00007fbf2fdc0000)
libpcre.so.3 => /lib64/libpcre.so.3 (0x00007fbf2fd7b000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007fbf2fd74000)
libz.so.1 => /lib64/libz.so.1 (0x00007fbf2fd57000)
libmount.so.1 => /lib64/libmount.so.1 (0x00007fbf2fd14000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fbf2fce9000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fbf2fce2000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fbf2fcda000)
libplds4.so => /usr/lib64/libplds4.so (0x00007fbf2fcd5000)
libplc4.so => /usr/lib64/libplc4.so (0x00007fbf2fcce000)
libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007fbf2fc06000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007fbf2fbcd000)
libcairo-gobject.so.2 => /usr/lib64/libcairo-gobject.so.2 (0x00007fbf2fbc1000)
libepoxy.so.0 => /usr/lib64/libepoxy.so.0 (0x00007fbf2fa93000)
libfribidi.so.0 => /usr/lib64/libfribidi.so.0 (0x00007fbf2fa73000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007fbf2fa59000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007fbf2f980000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007fbf2f934000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007fbf2f92f000)
libxkbcommon.so.0 => /usr/lib64/libxkbcommon.so.0 (0x00007fbf2f8e7000)
libwayland-cursor.so.0 => /usr/lib64/libwayland-cursor.so.0 (0x00007fbf2f8dd000)
libwayland-egl.so.1 => /usr/lib64/libwayland-egl.so.1 (0x00007fbf2f8d8000)
libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007fbf2f8c6000)
libthai.so.0 => /usr/lib64/libthai.so.0 (0x00007fbf2f8b9000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007fbf2f80f000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007fbf2f746000)
libEGL.so.1 => /usr/lib64/libEGL.so.1 (0x00007fbf2f734000)
libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007fbf2f72f000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007fbf2f71d000)
libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007fbf2f697000)
libwayland-server.so.0 => /usr/lib64/libwayland-server.so.0 (0x00007fbf2f681000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fbf2f3dd000)
libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x00007fbf2f3cf000)
libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x00007fbf2f3ba000)
libgnutls.so.30 => /usr/lib64/libgnutls.so.30 (0x00007fbf2f1f7000)
libblkid.so.1 => /lib64/libblkid.so.1 (0x00007fbf2f1c0000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fbf2f196000)
libzstd.so.1 => /lib64/libzstd.so.1 (0x00007fbf2f0ab000)
liblz4.so.1 => /lib64/liblz4.so.1 (0x00007fbf2f086000)
libgcrypt.so.20 => /lib64/libgcrypt.so.20 (0x00007fbf2ef4a000)
libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007fbf2ef26000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fbf2ef1d000)
libdatrie.so.1 => /usr/lib64/libdatrie.so.1 (0x00007fbf2ef14000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fbf2eef9000)
libbrotlidec.so.1 => /usr/lib64/libbrotlidec.so.1 (0x00007fbf2eeeb000)
libGLdispatch.so.0 => /usr/lib64/libGLdispatch.so.0 (0x00007fbf2ee34000)
libGLX.so.0 => /usr/lib64/libGLX.so.0 (0x00007fbf2ee02000)
libp11-kit.so.0 => /usr/lib64/libp11-kit.so.0 (0x00007fbf2ecd7000)
libidn2.so.0 => /lib64/libidn2.so.0 (0x00007fbf2ecb2000)
libunistring.so.2 => /lib64/libunistring.so.2 (0x00007fbf2eb2e000)
libtasn1.so.6 => /usr/lib64/libtasn1.so.6 (0x00007fbf2eb17000)
libnettle.so.8 => /usr/lib64/libnettle.so.8 (0x00007fbf2eacf000)
libhogweed.so.6 => /usr/lib64/libhogweed.so.6 (0x00007fbf2ea86000)
libgmp.so.10 => /usr/lib64/libgmp.so.10 (0x00007fbf2ea0d000)
libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007fbf2e9e5000)
libbrotlicommon.so.1 => /usr/lib64/libbrotlicommon.so.1 (0x00007fbf2e9c2000)

office-teams-linux-itpro

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KoodziejczykMicha-5010 · Feb 16 at 11:52 AM

I have the same problem on archlinux after upgrading glibc from 2.33 to 2.35. Interesting parts from logs.txt attached174984-logs.txt

1 ·

logs.txt (16.9 KiB)

JimmyYang-MSFT · Feb 16 at 05:31 AM

Hi @GrigoryMilev-2783

What is your operating system?

Do you have any operations before this issue occurred?

Have you tried to use Teams web client to see if it can be fixed.

If there is no issue in Teams web client. it recommends you try to clear your client cache file by running the following command:

rm -r ~/.config/Microsoft/Microsoft\Teams

0 ·

KoodziejczykMicha-5010 JimmyYang-MSFT · Feb 18 at 11:04 AM

Yes, it was after OS update, specifically after upgrading GLIBC from 2.33 to 2.35. As teams is distributed as a binary, it is required that Microsoft recompiles the binary with the new glibc version.

As a work around, I can run teams as teams --no-sandbox

0 ·

GrigoryMilev-2783 · Feb 16 at 08:03 AM

I'm use ALTLinux 64bit OS.
Yes, that issue comes after OS update.
Web client continue to work.
I'm try to remove cache, to remove all configs - do not help at all.

0 ·

JimmyYang-MSFT GrigoryMilev-2783 · Feb 18 at 10:00 AM

@GrigoryMilev-2783

Have you tried to install Teams-insider version in your environment? Does it work for you?

Considering this issue may related to Teams backend issue, we also recommend you to create a ticket from Microsoft 365 admin center.

0 ·

Answer 1 · 2022-02-18T09:57:26.27Z

88588560 answered Feb 18, '22 KristijanKovilevski-2913 commented Mar 10, '22

same Issue on Arch Linux after OS update.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KristijanKovilevski-2913 · Mar 10 at 03:15 PM

on ArchLinux with glibc version 2.35. I have the same issue, workaround with --disable-seccomp-filter-sandbox in .desktop file fixes the issue, but this should be fixed from the get go.

0 ·

Answer 2 · 2022-02-18T10:58:29.407Z

KoodziejczykMicha-5010 answered Feb 18, '22 Dr-6253 published Mar 8, '22

Error occured after OS update, specifically after upgrading GLIBC from 2.33 to 2.35. As teams is distributed as a binary, it is required that Microsoft recompiles the binary with the new glibc version.

As a work around, I can run teams as teams --no-sandbox

· 4

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GrigoryMilev-2783 · Feb 20 at 10:14 AM

Thank you, that help me.

0 ·

MarcoOrfei-4829 · Feb 22 at 06:31 PM

Thanks. It works.

0 ·

JimmyYang-MSFT MarcoOrfei-4829 · Feb 23 at 09:57 AM

Thanks for sharing your workaround about this issue.

@GrigoryMilev-2783

Meanwhile, if the reply is helpful to you, please try to mark it as an answer to close the thread, it will help others who encounter the same issue and read this thread.

Thank you for your understanding and patience!

0 ·

Dr-6253 · Mar 08 at 06:46 PM

This worked for me as well, using Manjaro, glibc 2.35, Teams 1.4.00.26453-1

0 ·

Answer 3 · 2022-02-23T11:02:21.527Z

ChristopheDREVET-7074 answered Feb 23, '22 DaveMacias-8300 commented Jul 18, '22

As commented in https://docs.microsoft.com/en-us/answers/questions/548771/teams-fails-to-load-on-linux.html#answer-744159 by @MichaelN-3933 it is sufficient to add the --disable-seccomp-filter-sandbox option.

I cloned the teams.desktop file to my ~/.local/share/applications folder and changed the command line: Exec=teams --disable-seccomp-filter-sandbox %U

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DaveMacias-8300 · Jul 18 at 01:06 PM

teams --disable-seccomp-filter-sandbox
or
teams --no-sandbox

didnt help for me.

Using manjaro linux with glibc 2.35-6 and teams 1.5.00.10453-1

Teams still crashes the moment i test audio call... with dmesg

[ 2393.503252] traps: teams[87142] general protection fault ip:7fa7b4fe96d7 sp:7fa76f93d018 error:0 in libc.so.6[7fa7b4eb8000+178000]

0 ·

question