Teams fails to load on Linux.

Hello,
I have been using Teams on Linux for online learning for the past few months. Up until this morning, it has been working without issue.
As of this morning, when attempting to open Teams the following issue occurs:
- White rectangle the size of teams window briefly appears, then vanishes.
- Several seconds later, the system tray icon appears.
- Finally, the blue window shown below appears, and continues to do nothing. It's not using any CPU, and I have tried just waiting. Nothing had happened after half an hour.
- I have tried running teams as the root user for both of the above options, as well as without root permissions.
- Yes, I've tried restarting the computor :)
The only thing that I can Identify as having changed since Teams stopped working is that I ran an application update (sudo apt update && sudo apt upgrade).
Here's what I have tried so far. None of these have made any difference:
- Uninstalling Teams, and reinstalling from the .deb download on Microsoft's website.
- I've also tried everything on this thread: https://learn.microsoft.com/en-us/answers/questions/35736/teams-on-linux-silently-crashes-my-linux-machine.html
Some stats about my system:
- I am running Ubuntu 21.10 with the Xfce desktop environment.
- Kernel is x86_64 Linux 5.13.0-14-generic
- I am not short on RAM, CPU, or disk space - Teams has run just fine until today.
Here are the logs, as retrieved through the button in the system tray icon.
Teams forms the basis for my year 12 online learning, so it's pretty important that I can get a quick resolution to this.
Thanks,
Murray.
What does the message "getInstallOrUpdateTime failed." actually mean, as a quick search online shows it is extremely common in almost every place a log is posted from Teams, most of which are taken from Windows....
I'm sure it "points to the update operation", in that we updated the client and the new one has a bug, but I think that error is very likely a red herring, given how common (and not platform specific) it appears to be.
Whatever the issue is, it's tied to "settings.json" which gets written to ~/.config/Microsoft/Microsoft Teams if you don't log in, it writes around a 70K file, and then it can load again... but if you log in it writes around a 140K file and cannot load teams again.
If settngs.json is restored to a pre-logged in state then it can load again.
@Knevah , @Murray Jones ,
Agree with Knevah-5715, update should be a red herring because the client has already on the latest version.
Currently, we cannot repro this problem. And we are trying to install same OS version to try again. Any update I will share here.
For me the problem occurred after updating from Ubuntu 20.04 to 21.10. Deleting the ~/.config/Microsoft directory before starting works, but I'm running the browser based version for now.
I've spent a while looking at this, and I found 1 other software project that was impacted with the same error, looking at the stackdump generated by teams, it appears to be an identical problem... which is stems from glibc being more critical of incorrect types for "stacksize".... it's hard to be precise, but the release for glibc notes say:-
2.1. Non-constant PTHREAD_STACK_MIN
In order to better support architectures that need a variable stack size for scalable vector registers the constant value for PTHREAD_STACK_MIN has transitioned to a non-constant value e.g. sysconf call.
You may no longer use PTHREAD_STACK_MIN in a way that treats it like a constant value. The value returned for PTHREAD_STACK_MIN is now of type long and so may generate compiler warnings when compared against an unsigned value e.g. size_t.
This will affect a lot of users in about 6 weeks when they start upgrading Ubuntu, but it seems only one other project was affected and they pushed the fix a bit more than 2 months ago.
I checked the dates that Teams on Linux has been updated:-
2020-10-05 22:13:01
2020-12-02 15:58:54
2021-03-09 23:18:50
2021-04-02 02:31:13
2021-06-08 11:55:11
Any chance this means we're overdue an update?
K
Sign in to comment
Thank you for reporting this issue. As already mentioned in the posts here, the problem is related to glibc 2.34 not being compatible with our implementation. While we look into the issue, we suggest you to use teams from the snapstore. You can install and run it this way:
@Murray Jones ,
Do you try the solution provided by RudolfTomori-MSFT?
If it works, please accept this reply as answer to benefit more people with the same problem.
Have a nice day!
Thanks, this does indeed work :). It seems a lot slower to load that the previous .deb was, but that's not really a big deal - might be just my computer.
@Murray Jones ,
It is really good news.
Sign in to comment
15 additional answers
Sort by: Newest
deleted....
Sign in to comment
Version 1.5 worked fine for me until about mid of August.
Now it has the mentioned startup issue again.
First found it on Arch, now switched to Debian, but still no luck.
Teams Version:
Debian Version:
Linux gopher-cern 5.18.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.16-1 (2022-08-10) x86_64 GNU/Linux
apt Version:
apt 2.5.2 (amd64)
glibc Version:
(Debian GLIBC 2.34-7) 2.34
Tried the official Flatpak with same result.
Also tried the unofficial Flatpak which has another issue complaining about some missing $DISPLAY since I'm in wayland.
Content of the
~/.config/Microsoft/Microsoft\ Teams/logs/teams-startup.log
:According to a colleague of mine latest greatest Ubuntu works well, so it might be some updated component making trouble.
@Rudolf Tomori Do you have any ideas (besides vendor-lock to an unfree operating system created by some british-something multi millionaire)?
Sign in to comment
Hi Rudolf, this version works, but dont know if it would work if I have uninstalled libstdc++6 before it.
Maybe someone else can confirm if this new package works.
Sign in to comment
Hello, we have released a new version 1.5.00.9652 of the package teams-insiders that is compatible with the new glibc. deb rpm Please confirm if it works on your system.
Thanks, this fixed the "We're sorry—we've run into an issue." bug that recently appeared trying to start teams on Ubuntu 20.04.
If there was a prize for unhelpful error messages, this would be a good contender.
Sign in to comment
Activity