Ms teams arch linux

Arch Linux User Repository

@mluque Yes, it seems that Microsoft is doing the wrong thing and has deleted the packages from the repository. There are several open threads on this topic.

The truth is that since the announcement that Microsoft was going to withdraw the Teams client, one does not know what is going to happen. I hope they restore the files, but in the meantime I have uploaded the binaries here (they are the Arch packages, I don’t have the original .deb packages but if someone passes them to me I can include them).

ogarcia commented on 2022-02-01 10:30 (UTC) (edited on 2022-04-19 12:53 (UTC) by ogarcia)

Please, before flag as Out-of-date perform a double check in versions. Version 1.4.00.4855 is higher than 1.3.00.30857, 1.3.00.5153 or 1.3.00.958.

If you doubt, please remember the math classes and perform a count 1, 2, 3, 4, . 958, 959, . 5152, 5153, 5154, . 30856, 30857, 30858, etc.

You can go to HERE, download DEB or RPM and compare versions

Latest Comments

karabaja4 commented on 2021-06-09 00:34 (UTC)

@gavinhungry — Have the same problem. Also reverted.

gavinhungry commented on 2021-06-08 19:38 (UTC)

1.4.00.13653-1 crashes for me every time I join a meeting. I’ve reverted to 1.4.00.7556-1.

godvino commented on 2021-06-08 14:49 (UTC)

By looking at «$HOME/.config/Microsoft/Microsoft Teams/logs.txt» I can see that they have upgraded their electron version to 10.4.5 which was released a month ago. So atleast Microsoft is doing something.

erickochen commented on 2021-06-08 10:22 (UTC)

Really interested in a changelog or release notes with 1.4.00.13653 being released.

count_zero commented on 2021-06-08 10:12 (UTC)

code_xpert commented on 2021-06-04 12:47 (UTC)

@linuxpro I have the EXACT same problem! I have been using Skype a lot too, and it has been working flawlessly. I would expect Teams and Skype to work the same, as they have basically the same dependencies. I guess chromium is pretty much the only choice. (at least for now)

linuxpro commented on 2021-06-04 12:31 (UTC)

@code_xpert Been having the problem with the microphone for the last 3 months. Sometimes it works flawlessly, sometimes it stops immediately and I can’t get the microphone to work again. Never had a problem when using BBB, Zoom, Skype etc; I also tried different sound devices. Only stable solution at this point is using it via Chromium.

bu.domino commented on 2021-06-01 23:20 (UTC) (edited on 2021-06-01 23:24 (UTC) by bu.domino)

I did my own digging and found this post from a week ago that says it’s fixed in the latest teams-insiders package.

I can confirm that it works. We’ll have to wait for the insiders package to be released as the mainstream version (so this package won’t work in the meantime) but at least we have proof that Microsoft was able to fix it on their end.

MorningWood commented on 2021-06-01 01:38 (UTC) (edited on 2021-06-01 01:46 (UTC) by MorningWood)

@code_xpert I was going to edit my previous comment (again) to note the fact that spoofing the user agent seems to work until I tried joining a meeting. It seems that it actually is not compatible as I get an error message.

In the meantime I’ve tried the Teams-for-Linux variant and it appears to sidestep the «you haven’t signed up for Teams» issue but now when test joining a meeting, clicking a meeting link doesn’t wind up actuating the meeting. Come on, Microsoft.

E: If only I scrolled SLIGHTLY and read @pawelj’s comment.

«In order to make joining a meeting work from Firefox I had to adjust the /usr/share/applications/teams-for-linux.desktop and rerun update-desktop-database

-Exec=teams-for-linux +Exec=teams-for-linux %U +MimeType=x-scheme-handler/msteams; «

code_xpert commented on 2021-05-31 16:38 (UTC)

I found the same problem too. I am on the latest update, I don’t know about you @MorningWood. The fastest solution is to spoof your user agent (to «fix» the incompatibility) with an extension and use Teams like this temporarily. I haven’t gone down that road (yet) with the web app Teams, so YMMV.

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Arch Linux User Repository

@mluque Yes, it seems that Microsoft is doing the wrong thing and has deleted the packages from the repository. There are several open threads on this topic.

The truth is that since the announcement that Microsoft was going to withdraw the Teams client, one does not know what is going to happen. I hope they restore the files, but in the meantime I have uploaded the binaries here (they are the Arch packages, I don’t have the original .deb packages but if someone passes them to me I can include them).

ogarcia commented on 2022-02-01 10:30 (UTC) (edited on 2022-04-19 12:53 (UTC) by ogarcia)

Please, before flag as Out-of-date perform a double check in versions. Version 1.4.00.4855 is higher than 1.3.00.30857, 1.3.00.5153 or 1.3.00.958.

If you doubt, please remember the math classes and perform a count 1, 2, 3, 4, . 958, 959, . 5152, 5153, 5154, . 30856, 30857, 30858, etc.

You can go to HERE, download DEB or RPM and compare versions

Latest Comments

rlees85 commented on 2022-02-28 13:34 (UTC)

Not seeing the same as iyanmv comment. I’m using Wayland and the —disable-seccomp-filter-sandbox workaround (recommended as it disables slightly less security than —no-sandbox ). Calls work fine, desktop sharing has not ever worked on Wayland anyway.

If teams has been crashing in calls its probably just normal behaviour for teams 😉

