Share via

Teams desktop client for Ubuntu 20 with strange behaviour

Víctor Herreros 31 Reputation points
2021-09-28T09:30:38.197+00:00

Hello,

I've been using Microsoft Teams desktop client for Ubuntu several months ago and I'm recently experiencing annoying issues.

The issues are:

  1. When browsing past threads on any channel, I can only review the last three or four threads. Previous threads appear blurred. See caption 01.png:

135882-01.png

  1. When diving into any thread with more than 2 replies, at first you can see it correctly states it has 'n' replies, but when trying to unfold the replies it only shows the last two ones. After that, if you collapse the replies, it shows the thread has only 2 replies (though it really has 'n' replies).
  2. When posting a new thread or a new reply, it doesn't instantly shows up on screen. You have to move to another channel, and then come back to the channel where you posted, to see your reply refreshed.

My environment is as follows:

  • Ubuntu 20.04.3 LTS 64-bit
  • Microsoft Teams desktop client 1.4.00.13653 (the most recent one)

I've tried the following workarounds without success:
a) Remove teams cache (rm -rf ~/.config/Microsoft/Microsoft\ Teams/).
b) Install older Teams versions (1.3.00.30857 and 1.4.00.7556).
c) Install last Teams insiders version (1.4.00.13653).

I've checked that this errors doesn't appear on Teams desktop client for Windows.

Any idea on how to solve it?

TIA.

Skype for Business Linux
Skype for Business Linux
Skype for Business: A Microsoft communications service that provides communications capabilities across presence, instant messaging, audio/video calling, and an online meeting experience that includes audio, video, and web conferencing.Linux: A family of open-source Unix-like operating systems.
456 questions

19 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Christian Taillon 1 Reputation point
    2021-11-23T19:36:48.497+00:00

    I still have the same issue.

    I now am realizing this issue affects the Web Client version as well. I cannot use Teams channels on my system as in almost every Channel we have threads with more than two comments.

    Does anyone know of any way to escalate this issue to Web or Linux development team?

    0 comments
  2. Davide Brunato 1 Reputation point
    2021-11-25T15:07:21.453+00:00

    Same issues on a Fedora 35 with both the Teams desktop client 1.4.00.26453 (64-bit) or the web client on Chrome 96.0.4664.45 (Official Build) (64-bit).

    This makes Teams pretty unusable on Linux (channels are the most used feature by my team).

    0 comments
  3. vakulenchuk 1 Reputation point
    2022-01-26T17:01:39.2+00:00

    Exact same issue, I can only see things by using the activity screen.
    My messages do not appear unless I switch channels after sending the message.
    and show previous replies only shows the last two, no matter how many previous messages there are.
    Ubuntu 21.10 impish
    Kernel: x86_64 Linux 5.13.0-27-generic
    Teams desktop client 1.4.00.26453 (64-bit)

    0 comments
  4. Víctor Herreros 31 Reputation points
    2022-02-11T07:02:24.463+00:00

    Does anybody knows how can we raise this thread / issue to the development team from Microsoft? Problems are persistent and the confidence we initially put on Teams Linux desktop client is reaching the lowest levels inside my organization.

  5. Ingar Smedstad 1 Reputation point
    2022-03-02T18:08:52.153+00:00

    This problem is also common in my organization.

    Ubuntu 20.04.04, kernel 5.13.0-30-generic and Teams Version 1.4.00.26453 (64-bit).

    I see when channels have unread messages. However, when I enter the channel and read the new messages the channels are not cleared. I also have the same problem with not showing all replies etc.

    I have noticed that if I go into files or some other place than Posts on the channel it works as intended when I return to Posts. This is a tiresome workaround since I have to do it on every channel that is misbehaving.

    And of course - not every channel is affected. I wonder if the amount of messages in the channel is what is causing this…

    0 comments