This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
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:
Some stats about my system:
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.
It is suggested to use Teams web client(https://teams.microsoft.com) as a urgent workaround.
From your log file, I find the following error message -- getInstallOrUpdateTime failed. It seemingly points to your update operation(sudo apt update && sudo apt upgrade).
I cannot get further more solutions for this now. We will research the log file carefully and do some more tests. If there is any update, I will share here as soon as possible. Thanks for your patience and understanding.
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: Most helpful
Edit /usr/bin/teams and modify the line:
to include the new option --disable-seccomp-filter-sandbox:
The latest glibc update broke another layer of sandboxing in the outdated chromium engine that the Teams Preview for Linux uses. Would be nice to have more frequently updated builds ...
By the way: I had to post this answer in Firefox. I tried posting it in Edge for Linux - with zero extensions loaded! - and the learn.microsoft.site refused to accept the post, thinking a CSRF attack was taking place:
Not a good Monday in Microsoft-on-Linux land all around, by the looks of things.
Worked for me. Been broken all week.
Many thanks!
Arch Linux - updated four days ago (2/21/22).
You are a goddamn saviour. I published your solution on the Manjaro forum for users having trouble with this problem, if that's okay with you.
Works for me as well on openSUSE Tumbleweed.
Thanks @Michael N , this solved the exact symptoms listed on this thread.
My 2 cents, I initially added the "--disable-seccomp-filter-sandbox" option after the existing ones and it did not solve the issue. Then I moved it so it would be the first option of the command line (as shown in your post) and it worked... I don't even want to know the reason why the ordering is impacting here, but I'm sure I won't be the only one doing this "mistake" :)
Worked for me too @Fedora 36, thanks!
Thank you. Worked for me on Fedora 36.
Sign in to comment
Honestly this is why I prefer not to rely on Microsoft products... in fact Microsoft is one of the reasons I use Linux... but not to get too bitchy about it... I installed teams yesterday in preparation for the first meeting of the pandemic that wants to use Teams, and not Zoom, or another VC that doesn't have these kinds of issues... and I have precisely the same issue as described above.
While I would like to have a proper solution too... I do have at least a temporary solution for you Murray, so I hope you aren't impacted for your online learning.
In your home folder, inside the hidden folder ".config", teams created 3 folders (why 3, I dread to think)... make sure teams isn't running, delete these three folders and when you start it again, it will ask you to log in as if it had just been installed... and it will work, for 1 session.
The folders are pretty obvious:-
~/.config/teams
~/.config/Microsoft
~/.config/Microsoft Teams - Preview
For anyone else, I have exactly the same symptoms as Murray.... fresh OS install, fresh teams install... works once after install, then after that will not re-load... just opens blank blue box and waits forever.
Thanks! This is functional as a workaround, and will at least be adequate for me to attend my lessons :) . Still a pain having to log in every time though, and it takes ages to load for first time start, so I'll leave the question open in case anyone knows a less temporary fix.
Oh, please do leave the question open... I came here for a fix too!... normally I wouldn't be found anywhere near a Microsoft forum, but sadly my employer has decided to use teams.
Murray,
I think I'm close to identifying the root cause of this issue can you check on your system in the patch history in /var/lib/apt to see when the last time both teams was updated and when libc 2.34 was installed.,,, and also when you last used it successfully before it stopped working?
I'm pretty sure it's a change to PTHREAD_STACK_MIN in glibc-2.34 that's involved, but I'm not quite sure if the this will impact existing binaries, or just binaries compiled against the new glibc without taking this change into account.
Teams has never been updated through apt. I originally installed via the .deb package from Microsoft's site a few months ago and have not installed an update for it since.
Last time i successfully used teams was around 2pm on 10th September. Discovered it was not working about 7am on 13th September. I had not attempted to open teams between those two dates.
libc-bin_2.34 was first installed at 23:30pm on 6th September.
Here's my update history as per /var/log/apt/history.log if you want to have a look for yourself: 132178-history.log
Hope that helps :)
I'm relatively convinced that the issue is related to this change in glibc, https://sourceware.org/glibc/wiki/Release/2.34#Packaging_Changes - specifically "2.1. Non-constant PTHREAD_STACK_MIN". But I'm not sure why this had so little impact, it seems as if the problematic use of PTHREAD_STACK_MIN is deprecated, bad practice or just rare... as the glibc guys didn't seem to give the change a second thought, and it impacted almost nothing else I could find, except the tor-browser.
Installing the teams deb, adds a source, in /etc/apt/sources.list.d... so it's possible that regular updating of the system could update teams, but it seems that the binary we have has not been updated since May... so the only thing I don't understand is why it didn't break for you on the 6th.... clearly it doesn't impact every code path, so perhaps it had to run once (and work)... to update the settings.conf in such a way that the next time it runs it uses the faulty code path... but I don't know how many times you ran it between
"23:30pm on 6th September" and "around 2pm on 10th September"...
I was able to demonstrate that teams fails to create a thread, getting SIGSYS (signal 31), and precisely this specific failure - "Bad system call. #0 clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:62" - I'm surprised it didn't simply error, perhaps it didn't check that the thread was created successfully?
Is it possible that the 10th was the first time you used it after updating on the 6th?
This is 100% replicated on a fresh 21.10, it works on a fresh 20.04, and the cause seems certain to be some planned fixes in glibc, which may even have to be backported to 20.04 as the new version has security fixes.... but what with 21.10 being released in ~6 weeks, I hope they can step up and fix this up.
Good points. I'm not 100% certain, but it is possible that I only ran teams for one session between the 10th and the 6th.
Sign in to comment
I have same bug on version: teams-1.4.00.26453-1.x86_64
Kernel: 5.16.7
GLibc: glibc-2.35.0.5.249624
Sign in to comment
For me Teams stopped working yesterday on Arch Linux 5.16.9-246-tkg-bmq
The teams processes just restartet themselves over and over again. When I deleted the directories "Microsoft" and "Microsoft Teams - Preview" from my .config directory this issue went away and just a white window is now being shown. See screenshot
Even the web version wont work for me on linux with the latest Vivaldi Browser, on Windows 10 it works....
Please fix this quickly.
I have almost the same problem on a quite similar machine. I run teams on an arch linux, which I updated yesterday. This morning teams behaved weird (input field overrode what I typed with old content), then I restarted teams and since then the splash screen is blank and teams doesn't start. During that time no other windows receive keyboard-input (however, alt-tab works? o.O). I removed all three aforementioned folders, rebooted, even reinstalled teams. I also tried setting
disableGputo true in~/.config/Microsoft/Microsoft Teams/desktop-config.json, but then teams just crashes alltogether. Luckily in my case the web client works.I see errors and crashes in the diagnostic logs, that I can't post here, because of the character limit. Here's an excerpt:
One of my colleagues confirmed that teams is broken this way after
pacman -Syuthis morning (it worked before).I can confirm this, running Teams on Arch Linux, only purple and window borders when I start the app. After deleting all config files in .config/, now I'm just getting white blank space.
I checked both snap and deb versions of teams and its still working on ubuntu so must be something specific to arch. Maybe check with their forums?
Right before it stopped working I've upgraded glibc and other people reported this, too: https://aur.archlinux.org/packages/teams#comment-852066 unfortunately keeping an outdated package version is not an option for me due to company update policies.
Nah, happens here too on openSuse Tumbleweed.
Must be something related to the fact that both Arch and Tumbleweed are bleeding edge.
I hit this in openSuse Tumbleweed this morning as well.
Edit /usr/bin/teams and modify the line:
to include the new option --disable-seccomp-filter-sandbox:
The latest glibc update broke another layer of sandboxing in the outdated chromium engine that the Teams Preview for Linux uses. Would be nice to have more frequently updated builds ...
Sign in to comment
Activity