This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 68%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
[I asked about this on UserVoice forum, but apparently that is no longer active..?]
teams-1.4.00.7556-1.x8664.rpm
Linux distro: Fedora 31
graphical env: xfce
kernel: 5.8.8-100.fc31.x8664
I can send and receive chat messages just fine, as long as I stay focused on the app window, but if I receive a chat message when the app window is not focused, the app appears to freeze for several minutes -- i.e, returning to the app window finds it unresponsive. If I receive a message while in a call (and focused on some other window), the call audio continues normally even though the app freezes. (I don't have a camera, so I can't say what video behavior would be.) When Teams is frozen, there doesn't seem to be any additional CPU usage.
I do not see the problem with the original version I had installed last fall: teams-1.3.00.16851-1, so I've reverted to that. IIRC I also tried downgrading to teams-1.3.00.25560-1 some time ago and saw the issue there too. So I believe it started somewhere between those versions.
BR,
Don
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
Hi @DGIDonE
Does anyone else have the same issue in your organization?
I did a test in my environment and it seems work (Ubuntu 20.04 Teams client version 1.4.00.7556). To exclude the client issue, could you try to login Teams web client to see if it can be reproduced?
In addition, please try to log out Teams client and clear your Teams client cache file, then restart Teams client to see if it can be fixed.
rm -r ~/.config/Microsoft/Microsoft\ Teams
Hi @JimmyYang-MSFT - Thanks for your quick reply!
Does anyone else have the same issue in your organization?
Not that I'm aware of, but I may be the only one using the Linux client. And I'm probably the only one using xfce.
... please try to log out Teams client and clear your Teams client cache file, then restart Teams client to see if it can be fixed.
I exited from the older version, upgraded to the latest (teams-1.4.00.7556-1.x86_64), removed ~/.config/Microsoft*, then re-started the client. The issue is still present.
[I had to split the message into two parts, sorry. The Submit button failed to work with "1 character left".]
... could you try to login Teams web client to see if it can be reproduced?
Just tried that, and it seems to work fine. In fact, I ran both at the same time, and when I received a message, the Linux client froze, but the web client didn't.
I've also noticed that after about 80% of its time of being frozen, the Chat message frame scrolls down slightly, cutting off the bottom of the last message. When it finally un-freezes, it scrolls to correct position.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 74%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZS%3C/text%3E%3C/svg%3E)
Hi @JimmyYang-MSFT ,
I also encountered this problem since yesterday on linux. It seems that the main thread get's blocked somehow...
when I'm in a video conference, the incomming videos, the sound and microphone and screensharing works fine, but nothing else. After a few seconds/minutes, the "we encountered a problem, trying to reconnect" popup occures. after that the ui is responsive again.
my version is also: Microsoft Teams Version 1.4.00.7556 (64-Bit).
os: manjaro
kernel: 5.10.36-2-MANJARO
window-manager: i3 (xserver)
installation via .deb package
Since Fedora 31 isn't really current any more, I tried installing Teams (1.4.00.7556) on another machine, this time with Fedora 33, xfce, and in a VNC session. The behaviour is almost exactly the same. The UI freezes immediately after receipt of a message, and stays frozen for about 1m40s, when both (sometimes) do the slight scroll-down I mentioned. On the F33 box, the app seems to be usable again about 10 seconds after that, and on F31, it's about 20 seconds later. Note: These measurements are from just 2 experiments, with different people sending messages -- it's possible that the times would vary if I did more experiments.
Hi @DGIDonE
Sorry for the delay response!
Our Fedora environment met some issue so we cannot test your situation and give you feedback right now. Once we repair it, we will feedback our test result at once.
In addition, could you try to install Teams client manually by running the following command?
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
sudo sh -c 'echo -e "[teams]\nname=teams\nbaseurl=https://packages.microsoft.com/yumrepos/ms-teams\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" > /etc/yum.repos.d/teams.repo'
sudo dnf check-update
sudo dnf install teams
Hi @JimmyYang-MSFT -
While you're waiting for your Fedora environment to be repaired, it might be interesting to see if the problem appears with xfce in some other distribution. (Just an idea...)
1: Before running the command you gave, I downloaded the key from the URL you gave, ran "rpm -qi gpg-pubkey-be1229cf-5631588c" and verified that the key text in the output matched the downloaded key. Running the command you gave didn't change anything.
3: I verified that the existing /etc/yum.repos.d/teams.repo matches the text in your command. So again, no change.
5 and 6: Since I reverted to the older version of Teams that doesn't have the issue, "dnf check-update" shows that it should be updated to 1.4.00.7556-1. I don't want to do that now on this machine because I need to use it for work. Of course I'm happy to try new versions temporarily for testing, but I can't leave it like that because it isn't really useful when it freezes.
Today I did a test in Fedora 30. The following picture shows our graphical environment. But we did not reproduce this issue in ourenvironment, so this issue looks like only happened in xfce, right?
I can't say it only happens with xfce. I've only tested it with xfce, and for me, it happens with Fedora 31 and 33. It is possible that it only happens with xfce (or only with certain settings I use in xfce), or that it only happens with Fedora version >= 31 -- or some combination of those things.
For me, with the two machines I've tested it on, the problem is 100% repeatable with any of the newer versions of Teams, and I've never seen it happen with the old version (1.3.00.16851) that I have reverted to.
Sorry, one minor correction: The other machine I've tested on is running Fedora 32, not 33. (I have F33 on another computer - not a work computer, so Teams is not installed on that one.)
Here is another data point for you: A co-worker ran the experiment using Teams 1.4.00.7556 on Fedora 31 with Enlightenment window manager. He does not see the problem.
On the earlier comment from @Ziegler, Sven , I suspect what I sometimes see as the "slight scroll down" near the end of the freeze is the "trying to reconnect" message that he reported. For me, the message appears in a gray banner at the top of the screen that pushes everything else down a little. I hadn't noticed that until recently.
Hi @DGIDonE
It is suggested to open a ticket to get more efficient support. The support engineer will collect your backend log file and analyze this problem exactly.
Meanwhile, if I get any update, I will post here.
Thanks for your understanding.
@JimmyYang-MSFT - Sorry for the dumb question, but how does one open a ticket? Here it says:
If you find a bug, submit it using Report a Problem from within the client.
But I haven't found any such button or menu item on the client. There is Help > Give feedback, but I can't tell from the description whether that results in a support ticket.
Thanks
Hi @DGIDonE
Please refer to the phone support part in this article:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 78%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFS%3C/text%3E%3C/svg%3E)
I am facing the same issue as well except that I am using Kubuntu 20.04, and Microsoft Teams version 1.4.00.13653 (64-bit)
I had tried reinstalling but still the problem persisted.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 3%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
Hi !
I have the same problem. I got new computer (HP Zbook) with plenty of RAM (32Gb) and with Ubuntu 20.04.3 LTS (Unity interface). I have tried several solutions so far:
-deleting data directories
None of the solutions work for me.
Andy
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 26%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
As it was mentioned before, the issue is with notifications. On KDE it was enough to ensure that notifications widget is present in system tray and not disabled(can be hidden as far as I can tell).
However this is not a solution, it is disgrace that MS can't make software that doesn't crash if OPTIONAL dependency is not met. So what will it be MS? You've been provided with all the information needed, now will you please fix this? (affects skype as well btw)