Replies: 1 comment 2 replies
-
|
I can only say that deb is the one people report less issues, but that could be because there are more people using snap. Difficult to tell, but deb has less complexity as it doesn't add the extra snap/flatpak confinement. Regarding performance, I am not sure if this app will make you have better performance, but if you can open an issue and put your logs in there, we can have a look. Sometimes the --disableGpu does magic for some people, but hard to tell without seeing the logs. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! I've now installed the .deb packages and will use it. I will report any bigger issues that I will encounter. As a side question: When I just receive the Teams meeting link (and no meeting ID nor password), does it still work to paste the link into a Chat in the app and open it from there to have the Teams meeting within the app (so that it does not open in the browser)? Or do I need to apply another workaround to open a Teams meeting link in the app? P.S. The performance issues referred to the web-version of MS Teams in the web browsers, before I became aware of Teams-for-linux. |
Beta Was this translation helpful? Give feedback.
-
|
in general, if you copy and paste it should work. Otherwise some people use a redirector app to do this re-forwarding. This 3 issues to look if you have any problems with those links are:
Hope helps! |
Beta Was this translation helpful? Give feedback.
-
I am using Ubuntu 24.4 and I wanted to ask which installation mode you recommend for Teams-for-Linux?
Is the .deb repository, the flatpak or the snap preferable?
I am particularly concerned with performance, as I frequently have performance issues (connection time, broken audio, video stuttering) with Teams using Chromium or Firefox browser. I always have the assumption that the .deb must be the most performant, am I right?
Beta Was this translation helpful? Give feedback.
All reactions