I 100% agree with the packager that we should not be adding flags that reduce security and are hacky at best to the package. If ogarcia changes their mind at least use —disable-seccomp-filter-sandbox

iyanmv commented on 2022-02-28 08:51 (UTC)

Those suggesting using —no-sandbox or —disable-seccomp-filter-sandbox maybe they just open the app and see that it starts as before, but is still completely broken. Video calls, sharing screen, etc. are completely broken and crash/freeze the app. So if you need Teams to join meetings DO NOT use this app until Microsoft releases a new version compatible with glibc>=2.34 . Just use the web version (with Chromium, unfortunately video and screen sharing also does not work with Firefox) or the Flatpack app.

DarkXylese commented on 2022-02-28 08:49 (UTC)

Thanks @karabaja4, —disable-seccomp-filter-sandbox works much better than —no-sandbox . No sandbox fully broke the app for me, but this one seems to be working just like before. No need to use a browser now

AUR_user commented on 2022-02-28 08:46 (UTC)

@ogarcia I think it would be good, if you also attach the link for the voting to the pinned comment, so it doesn’t get lost over all the messages.

karabaja4 commented on 2022-02-27 19:59 (UTC)

Also, as already mentioned using —disable-seccomp-filter-sandbox instead of —no-sandbox might have a lesser impact on weakened security, but it works just as well.

jvybihal commented on 2022-02-27 19:49 (UTC) (edited on 2022-02-27 19:51 (UTC) by jvybihal)

I am 100 % with @ogarcia on this one. It’s upstream issue. When google-chrome-dev had almost exact same issue, it was not a job of packager to put potencialy insecure workarouds in place, it has to be done in upstream. That’s the correct way. If it would be distro specific issue, I would agree in putting workarounds in place, but it’s not. Please, go to Microsoft, report it, and let them know they need to react properly. If they officially do not support Arch, fedora, etc., it shows how they care about their customers, and maybe customers should look for another (potentially) better product.

@linuxninja If you dont want teams rewriting YOUR .desktop file, again, bitch at MS for putting such shitty practise in place. Or make it read only, and maybe add immunitable flag on it.

linuxninja commented on 2022-02-27 19:10 (UTC)

IMHO, adding —no-sandbox is the right thing to do for this version, as not running an up-to-date Arch install is not supported. This package should support a newly installed Arch Linux. If it doesn’t then this package is broken. Adding the flag makes this package not broken. Do this at least until there is a version update for Teams that resolves the issue, then you can remove the flag.

Sure, doesn’t work for every case, but does work for most cases. Add the flag. There shouldn’t be a requirement that everyone who installs this package has to come here to see all the drama and what they need to manually do to make it work when it could be already done and ‘just work’. Yes, there could be ‘security concerns’, but, this is the AUR. Making the change manually is the exact same ‘security concern’ as just having the package do it correctly in the first place.

BTW, Teams likes to create its own teams.desktop autostart file which DOESN’T have the flag. That’s a real PITA.

ogarcia commented on 2022-02-27 10:49 (UTC) (edited on 2022-04-07 07:42 (UTC) by ogarcia)

Teams (1.4.00.26453) is now not compatible with glibc 2.35. It is upstream problem (aka Microsoft has to fix it/update). Here are the workarounds, which can be unstable or insecure.

For all the people who are requesting to add the —disable-seccomp-filter-sandbox or —no-sandbox option to the package, please note that we do not do it because there are people who do not have that need (for example those who have not yet updated the system).

Anyway, if you want to avoid having to type the command with the —disable-seccomp-filter-sandbox option every time you want to start Teams you can execute the following lines.

mkdir -p "$/applications" cp -a "/usr/share/applications/teams.desktop" \ "$/applications/teams.desktop" sed -i -e 's,teams %U,teams --disable-seccomp-filter-sandbox %U,' \ "$/applications/teams.desktop" 

What this does line by line is:

1. Make sure that the applications directory exists in your XDG_DATA_HOME.
2. Copy the teams.desktop file to the applications directory of your XDG_DATA_HOME.
3. Modify this file to add the —disable-seccomp-filter-sandbox option.

This way you will have a modified .desktop file that will allow you to start Teams with the added option without touching the system files (and without root permissions).

To do it with —no-sandbox (if don’t work with —disable-seccomp-filter-sandbox ):

mkdir -p "$/applications" cp -a "/usr/share/applications/teams.desktop" \ "$/applications/teams.desktop" sed -i -e 's,teams %U,teams --no-sandbox %U,' \ "$/applications/teams.desktop" 

If you have Teams to start automatically at startup you must also run this:

sed -i -e 's,teams %U,teams --disable-seccomp-filter-sandbox %U,' \ "$/autostart/teams.desktop" 

Or if you need do it with —no-sandbox :

sed -i -e 's,teams %U,teams --no-sandbox %U,' \ "$/autostart/teams.desktop" 

In the future, when Microsoft gets wise and fixes the bug you will simply be able to delete the desktop files from your home:

rm "$/applications/teams.desktop" rm "$/autostart/teams.desktop" 

dmstocking commented on 2022-02-23 20:27 (UTC)

I also had to add —disable-seccomp-filter-sandbox to fix the issue where teams would just launch and there would be nothing but a white box. The logs showed a rendering process crashed.

dr4Ke commented on 2022-02-23 09:32 (UTC)

Adding —disable-seccomp-filter-sandbox is sufficient to fix this issue. I don’t know what the security implications are.

I used a custom teams.desktop file to add this option.

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник