Linux client - Electron segmentation fault
Steps to reproduce: use a Linux system with glibc >= 2.31 and run Microsoft Teams Preview, then run dmesg in a terminal. You'll find the following segmentation fault log: [56014.941411] SGI_video_sync[40006]: segfault at e6 ip 00005648d563ef92 sp 00007f66437fc7c0 error 6 in teams[5648d2b5b000+4bf6000] [56014.941417] Code: e8 43 00 00 00 4c 89 f7 e8 db 01 00 00 41 8b 46 10 41 8b 4e 18 c1 e0 0c 25 00 f0 0f 00 c1 e1 14 81 e1 00 00 f0 0f 09 c1 09 d9 <c6> 01 00 81 e3 ff 0f 00 00 c6 03 00 bf 01 00 00 00 e8 38 d0 10 02 This has also affected other Electron applications that use their own bundled Electron on Linux. Here is a very detailed bug report for Discord, where the issue is identical to Microsoft Teams: https://bugs.archlinux.org/task/65643?project=5&string=discord
[Linux V4L] Video isn't working We couldn't use your webcam for video.
I cannot get my video4linux devices working with Teams. OS: Ubuntu 18.04 When I run Teams it shows a report that all devices are connected: But then when I do the test call, a message appears on the top: Video isn't working We couldn't use your webcam for video. All other V4L-compatible apps like for example Vokoscreen work perfectly. Any ideas what's wrong with another MS product on Linux? UPDATE. I checked out logs but found there nother about video or Teams having any issues with video. Basically, when another V4L device gets created, Teams shows no video at all, including the one from the default web camera.
Linux Client: Authentication issue with vIDM (WorkspaceOne Access)
We are testing the new Linux client internally. During first authentication (connect Teams and your account) we run into a "202 ERR_CERT_AUTHORITY_INVALID" error. In the beginning, we first assumed, that it has something to do with our SSL inspection. After some debugging, we now see the root cause somewhere between the Teams client and our IDM. We use WorkspaceOne Access and have a access policy in place for all O365 services - also Teams. The policy is: If coming from an internal (company own external) IP address, try... ...using your Kerberos ticket firstly ...using Username and Password as fallback Since we don't have Kerberos on Linux devices, it actually should fallback to Username and Password. Unfortunately the Teams client overtakes and gives the mentioned error back before vIDM can proceed with the fallback method. I deactivated Kerberos to test the behavior and it is working as expected. After entering Username and Password, Teams connects my user and everything runs well. Does anyone have the same issue or, much better, a workaround for it? Are there somewhere logs on the client we could check? If there is something else I can provide, just ask. Thanks, Alex
problems with teams_1.4.00.26453_amd64.deb
very often, i lose the ability to edit conversations because the "..." icon to edit disappears. i am forced to exit Teams and relaunch Teams. another problem i'm having is that expanding and collapsing replies in conversations erases replies from the UI and again, i have to exit Teams and relaunch Teams to see them again. Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-5 (2021-09-23) x86_64 GNU/Linux Xfce 4.16
