Starting today, Microsoft Teams is available for Linux users in public preview, enabling high quality collaboration experiences for the open source community at work and in educational institutions. ...
Updated Nov 09, 2023
Version 4.0
Blog Post
The log file from Teams, which I capture when I run it, is full of many entries like:
Server response:
[162741:0609/154035.073022:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:
[163963:0609/160248.917561:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:
[165935:0609/163635.505929:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:
[166735:0609/165007.544840:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:
[169256:0609/173609.333265:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
/dev/fd/3: No such file or directory
Server response:
/dev/fd/3: No such file or directory
Server response:
It looks like it does not like being run with:
$ teams >teams.log 2>&1
Well, that's just tough, that's the way it has to run, else it spits out loads of error messages to my terminal.
The current Teams for linux version presents indeed a most disappointing user experience on Linux .