Package Details: teams

Git Clone URL: (read-only, click to copy)
Package Base: teams
Description: Microsoft Teams for Linux is your chat-centered workspace in Office 365
Upstream URL:
Licenses: custom
Conflicts: ms-teams
Replaces: ms-teams
Submitter: ogarcia
Maintainer: ogarcia (jvybihal)
Last Packager: ogarcia
Votes: 310
Popularity: 17.62
First Submitted: 2019-12-10 18:41 (UTC)
Last Updated: 2022-04-19 12:49 (UTC)

Pinned Comments

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 is higher than, or

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

crystal_pepsi commented on 2022-05-23 12:43 (UTC)

@mrechte Im unsure how I would do that - I dont use a display manager currently (i3). What i find confusing is that this bug only appeared recently.

iyanmv commented on 2022-05-23 12:14 (UTC)

Do you know if it is possible to run Teams as a native wayland app? I tried passing the flags --enable-features=UseOzonePlatform --ozone-platform=wayland, but it still uses XWayland (tested with extramaus)

mrechte commented on 2022-05-23 12:13 (UTC)

@crystal_pepsi have you tried with Xorg server ? I got similar problem with another tool (Bluejeans) which is not able to share the screen with Wayland (it used be to able to).

crystal_pepsi commented on 2022-05-23 09:00 (UTC) (edited on 2022-05-23 15:57 (UTC) by crystal_pepsi)

Is anyone else having a screen sharing issue? I cant share my screen, only powerpoint files. I haven't found a work around yet and wondered if anyone else has ran into this?

Firestar commented on 2022-05-12 04:43 (UTC)

ERROR: One or more files did not pass the validity check!

I changed b2sums to SKIP

jwhendy commented on 2022-04-29 19:49 (UTC)

Wow @Bosnia. While I didn't mind typing in fixed width font... it's much easier to parse normal chats and programming now. Perhaps this should be added as a dependency or optional dep?

Exanime commented on 2022-04-29 19:18 (UTC)

@Bosnia you are a genius...

Got it to work installing this AUR package

Bosnia commented on 2022-04-29 17:07 (UTC)

It looks like the segoe-ui is required to fix the font issues. I installed it using yay -S ttf-windows.

elisiariocouto commented on 2022-04-28 14:08 (UTC) (edited on 2022-04-28 14:08 (UTC) by elisiariocouto)

Did anyone found a fix for the font issue?

jwhendy commented on 2022-04-27 18:08 (UTC)

Finding still glitchy. I blurred the sensitive areas in these pics, but the gray overlays are real, and in the second pic I blurred the the left-most faces, but the furthest right one is as-is. When people start talking their pic disappears and it's just a glowing bluish blob.

I think this might be tied to resume from suspend, as upon launch things seem ok, but resuming not so much. I haven't paid close enough attention to know if just having it open all day also causes glitches.

I added a note to this effect at the MS Feedback portal as well, lest MS think this is definitely resolved. Not sure what others' experience has been on 1.5 though.

Exanime commented on 2022-04-26 13:32 (UTC)

@bradwood @jwhendy

If I play with the system font, I get it to behave for a bit... but notice how the chat windows appear OK while the actual chat listing still show the problem... I believe the "problem" font is hack (a default for KDE, which is what I have) and it is not been overridden like the rest of the system

bradwood commented on 2022-04-26 12:45 (UTC)

@Exanime -- my browser has the same problem also (Brave) but, like you, it's only MSTeams that has the problem.

Exanime commented on 2022-04-26 12:30 (UTC)

@jwhendy It does, my current system font is Fira. I tried changing it to DejaVu and notice it changing.

When I do change it, things improve at first view, but as I jump around chats and/or start typing I get this artifact again.

It affects this stand alone app as well as the web app in both Firefox and Chromium. This is the only affected app as far as I have noticed

@Bradwood - same here, I have removed the package (including any config files) and reinstalled it; changed system fonts a few times, played with GPU rendering... no change so far.

bradwood commented on 2022-04-26 11:17 (UTC)

@daminator -- I have the same in i3. When I use meta+q the window closes without a problem. I never click on the X button on the top right hand corner of the window anyway, but when I do, it doesn't close.

For me this is not a problem as, with i3, you are generally more keyboard-focused in any case.

bradwood commented on 2022-04-26 08:15 (UTC) (edited on 2022-04-26 08:22 (UTC) by bradwood)

@Exanime -- I have exactly the same problem -- doing my head in!

It's the same on teams-insiders...

jwhendy commented on 2022-04-25 20:12 (UTC)

@Exanime: Does it match your system font(s) by chance? Interestingly, teams just started using Hack in my chats, starting a few days ago. This is the system font I have defined via lxappearance. I was surprised to see that, but wonder if it's related to a different package update and not teams (happened before my update to 1.5).

Exanime commented on 2022-04-25 19:35 (UTC)

Anyone experiencing issues with font? Mine look way too spaced out (as if attempting center alignment) and the numbers have these gray fade effect that makes them hard to read.

It is not like the font has not been rendered properly though (as in cases where the fonts are broken, blurry or pixelated)

Here is a sample

daminator commented on 2022-04-25 10:01 (UTC) (edited on 2022-04-25 10:01 (UTC) by daminator)

I am experiencing issues with closing a teams window while using i3 (e.g. it won't close). This also happens for the teams-insiders packages. Does anyone else experience this?

randomnerd commented on 2022-04-19 16:27 (UTC)

Looks like it finally works.

mozo commented on 2022-04-19 09:36 (UTC)

Thank you jvybihal, mocolini :)

mocolini commented on 2022-04-19 09:21 (UTC)

@jvybihal just couse I wasn't aware about it! I apologize to all of you

jvybihal commented on 2022-04-19 09:14 (UTC)

Why not just install teams-insiders package? Why bother to ducktape it and spam comments? It was always available :O

mocolini commented on 2022-04-19 09:05 (UTC) (edited on 2022-04-19 09:08 (UTC) by mocolini)

@mozo for test purpose I've just modified the PKGBUILD this way:


-source=("${pkgname}_${ noextract=("${pkgname}_${pkgver}_amd64.deb")pkgver}_amd64.deb")


mozo commented on 2022-04-19 08:55 (UTC)

@mocolini And how we're supposed to install it? Will a simple file substition be enough?

mocolini commented on 2022-04-19 08:38 (UTC)

FYI teams-insiders_1.5.00.10453 seems work flowlessy (

Maybelline commented on 2022-04-18 15:55 (UTC) (edited on 2022-04-18 15:55 (UTC) by Maybelline)

Would it make sense to start a wiki page about Microsoft Teams or is it not a good practice for AUR packages? Like

@sandstorm I'm not expert on "good practice", but I think a wiki page is an excellent idea. I went in search of it when I couldn't get Teams to play nicely under Sway WM (and still can't, so I'm back in Gnome).

sandstorm commented on 2022-04-13 13:33 (UTC)

Would it make sense to start a wiki page about Microsoft Teams or is it not a good practice for AUR packages? Like

kemuzor commented on 2022-04-09 01:12 (UTC)

Is there a chance that we get a flawlessly working package for Teams soon?

alex.henrie commented on 2022-03-30 21:14 (UTC)

"we do not [add the --no-sandbox option] because there are people who do not have that need"

Keeping this package broken in the AUR is hurting far more people than it is helping.

luistp commented on 2022-03-30 09:37 (UTC) (edited on 2022-03-30 18:57 (UTC) by luistp)

The issue at the feedbackportal from Microsoft is at 820 votes, page 26 (two weeks ago it was at 425 votes, page 45, as per @vpotocek). Keep voting please... Is it our only hope?

Thank you.

merzo commented on 2022-03-28 11:51 (UTC)

Latest version of teams with latest update of ArchLinux started to blink screen between applications when I try to share screen. Is it a known issue?

viktarchemko commented on 2022-03-26 20:09 (UTC) (edited on 2022-03-26 20:15 (UTC) by viktarchemko)

I changed the command from the pinned comment to also solve the problem with joining online meetings

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

mozo commented on 2022-03-22 11:25 (UTC)

@pcfreak You can try this:

pcfreak commented on 2022-03-22 11:19 (UTC)

It seems, that with the current version it is not possible to join a teams meeting via URL. The website pops up and if I select to open the meeting with xdg-open teams gets the focus like doing something but joining the meeting is not happening.

mozo commented on 2022-03-14 10:31 (UTC)


vpotocek commented on 2022-03-14 10:12 (UTC) (edited on 2022-03-14 10:12 (UTC) by vpotocek)

Everyone who can please cast a vote at This is only a login and one click away and takes mere seconds. At the time of writing this, the issue is at 425 votes, putting it at page 49 (!!!) in the feedback list. There is ZERO chance Microsoft is going to even notice if it's busy implementing useless clap like DTMF tones (490), GIF avatars (680) or the poop emoji (940 votes). The important things seem to start upwards of 1000 votes and it should not be too far away to get in their company if we really try.

ogarcia commented on 2022-03-09 07:45 (UTC)

@jorge_barroso please, before posting read pinned comments. Say that is a newer version than current one (at moment of write this comment is FUD.

But if you doubt about latest version of Teams, you can go to Microsoft Teams download page and download the lastest DEB or RPM version. What version download?

matt17br commented on 2022-03-09 01:15 (UTC)

@jorge_barroso, as per @ogarcia's pinned comments, "WARNING: PLEASE STOP FLAG THIS PACKAGE AS OUT OF DATE teams_1.4.00.7556_amd64.deb IS LOWER THAN CURRENT VERSION"

Microsoft adopts a misleading versioning scheme.

mozo commented on 2022-03-09 00:19 (UTC)

@jorge_barroso What are these quality of life improvements? Thanks for the patch!

jorge_barroso commented on 2022-03-08 23:29 (UTC) (edited on 2022-03-08 23:30 (UTC) by jorge_barroso)

The newest version seems to include a couple of quality of life improvements, plus fixes it for the latest version of either wayland on electron (don't know which one, but the current one stopped working for me after a recent update and the latest fixes it)

Here's a simple patch for it, nothing too crazy, just sha256 and version number updated:

--- PKGBUILD_old 2022-03-08 17:18:13.507578928 -0600
+++ PKGBUILD    2022-03-08 17:21:18.983481126 -0600
@@ -1,7 +1,7 @@
 # Maintainer: "Amhairghin" Oscar Garcia Amor (

 pkgdesc="Microsoft Teams for Linux is your chat-centered workspace in Office 365"
@@ -14,7 +14,7 @@

 package() {
   bsdtar -O -xf "${pkgname}_${pkgver}_amd64.deb" data.tar.xz | bsdtar -C "${pkgdir}" -xJf -

TwoD commented on 2022-03-08 13:48 (UTC)

If you put any switches like --disable-seccomp-filter-sandbox or --no-sandbox in your [custom] Teams desktop file, make sure they go after %U or clicking meeting links won't work. Known bug in Teams:

ogarcia commented on 2022-03-03 11:29 (UTC)

@jvybihal: I pick some of your summary to add in the pinned comment ;-)

snack commented on 2022-03-03 10:55 (UTC)

@jvybihal: thanks for the resume. Adding the --disable-seccomp-filter-sandbox option makes everything work again. Web browser is not a viable alternative for me, I use Firefox and voice calls don't work with it. I'll try to report to Microsoft as well.

jvybihal commented on 2022-03-03 10:51 (UTC)

@snack in short: teams is now not compatible with glibc 2.35. It is upstream problem (aka Microsoft has to fix it/update). There are workarounds, which can be unstable or insecure. If possible use webbrowser version instead of an app. And ofcourse, report to Microsoft. If only few people will report it, it will always be low priority for them (at least that is my perception).

To everyone: please keep the comments helpful, kinds and informative. If your message does not bring anything constructive to the table, maybe don't post it? Thanks.

snack commented on 2022-03-03 10:43 (UTC)

@sarvasana I did, and honestly I did not understand if it is related at all with my problem. The pinned comment does not state what's about, and I got lost going back through the endless discussion. So I'm sorry to bother people who are up-to-date with the discussion, but I did my best. I'll go back again and try to sort the endless discussion out. Thanks for your contribution.

sarvasana commented on 2022-03-03 10:36 (UTC) (edited on 2022-03-03 10:37 (UTC) by sarvasana)


Maybe you can read the endless discussion here before posting your question?
There is even a pinned message...

snack commented on 2022-03-03 10:33 (UTC)

I don't use teams often but today I tried to open it using the menu entry and it does not start anymore. The icon keeps appearing in the system tray and then disappearing, until it appears definitively but no window is visible. Right click and then Open does not produce any result.

It used to work up to a couple of weeks ago, not sure what I did in the meantime that might broke it (maybe updating Plasma desktop to 5.23?). Any KDE user (X11 session) experiencing the same? Any hint about how to investigate/solve? Thanks.

luistp commented on 2022-03-02 08:20 (UTC) (edited on 2022-03-02 12:50 (UTC) by luistp)

I can confirm that for me, on X11, --disable-seccomp-filter-sandbox works better than --no-sandbox. No sandbox presents a random behaviour in my system, allowing the application to start on only a fraction of the attempts.

nyanpasu64 commented on 2022-02-28 23:09 (UTC)

I don't use Teams, but betterdiscord-installer runs into a similar issue. There's a bit of technical detail at (in short, glibc 2.35 enables rseq which makes syscalls, and older Electron uses seccomp to block syscalls and SIGSYS the process making them). I'm not sure what the real fix is though, possibly

karabaja4 commented on 2022-02-28 14:08 (UTC) (edited on 2022-02-28 14:10 (UTC) by karabaja4)

I can also confirm that on X11. With --disable-seccomp-filter-sandbox teams is working exactly the same with glibc 2.35 as it worked with glibc 2.34 (calls, camera, screen sharing, chat).

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.

That's my 2 cents.

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 ( 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 "${XDG_DATA_HOME:-$HOME/.local/share}/applications"
cp -a "/usr/share/applications/teams.desktop" \
sed -i -e 's,teams %U,teams --disable-seccomp-filter-sandbox %U,' \

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 "${XDG_DATA_HOME:-$HOME/.local/share}/applications"
cp -a "/usr/share/applications/teams.desktop" \
sed -i -e 's,teams %U,teams --no-sandbox %U,' \

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,' \

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

sed -i -e 's,teams %U,teams --no-sandbox %U,' \

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 "${XDG_DATA_HOME:-$HOME/.local/share}/applications/teams.desktop"
rm "${XDG_CONFIG_HOME:-$HOME/.config}/autostart/teams.desktop"

Vote issue in upstream here:

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.

fireratio commented on 2022-02-22 05:44 (UTC)

Please don't suggest adding --no-sandbox permanently in the package. This should be an ephemeral workaround used with caution, as --no-sandbox itself carries many security risks.

bidulock commented on 2022-02-22 00:53 (UTC)

Please add the following line at the end of package():

sed -i -e 's,--disable.*sandbox,--no-sandbox,' "${pkgdir}/usr/bin/teams"

to add the --no-sandbox flag to the /usr/bin/teams invocation script.

Xuebit commented on 2022-02-21 18:37 (UTC)

The --no-sandbox flag worked for me. Just make sure you kill any non-working teams processes if you are still having issues.

Kitt3120 commented on 2022-02-21 10:55 (UTC) (edited on 2022-02-21 10:55 (UTC) by Kitt3120)

If you don't want to start teams from the terminal all the time, there is no need for a custom AUR package. Just open your favorite editor on /usr/share/applications/teams.desktop or teams-insiders.desktop and edit the "Exec" line in "[Desktop Entry]" to contain the argument. If you're using KDE Plasma and have teams in autostart, also edit ~/.config/autostart/teams.desktop or teams-insiders.desktop or just remove the autostart entry through GUI settings and add it again.

Also make sure to revert and test again after the teams package has been updated.

alexleach commented on 2022-02-21 10:45 (UTC)

Is it worth someone releasing a new AUR version, with --no-sandbox added to the command line options in /usr/bin/teams? Would save us from having to launch teams from the terminal each time, and would allow teams to start on login. I'm going to do that on my local machine anyway...

TJM commented on 2022-02-21 08:28 (UTC)

Teams work well with --no-sandbox. However, unable to run and terminated with SIGILL or SIGSYS without --no-sandbox. Strange.

TJM commented on 2022-02-21 08:28 (UTC)

Teams work well with --no-sandbox. However, unable to run and terminated with SIGILL or SIGSYS without --no-sandbox. Strange.

thewhitemike commented on 2022-02-21 07:43 (UTC)

@deep_thought Try to launch teams from your terminal whit this commande teams --no-sandbox.

deep_thought commented on 2022-02-21 07:31 (UTC)

Does teams need a specific nodejs version to run? I have updated nodejs to 17 and now, teams fails to start.

Rin4th commented on 2022-02-21 00:51 (UTC)

for me teams --no-sandbox works properly, but I don't know why I can't login in my collage account

janp commented on 2022-02-18 12:05 (UTC)

Me too.. teams --no-sandbox works for me both inside a virtual machine and on a real machine with discrete gpu (AMD radeon) Thank you

galacta_dm commented on 2022-02-18 04:00 (UTC)

I have the same problem. When I launch the teams app, only a small icon appears on notification panel and it's blinking.

I use primus(Intel + nvidia) and "teams --no-sandbox" works for only Intel graphics, not for discrete GPU.

sandstorm commented on 2022-02-17 16:18 (UTC)

I use Wayland, teams --no-sandbox works for me.

bred commented on 2022-02-17 13:09 (UTC)

teams --no-sandbox works for me


ogarcia commented on 2022-02-17 12:40 (UTC)

Maybe teams --no-sandbox only work with X11 and not in Wayland. Anyway this is a upstream bug.

Please, if you can, vote the issue:

AUR_user commented on 2022-02-17 10:49 (UTC) (edited on 2022-02-17 10:50 (UTC) by AUR_user)

The teams --no-sandbox doesn't work for me either. I'm also forced to use teams, company related. The downgrade of all gcc and glibc related packages worked for now. I checked on the Microsoft feedback portal and found a related topic.

Maybe we get the topic pushed a bit further up, since this is quite a major issue.

harroxelas commented on 2022-02-17 10:33 (UTC)

teams --no-sandbox worked!

bred commented on 2022-02-17 10:23 (UTC) (edited on 2022-02-17 10:25 (UTC) by bred)

Since today I have this error:

Error while parsing hooks JSON. Error: "ENOENT: no such file or directory, open '/home/myhome/.config/Microsoft/Microsoft Teams/hooks.json'"
(node:27675) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:27675) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ecsSettingsUpdated listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
(node:27675) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 appInitialized listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
[27675:0217/] GPU process isn't usable. Goodbye.
Server response: 
Server response: 
fish: Job 1, '/usr/share/teams/teams' terminated by signal SIGILL (Illegal instruction)

DarkXylese commented on 2022-02-17 09:38 (UTC) (edited on 2022-02-17 09:41 (UTC) by DarkXylese)

teams --no-sandbox doesn't work for me properly. Sure the teams app launches now, but I get these errors, no text loads and I can't join any meeting sadly: {{::middleMessagesStripe.emptyStateTitle}} {{::middleMessagesStripe.emptyStateMessage}}

My eternal hate for MS continues. Switching to Linux doesn't even help with truly getting away since my job requires ms teams..
Gonna have to stay on the browser version for the time being I guess...

alex.henrie commented on 2022-02-17 00:46 (UTC)

@landaro teams --no-sandbox worked for me. Thanks for the tip!

mimhof commented on 2022-02-16 21:09 (UTC)

I found this alternative solution which works for me:

landaro commented on 2022-02-16 17:04 (UTC)

maybe relevant: the AUR version of RStudio is also running on electron, is also currently facing a whitescreen on start-up issue, which can also be worked around with the --no-sandbox flag. The discussion over there is suspecting issues with qt5. Cross-linking in case there is a common root cause

HyperFrame commented on 2022-02-16 09:13 (UTC)

@gavinhungry thank you, it works fine. Would prefere to not install flatpak.

attila123 commented on 2022-02-16 07:36 (UTC)

@gavinhungry you are right, I upgraded glibc. Hopefully I can just temporarily downgrade those 4 packages before next time I need to restart Teams. Sure the flatpak way is much cleaner. Maybe I will switch to that if needed.

kishvanchee commented on 2022-02-16 07:31 (UTC)

For the current version (, you can pass the --no-sandbox argument to teams

Can confirm, this works for me as well. @ng0177 I faced the same problem as you did.

ogghi commented on 2022-02-16 07:21 (UTC)

@ng0177 I stopped looking at solving things here, just using the flatpak version at this point...

ng0177 commented on 2022-02-16 07:07 (UTC) (edited on 2022-02-16 07:07 (UTC) by ng0177)

It gets stuck on startup purple "Microsoft Team - Preview" window - since about two days... Any ideas?

gavinhungry commented on 2022-02-15 23:15 (UTC)


I checked, and the enableProcessIntegrityLevel workaround only works for and (and probably earlier versions, as well).

For the current version (, you can pass the --no-sandbox argument to teams (which is part of what enableProcessIntegrityLevel is doing under the hood in any case). See for more information.

Flatpak is still probably the best workaround for most people. Much, much better than sticking to an out-of-date glibc.

attila123 commented on 2022-02-15 22:08 (UTC)

After the below mentioned package downgrades I wanted to test things after rebooting, but could not log in to Cinnamon (actually I could log in to XFCE). But I wanted to use Cinnamon, so I upgraded stuff again (can be done in console) (sudo pacman -Su), then I could log in to Cinnamon. Then I started whatever apps I wanted and downgraded the libs again (see below) to start Teams. Unless sg is not working I stay with the downgraded libs for the moment. Otherwise I will upgrade and downgrade as needed. I am OK with this as I reboot maybe per 1-2 weeks, and using just suspend when I am not working.

flatpak - will check if all else fails.

pezz commented on 2022-02-15 21:52 (UTC)

I feel flatpak is the best workaround here, it's running as good as this version imo. teams-nativefier doesn't work with the suggested useragent tweak either.

attila123 commented on 2022-02-15 21:37 (UTC)

@gavinhungry thanks, but creating the hooks.json did not prevent the white box, it just prevented the error message about hooks.json in the startup log. I needed to downgrade those libs.

@baggar11, thank you very much, those downgrades fixed it for me :)

sudo pacman -U glibc-2.33-5-x86_64.pkg.tar.zst gcc-libs-11.1.0-3-x86_64.pkg.tar.zst binutils-2.36.1-3-x86_64.pkg.tar.zst gcc-11.1.0-3-x86_64.pkg.tar.zst

@Ravenman, thanks for the info, I did the manual downgrade before I could read your comment, but will save this in my notes.

baggar11 commented on 2022-02-15 18:43 (UTC) (edited on 2022-02-15 18:43 (UTC) by baggar11)

Downgraded the following fixed the issue for me.

[2022-02-15T10:34:21-0800] [ALPM] downgraded glibc (2.35-2 -> 2.33-5)

[2022-02-15T10:38:02-0800] [ALPM] downgraded gcc-libs (11.2.0-3 -> 11.1.0-3)

[2022-02-15T10:38:03-0800] [ALPM] downgraded binutils (2.38-3 -> 2.36.1-3)

[2022-02-15T10:38:03-0800] [ALPM] downgraded gcc (11.2.0-3 -> 11.1.0-3)

gavinhungry commented on 2022-02-15 18:03 (UTC) (edited on 2022-02-15 22:46 (UTC) by gavinhungry)

I've only tested this on, but you can work around the blank splash screen crash by creating the following file:

${XDG_CONFIG_HOME}/Microsoft/Microsoft Teams/hooks.json

With the following content:

{ "enableProcessIntegrityLevel": false }

mephinet commented on 2022-02-15 15:43 (UTC)

Also seeing the "white screen issue" after updating today. I removed .config/Microsoft and .config/Microsoft Teams - Preview, and started Teams again - this is the log file:

This is the output of today's paclog - so the issue must be caused by the update of one of these packages:

ogghi commented on 2022-02-15 13:50 (UTC)

I feel the flatpak Teams being faster now xD Did you disable GPU hardware acceleration and turned off animations?

Veltarn commented on 2022-02-15 13:19 (UTC)

@ogghi you're not alone: i7 8th gen + 16GB of Ram and Teams flatpak is laggy on the other side: AUR teams is perfectly fine

ogghi commented on 2022-02-15 13:00 (UTC)

Also on installed version the performance is not good...flatpack? Might check out. Core i5 and 16GB RAM...but also with higher spec desktop, it's always laggy, but this might just be Teams itself...

euzao commented on 2022-02-15 12:33 (UTC)

Yes, I had the same issue with that white screen. Now I am running MS Teams on Flatpak and it is working flawlessly.

ArthurBorsboom commented on 2022-02-15 12:32 (UTC)

As a workaround I use the web version.

ogghi commented on 2022-02-15 11:43 (UTC)

@attila123 Fun fact, I just encountered the same after clearing those folders. Before that I was trying teams-for-linux, which changed some nodeJS, I reverted changes, but still this white box capturing all input! Will see, maybe nodeJS configs eventually?

attila123 commented on 2022-02-15 11:33 (UTC) (edited on 2022-02-15 11:34 (UTC) by attila123)

Hi, anyone else having this issue? Teams stopped working for me today. Maybe due to some of its dependencies got updated? Just guessing (I did update Arch recently). When I try to start it, it just displays a white box (I guess it would be the login screen), and grabs all the keyboard input. So I cannot use keyboard anywhere else, including terminal. I need to right click the Teams icon in the tray and exit it from there. I also tried to delete its files, hope this is the right place: 'rm -rf ~/.config/Microsoft/Microsoft\ Teams'. Did not help. I am on Cinnamon if that matters.

originalsouth commented on 2022-02-15 09:59 (UTC)

As a (temporary) work around -- given you do not want to downgrade -- you can switch to (you will need to change the user agent in build script yourself, for me "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.80 Safari/537.36" works).

arvids commented on 2022-02-15 09:51 (UTC)

after update today stopped to work for me too, as expected - rebuilding does not help

Veltarn commented on 2022-02-15 09:48 (UTC)

I can confirm, I updated to glibc 2.35 and teams has ceased to work.

linuxninja commented on 2022-02-15 09:46 (UTC) (edited on 2022-02-15 09:50 (UTC) by linuxninja)

Will not run on a system updated to glibc 2.35 I wouldn't recommend downgrading your glibc packages to glibc 2.33, as the rest of the system is going to be updating and relying on glibc 2.35. Microsoft is going to have to rebuild based on glibc 2.35, so for now, we're just going to have to use their web version.

We can't rebuild. We don't have the source. Teams is proprietary.

totsilence commented on 2022-02-15 08:50 (UTC)

@johnnybash, seems unlikely as this is a binary package

johnnybash commented on 2022-02-15 08:22 (UTC)

rebuilding the teams package after updating to the new toolchain packages (glibc, binutils, ...) should solve your problems!

knatter commented on 2022-02-15 08:16 (UTC)

teams works with the following downgrade

sudo pacman -U /var/cache/pacman/pkg/glibc-2.33-5-x86_64.pkg.tar.zst /var/cache/pacman/pkg/gcc-libs-11.1.0-3-x86_64.pkg.tar.zst /var/cache/pacman/pkg/gcc-11.1.0-3-x86_64.pkg.tar.zst /var/cache/pacman/pkg/binutils-2.36.1-3-x86_64.pkg.tar.zst /var/cache/pacman/pkg/libtool-2.4.6+42+gb88cebd5-16-x86_64.pkg.tar.zst /var/cache/pacman/pkg/elfutils-0.186-4-x86_64.pkg.tar.zst /var/cache/pacman/pkg/libelf-0.186-4-x86_64.pkg.tar.zst

simontunnat commented on 2022-02-15 07:29 (UTC) (edited on 2022-02-15 07:57 (UTC) by simontunnat)

Had the same problem as @sajran.

Downgrading the following packages helped for now: gcc-libs gcc binutils glibc libtool elfutils libelf

bcyran commented on 2022-02-15 06:55 (UTC) (edited on 2022-02-15 06:56 (UTC) by bcyran)

Seems to be broken by yesterday glibc update. Tray indicator shows up and disappears a few times. Sometimes small, empty, violet window pops up. Downgrading all packages from yesterday's bundle fixed the problem.

gorgdel commented on 2022-02-15 04:51 (UTC)

White screen pops up, doesn't allow sign in. Any solutions?

attila123 commented on 2022-02-05 09:32 (UTC) (edited on 2022-02-05 09:34 (UTC) by attila123)

Hi, for some time (weeks or months) colleagues complain when I try to share screen with this Teams app, that what I share (the video) is somehow "glitchy", somehow "jumping" (sorry, my English is limited) in some part of the time. The workaround is to share my screen from a browser (e.g. Chromium), then sharing works fine. Lenovo T470, LTS kernel, Cinnamon. Anyone else having this issue? Maybe some solution? I did not try to change eg desktop env. (always hoped that eventually it would be fixed by some update + workaround exists)

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 is higher than, or

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

vagelis commented on 2022-01-25 18:55 (UTC)

Yes, share works but I cannot give control to other user. Is there any woraround for this?

Fenrihr commented on 2022-01-25 18:31 (UTC) (edited on 2022-01-25 18:34 (UTC) by Fenrihr)

@chovy it works (*), but you will need X11 as display server to share screen (Wayland don't work). All other features have worked for me.

(*) Currently, I am using it in Manjaro 21.2.2 (kernel 5.15.16) with Gnome 41.3 + Display Server X11

jvybihal commented on 2022-01-25 17:58 (UTC)

@chovy please send all the feedback to Microsoft.

chovy commented on 2022-01-25 17:48 (UTC)

this seems to be some kind of limited beta preview which doesn't even work.

Alad commented on 2022-01-17 13:49 (UTC)

The replaces field serves no purpose for an AUR package; please replace it with provides.

vagelis commented on 2022-01-17 12:00 (UTC) (edited on 2022-01-17 12:01 (UTC) by vagelis)

Hi there. I've noticed that I cannot accept Control Requests. Notice is popping up but always greyed out or something. Is there any workaround? Thanx

Gnome 41.2, kernel 5.15.14-1-lts

Fenrihr commented on 2021-12-29 13:44 (UTC) (edited on 2021-12-29 13:50 (UTC) by Fenrihr)

Screen sharing doesn't work on Linux with Wayland ( teams - Manjaro 21.2.0 - Gnome 41.2 )


  1. switch to X11 for the defaults display server
  2. Using desktop as fake webcam on Linux (more details)
  3. Use the browser version of Teams ( with Chromium

iggypop commented on 2021-12-04 17:35 (UTC) (edited on 2021-12-04 17:41 (UTC) by iggypop)

@Numero: same problem at my side. For me downgrading 'soundtouch' to version soundtouch-2.3.0-1 worked for me as work-around.

Numero commented on 2021-11-24 17:20 (UTC)

Using teams to join a call, video (with external USB webcam) worked fine both ways, but no one could hear me (Yamaha Audiogram 6 USB audio interface). I could hear them over the same interface, and other apps (specifically Audacity) can get audio input over the same interface. The mic VU meter in settings pane in the call wouldn't move.

dnnis commented on 2021-11-19 12:18 (UTC)

Kernel 5.14.16-arch1-1, app does not seem to start for quite some time now (some weeks at least). Does anyone else face the same problem?

japhir commented on 2021-11-19 11:40 (UTC)

I've read somewhere on Reddit that people switched to using microsoft edge and running teams from there. Then basically using edge for everything work-related, like online office etc. I've also adapted this workflow, and it works BETTER than their native app for me: I can look at the gallery view with >4 video feeds at the same time and I can share tabs in edge.

thraizz commented on 2021-11-19 11:37 (UTC)

If you cannot get your video devices to work with this official binary, try the teams-for-linux AUR package. My external webcam is only recognized there!

TheBill2001 commented on 2021-11-06 02:57 (UTC)

Has anyone find a way to make Teams remember audio device setting with pipewire? I have to set the correct audio output every time I open the app.

pezz commented on 2021-10-15 23:20 (UTC) (edited on 2021-10-16 05:11 (UTC) by pezz)

Issues like "I can't share my screen" or "I can't accept calls" can't be solved by the AUR packager. You should try and get support elsewhere.

jefferson-lima commented on 2021-10-15 14:07 (UTC)

Since this week I'm unable to share my screen. The button that previously shared the screen now opens an empty share tray in the bottom of the screen.

emorozov commented on 2021-10-12 08:05 (UTC)

I'm unable to accept calls using latest release ( When I receive a call or initiate a call, the screen flashes, I hear rings, but teams doesn't react when I click on any of the buttons (to receive the call or hang up). :(

CodingCellist commented on 2021-10-07 08:27 (UTC)

@DAC324: In terms of using pipewire instead of PA I believe that's what the pipewire-pulse package is meant to help with.

Don't know about the "appropriate" thing, sorry.

DAC324 commented on 2021-10-07 08:18 (UTC)

@ luisalcarasr :

Some problems when Teams crashes during the start of a call may be related to an inappropriate installation of `pulseaudio`.

How can I check if my pulseaudio installation is "appropriate"? And, what can I do if I use pipewire instead of pulseaudio?

jwhendy commented on 2021-09-14 17:57 (UTC)

The latest update ( has major screen glitches for me. Another virtual desktop background appearing in teams, artifacts around people's heads, settings -> devices yielded a black popup once the webcam preview tried to kick in... I'm downgrading.

TheBill2001 commented on 2021-09-07 02:04 (UTC)

This app seems to fail to load powerpoint live feature. However, teams-for-linux works.

flamehazelinux commented on 2021-09-01 14:36 (UTC)

I did a fresh installation of this and it's givin

This project will start, allow me to log in, but then report "Error code - online_check_failed: exceeded retry attempts Failed to connect to settings endpoint"

Quickly Googling, I've done the tasks of making sure the time is synced, etc. This problem still persists. I am able to log into Teams through Firefox, but I require the feature of sharing my screen.

As recommended below, I did try teams-for-linux, and I just get a white screen on that application. It does not even get to the login screen.

wget commented on 2021-08-29 17:32 (UTC)

Hello everyone,

For those of you finding this thread and being on Arch as well, if you do experience an issue with OBS Virtual Webcam and the latter appears as a black screen under teams, just reduce the Output (Scaled) Resolution to 720p in the OBS settings.

gudwin commented on 2021-08-24 15:02 (UTC)

For me, since the last upgrade, when I start teams, the only thing I see is a white box, completely inoperant. Apparently, the app starts (I can see some rendering), and then this white box is rendered on top of it, and I can neither close it. Completely useless.

Fortunately, I can close the app by using the small icon in the taskbar, but this is all I can do with this app. I had to uninstall it and install the AUR teams-for-linux package instead, which is unofficial, but at least works. Ah .. I can also open the app log, and I noticed I have a very huge log. Maybe I have some old configuration files somewhere, which might be causing this strange behavior (white box), but I was unable to discover where it is.

freebench commented on 2021-08-19 09:07 (UTC)

The only issue for me is that after a restart it doesn't save audio settings, what mic was in use last time. So I have to set it up before the call each time. Has anyone got solution to this ? PS. it is the heaviest app on my machine :)

karabaja4 commented on 2021-07-21 22:46 (UTC) (edited on 2021-07-21 23:53 (UTC) by karabaja4)

@luisalcarasr, thanks! I don't use pulseaudio, but running Teams with apulse fixes the crash when joining the meeting.

EDIT: Unfortunately, running Teams with apulse breaks my microphone. Back to I suppose.

EDIT2: However! After inspecting what exactly /usr/bin/teams does, I digged out a command that should keep apulse running together with Teams in foreground. This seems to work:

/usr/bin/apulse /usr/share/teams/teams --disable-namespace-sandbox --disable-setuid-sandbox 

My microphone is recognized in and it no longer crashes when joining a meeting. Yay!

luisalcarasr commented on 2021-07-19 14:31 (UTC) (edited on 2021-07-19 14:32 (UTC) by luisalcarasr)

Some problems when Teams crashes during the start of a call may be related to an inappropriate installation of pulseaudio.

kulak commented on 2021-07-09 17:57 (UTC)

Default Downloads location is $HOME. to change it install

pacman -S xdg-user-dirs

Set DOWNLOAD to your directory of choice:

xdg-user-dirs-update --set DOWNLOAD $HOME/Downloads/

zelimir commented on 2021-06-17 19:40 (UTC)

It looks like they fix the DEB link.

schokotets commented on 2021-06-17 14:26 (UTC) (edited on 2021-06-17 14:27 (UTC) by schokotets)

This is the PKBUILD of an rpm-based version you can try while the debian one is broken (modified from this packages' original PKGBUILD and lacking license).

pkgdesc="Microsoft Teams for Linux is your chat-centered workspace in Office 365"
depends=("gtk3" "libxss" "alsa-lib" "libxtst" "libsecret" "nss" "glibc>=2.28-4")
optdepends=("libappindicator-gtk3: Systray indicator support"
            "org.freedesktop.secrets: Keyring password store support")
package() {
  rpm2cpio "${pkgname}-${pkgver}-${pkgrel}.x86_64.rpm" | gunzip - | (cd "${pkgdir}" && cpio -idum --quiet)

  # Permissions fix
  find "${pkgdir}" -type d -exec chmod 755 {} \;

jvybihal commented on 2021-06-17 13:09 (UTC)

If updated version does not work, just downgrade back to working version. Making more packages makes no sense. And to everyone, I would suggest to go and pressure Microsoft to fix their actual shit. Comments about something not working in user-created package threads are just unnecessary clutter imho. If it is not packaging problem, no one will actually respond to that.

norg commented on 2021-06-17 13:01 (UTC)

I see issues with the 1.4.00.x branch on several machines with webcam and audio sometimes working, sometimes not. The interesting thing is that some folks have issues with the 1.4.00.x branch, some with the 1.3.00.x branch. But all did narrow it down to teams, since Zoom, Slack and others work fine.

Would it make sense to provide a teams-legacy or teams-1300 AUR package or should we just recommend the downgrade in such cases?

zelimir commented on 2021-06-17 07:49 (UTC)

@ogarcia Yep, flatpak version also can't be installed (same link is source). But .rpm version is available.

ogarcia commented on 2021-06-17 07:14 (UTC)

@zelimir Microsoft broke his own mirror (seems that they delete pool directory), the download fails in Teams page too.

zelimir commented on 2021-06-17 07:00 (UTC)

It looks like the link to the .deb file is down.

sarvasana commented on 2021-06-15 18:41 (UTC)

I am on Gnome 40 Xorg and on my machine it does not crash.

However, the tenant switching does not work yet. Weird thing is that MS did fix this issue on Android somehow.

karabaja4 commented on 2021-06-15 13:21 (UTC)

It seems that crashes for some people when joining a meeting, but not for others.

If someone figures out the cause, don't be shy to share :)

madeinnz commented on 2021-06-14 20:58 (UTC) also crashes for me every time I join a meeting. It also hangs when hanging up a call.

XTREEMRAGE commented on 2021-06-13 18:24 (UTC) (edited on 2021-06-13 18:26 (UTC) by XTREEMRAGE)

@DAC324 Well with firefox and curl (terminal) I can download it and it's pretty fast for me, but when I try to update this package, I get this error:

curl: (22) The requested URL returned error: 416
==> ERROR: Failure while downloading
Error: Failed to build teams

So it seems something is wrong with this package, I get a HTTP code error 416 as a return. I will try to remove it first and reinstall it.

=== Edit

Well that didn't work... can't reinstall it because of the error :(

DAC324 commented on 2021-06-11 13:51 (UTC)

@XTREEMRAGE: The download server is very slow. I also had to try several times, and when it then started downloading, it was at ~200 kB/s only.

XTREEMRAGE commented on 2021-06-11 09:32 (UTC)

Hmm I can't update to this version, it can't download the deb file:

curl: (22) The requested URL returned error: 416
==> ERROR: Failure while downloading
Error: Failed to build teams

Via firefox and curl (terminal) I can download it... See http code above

trashcoder commented on 2021-06-10 10:56 (UTC) (edited on 2021-06-10 10:57 (UTC) by trashcoder) Account-switching still not working: When switching to different account, it switches for a second and then reverts to the default account.

count_zero commented on 2021-06-09 10:19 (UTC)

So far no major problems under Manjaro with KDE. However, I have noticed that the CPU load has decreased considerably.

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) crashes for me every time I join a meeting. I've reverted to

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 being released.

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

There is an update to the latest version ( Would be nice if someone can update it. tx.

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.

MorningWood commented on 2021-05-31 16:22 (UTC) (edited on 2021-05-31 16:22 (UTC) by MorningWood)

Does anyone know how to get past the "you haven't signed up for Teams" "welcome" screen? I am signed up for Teams and have signed up again since getting this screen but keep getting it on Linux. In the comments left by others I've noticed that I'm not the only one.

Just curious if there's a workaround for this issue while still being able to retain this app. The Windows version installer straight up refuses to start so Wine is out as well. Would prefer not to run the web app (not Firefox compatible) or virtualization.

code_xpert commented on 2021-05-30 17:11 (UTC)

Guys, I have a serious problem. When I make a test call with that "Echo" thing, I sound just fine. Whichever call I join, though (that is of course not the "Echo" thing), no one can hear me. It works for 5-10 seconds at the start sometimes, then it doesn't work at all. Even the app says that my microphone doesn't work. It has been driving me crazy that it happens EVERY SINGLE TIME. Please help me, I really need Teams to work.

sarvasana commented on 2021-05-19 13:05 (UTC)

@easylee Only tip I can give you is to make sure you have selected the correct inputs/outputs before starting teams. Otherwise it will most likely not pick up correctly.

@ogarcia I did not know. Let's hope it will be better.

ogarcia commented on 2021-05-19 11:38 (UTC)

@sarvasana bad news, but Edge WebView2 is the same that Electron but with other name, both are based in same engine Blink. The only difference is that Edge WebView2 based applications will be smallest because will use Edge shared libraries. In Linux we could do the same with electron if Microsoft opened the Teams source code, but I doubt we'll ever see that.

erickochen commented on 2021-05-19 09:04 (UTC)

Thanks for that!

If anyone has any solutions for the issues with audio feel free to share :) I'd really appreciate it.

sarvasana commented on 2021-05-19 08:52 (UTC) (edited on 2021-05-19 08:52 (UTC) by sarvasana)

They mention Windows 10 only, but as it is web-based, it will most likely work on any platform.

Codename: Maglev.

erickochen commented on 2021-05-19 08:48 (UTC)

I simply need a solution for Teams meetings. A virtual machine is not a bad idea at all, at least to try.

Where does the rumor come from?

sarvasana commented on 2021-05-19 08:45 (UTC)

If that alone already pushes you back to Windows, then good luck! My advise is to just accept the limitations or virtualize windows for the time being.

Rumor has it MS is developing a new, non Electron based, version of MS Teams.

erickochen commented on 2021-05-19 08:36 (UTC)

I am about to give up and switch to Windows for my Teams meetings. Teams has been driving me insane on Linux.

For some reason the Linux app keeps on messing with the audio settings. Even restarting Teams after every single session is not always the solution.

I tried PulseAudio and PipeWire and I always have pavucontrol open hoping to resolve the problems.

Really, I am about to give up. I'm not even going to start discussing the other issues. Like screen sharing for example. Or lack of features...

MrMiyagi commented on 2021-05-07 14:45 (UTC)

Having the same issue with login loop on tenant switch. Figured out, the only way to access the tenant of an Organization I work with was to set homeTenantId to the TenantId I wanted to switch to in desktop-config.json.

Feakster commented on 2021-05-06 17:08 (UTC)

Is anyone else having issues where Teams keeps signing them out? I only have this problem on Linux.

usuariopolivalen commented on 2021-05-04 14:32 (UTC)

someons is having problems to join teams meetings like guest with url on linux?

ydallilar commented on 2021-05-04 09:59 (UTC)

Does anyone have problems joining to a Teams meeting today? The app keeps asking me to sign-up for Teams meeting. Then, I did. But, still complains. Unrelated but web app shows the same behavior. Final resort, I switched to my Windows VM. It worked there...

sarvasana commented on 2021-05-01 06:23 (UTC) (edited on 2021-05-01 06:23 (UTC) by sarvasana)

If you change your session from Wayland to x11, then screen sharing works again.
The same is true for slack-beta. There the screen sharing also only works on x11.

l0b0 commented on 2021-04-27 02:39 (UTC)

For people like myself struggling with desktop sharing, it still kinda works in Chromium. You can only share individual applications, though, not screens.

sarvasana commented on 2021-04-14 05:15 (UTC)

Yes, I have that too. It seems to be very difficult for Microsoft to keep Teams for Linux stable.

notixfy commented on 2021-04-13 21:20 (UTC) (edited on 2021-04-14 03:49 (UTC) by notixfy)

Anyone else unable to screenshare? I'm using gnome 3.38.4 and teams version and there is no option to share my screen. Everything else is working fine but there is no button for screensharing.

sarvasana commented on 2021-04-08 07:35 (UTC)

If you click "Sign-in options" on the O365 login screen and choose "Sign in to an organization" it lets you type in the domain name of the organization to sign in to.

From Reddit ^^

This will allow you to sign in to the tenant as a guest.

sarvasana commented on 2021-04-07 15:12 (UTC)

Somebody else already mentioned it on uservoice:

bmazotti commented on 2021-04-07 13:33 (UTC)

I and a colleague, were having the same problem switching tenants yesterday, but after some hours, refreshing the page on the browser, and the application resolved the problem. It seems like something server side was changed, and refreshing made it appear. While the problem was happening on Firefox and on this native app, the switch was being normally shown on Chromium. So you could try opening it on Chromium or Chrome.

sarvasana commented on 2021-04-07 13:12 (UTC) (edited on 2021-04-07 13:13 (UTC) by sarvasana)

For what it's worth:

Please vote.

jschuetzke commented on 2021-04-07 12:38 (UTC) (edited on 2021-04-07 13:55 (UTC) by jschuetzke)

@jaapcrezee @sarvasana Exactly the same for me, only my "default" tenant is working. When I try to change the tenant, I can see the teams within the other tenant shortly, before the MS-Teams window closes and the default tenant loads again.

The package was last updated more than a week ago and I'm fairly sure that I successfully changed tenants since updating it. So my guess is it's a server side issue but the Win10 version works fine...

sarvasana commented on 2021-04-07 12:23 (UTC) (edited on 2021-04-07 12:25 (UTC) by sarvasana)


I also tried older versions, but I have the issue with those versions also. (X11 and Wayland)

This leaves me thinking that it is either a dependency causing the issue or the server side of teams.

How can we raise this upstream?

jaapcrezee commented on 2021-04-07 12:20 (UTC)

Anybody else having issues switching between tenants? My account is a guest in several other tenants and I can no longer switch between tenants. It works on the browser, android and macos, but not on linux.

Having exactly the same issue(s).

sarvasana commented on 2021-04-07 12:18 (UTC) (edited on 2021-04-07 12:18 (UTC) by sarvasana)

Anybody else having issues switching between tenants?

My account is a guest in several other tenants and I can no longer switch between tenants.

It works on the browser, android and macos, but not on linux.

Wiichele commented on 2021-03-31 14:25 (UTC)

@Feakster Same. Now everything works just fine.

WhiteKnight commented on 2021-03-31 11:40 (UTC)

I can confirm, that KStatusNotifierItem is a problem not only with Teams. On two of my systems, it caused my gnome shell to restart regularly.

I use as an alternative without problems.

erickochen commented on 2021-03-31 11:36 (UTC)

@Feakster I think it is related to KStatusNotifierItem and happens whenever my status changes.

I've been using and noticed

I've now switched to and also reverted back to Wayland. So far so good.

Feakster commented on 2021-03-31 11:08 (UTC)

Hmm... the latest version ( appears not to crash Gnome anymore. It hasnt' so far, anyway.

erickochen commented on 2021-03-31 08:02 (UTC)

@Feakster @Wiichele Same issue. It seems to be related to

Wiichele commented on 2021-03-28 17:32 (UTC)

@Feakster Same issue here. Don't know if this is caused by GNOME or Teams.

Feakster commented on 2021-03-26 15:34 (UTC)

Is anyone having problems with this package on Gnome 3.38? For me, on Wayland it crashes the desktop. On X11, it causes the desktop to keep reloading.

erickochen commented on 2021-03-24 12:33 (UTC)

@antospo When running "xdpyinfo | grep -i render" I see it's already enabled. I verified my current session with loginctl show-session and it displays x11 and not wayland. Not sure what else I should change?

antospo commented on 2021-03-23 22:33 (UTC)

@easylee I'm using KDE and xorg, intel integrated graphics. It may actually be X-related; I don't think it will get fixed anytime soon sadly; switching to xrender is the only option at the moment.

erickochen commented on 2021-03-23 13:19 (UTC)

@bmazotti I appreciate your help! Sadly tho I do not have NVIDIA graphics.

bmazotti commented on 2021-03-23 13:17 (UTC)

@easylee and @antospo, I don't think I have this problem, so I don't know if this could help, but when starting simplescreenrecorder with a nvidia video card, it suggests disabling the "Allow Flipping" option to avoid glitches in the recordings. Perhaps this could help. This can be done in "NVIDIA X Server Settings".

erickochen commented on 2021-03-23 10:05 (UTC)

@antospo I'm using GNOME and X11. No NVIDIA graphics. Same issue then?

antospo commented on 2021-03-23 08:21 (UTC)

@easylee I've been experiencing the same issues. Moving from opengl composing to xrender fixed the issue for me. But it would be nice to have it working properly with opengl aswell.

erickochen commented on 2021-03-22 12:32 (UTC)

I've been experiencing issues sharing my desktop. People in the meeting describe it as a flickering image. Anyone else familiar with this behavior?

mwkuster commented on 2021-03-12 17:25 (UTC)

Magnificent - thank you @Master-2000 for this patch!

sarvasana commented on 2021-03-12 09:53 (UTC)

This again shows how awesome this community is. Thanks guys!

marcleb commented on 2021-03-12 09:42 (UTC)

Hi! I can't add a file to share in the Files directory. The file size is zero when added. Drag and drop doesn't work at all :-( Does anyone know how to fix it? Thx!

ogarcia commented on 2021-03-12 09:39 (UTC)

Thanks for the fix @Master-2000 !! Added to package.

daniel_chesters commented on 2021-03-12 09:21 (UTC)

It for me, thank you. This fix should be included with this package.

Master-2000 commented on 2021-03-12 08:31 (UTC)

The @ represent the incoming parameters (the clicked link) and the link was called in the wrong order. That's all. :)

sarvasana commented on 2021-03-12 08:29 (UTC)

@Master-2000 Thank you for this information. For educational purposes, would you mind writing a small description about what this does?

Master-2000 commented on 2021-03-12 08:12 (UTC)

you can solve the problem by editing /usr/bin/teams

change last line to: nohup "$TEAMS_PATH" "$@" --disable-namespace-sandbox --disable-setuid-sandbox > "$TEAMS_LOGS/teams-startup.log" 2>&1 &

sarvasana commented on 2021-03-11 14:46 (UTC) (edited on 2021-03-11 14:48 (UTC) by sarvasana)

Like crystal_pepsi mentions, this version is broken. ( Meeting links simply never open.

Would it be possible to create an additional teams package what will install the previous version?

I would be very happy to contribute to that.

Most likely it only involves taking the previous PKGBUILD file so that the version is downloaded and installed.

@crystal_pepsi: You probably know this, but for what it is worth. You can change the downloaded *.deb file and hash in your local PKGBUILD file and get a working version of teams.

crystal_pepsi commented on 2021-03-11 10:27 (UTC) (edited on 2021-03-11 10:29 (UTC) by crystal_pepsi)

Like others here, I have noticed that after updating to 1.4, teams can no longer handle links from browsers. I did find a workaround I wanted to share.

If you open the teams application, and navigate to the calendar tab, you can join meetings through invitations on your calendar (assuming you received an outlook calendar invitation containing the meeting link).

Obviously, this work around doesn't work if you do not have a meeting invitation in your outlook calendar.

je-vv commented on 2021-03-10 20:05 (UTC) (edited on 2021-03-10 20:05 (UTC) by je-vv)

Hi ! does anyone know how to start teams on tray, not opening a window at all, just remaining in tray?

mwkuster commented on 2021-03-10 19:13 (UTC)

Same observation as @daniel_chesters here - impossible to launch version via a link to a Teams meeting. Instead, the Teams windows flickers (if already open) or just opens (if not), but does not connect to the meeting.

This problem did not exist in 1.3.x

Here is what I see in the log in .config/Microsoft/Microsoft Teams/logs.txt:

... Wed Mar 10 2021 XZ:ZA:56 GMT+0100 (Central European Standard Time) <2575> -- info -- Running command line from source: handleCommandLine Wed Mar 10 2021 XZ:ZA:56 GMT+0100 (Central European Standard Time) <2575> -- info -- Command Line State - Unknown Wed Mar 10 2021 XZ:ZA:56 GMT+0100 (Central European Standard Time) <2575> -- info -- App subsequent launch - restoring existing app ...

resuni commented on 2021-03-09 15:19 (UTC)

Updating to the 1.4 package fixed my sign-in loop issue, but I had to clear the saved credentials first. Otherwise it would still loop.

daniel_chesters commented on 2021-03-09 10:23 (UTC) (edited on 2021-03-09 10:30 (UTC) by daniel_chesters)

Hi, when I update to version, neither with Firefox nor with Chromium nor with command-line, teams stop to handle the link. Teams only open and doesn't connect to meeting from the link. I have to stay in 1.3.xx until I found a solution for this issue.

EDIT: On Microsoft site, it stills a 1.3.xxxxx version for the Linux desktop packages.

nrbr commented on 2021-03-04 21:04 (UTC)

Like mortenn I've the same problem, also the link don't work on firefox (same sign in loop). Chromium was the solution.

BachoSeven commented on 2021-03-03 15:11 (UTC)

thanks for the suggestion, it is an institutional account from my university. However, I'm inclined to think that the lack of features is an issue with being on linux, see for instance

Cape commented on 2021-03-03 15:02 (UTC)

Are you using a free Teams account? Or is it a company managed account?

Because I've experienced similar simptoms some time ago with an older versione of the app. The IT teams did something via the Teams admin console which fixed it (though i dunno what it was...).

BachoSeven commented on 2021-03-03 14:28 (UTC)

@The-Arjdroid did you manage to switch to the Windows instance? I have tried with a plugin but it seems like I'm not able to spoof the website, since it still lacks the windows features such as grid with more than 4 faces.

The_Arjdroid commented on 2021-03-03 02:49 (UTC)

I think the latest problems are Microsoft purposely handicapping their Linux applications, both web app and desktop app... I will be trying out a User Agent Switcher on my chromium instance to switch to a Windows instance and see whether it improves the conditions of my connectivity.

resuni commented on 2021-03-02 18:04 (UTC) (edited on 2021-03-02 18:05 (UTC) by resuni)

I'm also having the same problem as mortenn, but I have the exact same problem when signing into Teams in Chrome and Vivaldi. Oddly enough I can get signed in when I use Firefox, but certain features such as screen sharing don't work.

Browser and desktop app both work on Windows. Neither browser nor desktop app work on Linux.

gloomy commented on 2021-03-02 12:15 (UTC)

I am having the same problem as mortenn.

mortenn commented on 2021-02-26 10:22 (UTC)

I am beginning to encounter login loops of "Stay signed in" to "We're sorry we've run into an issue" followed by immediately restarting and continuing on.

After some iterations of this it takes me to a blank screen with To open the web app, {{aTagStart}}change your browser settings{{aTagEnd}} to allow third-party cookies or {{aTagStart}}allow certain trusted domains{{aTagEnd}}.

Marcel_K commented on 2021-02-04 10:47 (UTC)

alesasnouski probably meant, but I don't know where they got that number from, as the current version for Linux is still

ogarcia commented on 2021-02-04 10:45 (UTC)

@alesasnouski in what world is higher version than Is the number 958 more high than 30857? Did I miss something? Do I need to back to school?

alesasnouski commented on 2021-02-04 10:05 (UTC)

Is it possible to update to teams ?

Marcel_K commented on 2021-01-26 17:46 (UTC)

This is still the newest version one can download, so this package is not out of date. Chances are that Microsoft delays implementing new features in the Linux version.

PassTheSoap commented on 2021-01-26 17:33 (UTC)

Being invited to breakout rooms doesn't seem to work, quick googling shows they were made generally available on the 9th of December 2020 (7 days after this package's last update). Is this package not up to date, or am I missing something? Thanks in advance (and thanks for maintaining it!!)

erenoglu commented on 2021-01-17 18:56 (UTC)

Hi @Hkyx, Microsoft is probably using an older electron which does not support screen sharing on Wayland (gnome default) using pipewire. So try to use Xorg session instead, then you'll see screen sharing.

Hkyx commented on 2020-12-24 18:43 (UTC)

sinxe last update onmanjaro with gnome or awesome, I can't share screen anymore, it doesn't show any monitor available to share.

szemy commented on 2020-12-17 12:54 (UTC)

In firejail since update: Log: dmesg:

snake2903 commented on 2020-12-10 12:21 (UTC)

Same problem here with guest join, it ask to login with Microsoft Account. I also tried all 1.3 version, tried to delete $HOME/.config/Microsoft/Microsoft Teams/ but noting works.

My current workaround is to use Chrome. When open in Chrome i can join meeting as guest. Camera and headphones is working. So i'll use Teams in Chrome until fix arrive.

ogarcia commented on 2020-12-08 16:28 (UTC)

@mksahin in this case the problem is located at upstream :-(

mksahin commented on 2020-12-08 16:00 (UTC)

@ogarcia: Tried your suggestion of renaming the mentioned directory. Doesn't fix the problem of not being able to join a meeting as a guest which started with this update (

ogarcia commented on 2020-12-08 14:57 (UTC)

For all people that fails start, first for all try to rename (or remove) the directory $HOME/.config/Microsoft/Microsoft Teams/ to start with a clean environment.

CodingCellist commented on 2020-12-08 09:54 (UTC)

In case people are still having trouble getting the latest release ( to work, I managed to get it running. However, I have some concerns about the method.

Looking at the $HOME/.config/Microsoft/Microsoft Teams/logs/teams-startup.log file after trying to launch Teams, revealed the following message:

[4706:1208/] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /usr/share/teams/chrome-sandbox is owned by root and has mode 4755.

Inspecting /usr/share/teams/chrome-sandbox the owner was root:root as required, but the permissions were 0755 (rwxr-xr-x) rather than 4755 (rwsr-xr-x). After changing this, Teams started successfully. HOWEVER, I am a bit cautious of this:

I am not familiar with the less common file permissions, but I found the following explanation online:

The setuid/setguid permissions are used to tell the system to run an executable as the owner with the owner’s permissions.

Be careful using setuid/setgid bits in permissions. If you incorrectly assign permissions to a file owned by root with the setuid/setgid bit set, then you can open your system to intrusion.

You can only assign the setuid/setgid bit by explicitly defining permissions. The character for the setuid/setguid bit is s.

If I understand this correctly, it means that changing the permissions allows chrome-sandbox to run as root, retaining root permissions (please correct me if I'm wrong). No other electron app I have installed has ever required this change, and I am definitely not too happy with Microsoft's being the only one that does require it. I think it is worth considering before doing the change.

If this is a serious concern to you, I would suggest either sticking with a previous release or using the open-source "teams-for-linux" package which (as far as I know) still works fine.

renkei commented on 2020-12-03 19:49 (UTC) (edited on 2020-12-06 11:26 (UTC) by renkei)

Update: Sorry, my fault. I didn't see that org.freedesktop.secrets via gnome-keyring or keepassxc was already specified as optional dependency. As a KDE user I switched from gnome-keyring to keepassxc, now. Login with my company account works as well, of course.

Starts without problems but I was not able to login with my company account. When I start teams in a terminal I get this:

(node:9086) UnhandledPromiseRejectionWarning: Error: The name org.freedesktop.secrets was not provided by any .service files

I found out that this can be solved by installing the package gnome-keyring. Now I can login. Maybe gnome-keyring should be added to the list of dependencies in the PKGBUILD. I'm using KDE.

szemy commented on 2020-12-03 14:18 (UTC)

Same here, does not start since last update.

zilvervos commented on 2020-12-03 12:28 (UTC) (edited on 2020-12-03 12:52 (UTC) by zilvervos)

Similar issue with teams as @jordanoff83 and @crackwolf8: when I tried to join a weekly weather briefing an hour ago, I couldn't join as normally via the link to that meeting. It now asks me to identify and that doesn't work as I am not part of any 'team' but just invited as a guest.

I solved the issue by installing microsoft-edge-dev-bin and using that to connect to the Teams meeting instead of the stand-alone teams app...

jordanoff83 commented on 2020-12-03 11:40 (UTC)

Well, downgraded to resolved the issue. On my other PC there's another problem - it asks me to login randomly, just the password, it remembers the email address. It starts normally and after a few seconds or when I click on a document it asks me for password again. There's no such problem on the PC I write this. Is it possible the reason for this to be that on the other PC the home partition is on a different physical disk? Absolutely identical OS - manjaro xfce, kernel 5.4.

CrackWolf8 commented on 2020-12-03 09:55 (UTC)

Having an issue where joining meetings anonymously is no longer working, it's requiring me to sign in. Downgrading to fixes the issue.

jordanoff83 commented on 2020-12-02 21:50 (UTC) (edited on 2020-12-03 07:36 (UTC) by jordanoff83)

@ogarcia Not starting at all after the last update. Even on terminal.

freebench commented on 2020-11-26 20:27 (UTC)

@theokonos all devices detected normally. however sometimes it doesn't save selected device, if you've got two webcams and using one specifically, it may not be saved, and similar with the other devs. solution to this is to check your devices before the call and don't change during the call.

theokonos commented on 2020-11-19 14:32 (UTC)

Did anyone else's audio/mic/camera device detection break recently? I tried the pulseaudio fixes below with no avail.

Ranguna commented on 2020-11-06 16:08 (UTC)

I downgraded pulseaudio to 13.99.2+7+g6101798c7-2 and it started working. I'm not sure if it was because I restarted pulseaudio after the downgrade or not.

japhir commented on 2020-10-15 09:00 (UTC) (edited on 2020-10-15 09:00 (UTC) by japhir)

It appears that resetting the pulseaudio config worked to get my mic working again!

mv ~/.config/pulse ~/.config/pulse-bak
pulseaudio --kill
pulseaudio --start

japhir commented on 2020-10-15 08:53 (UTC)

@cowai: background blur and replacing the background with an image have never worked for me.

cowai commented on 2020-10-14 10:35 (UTC)

Is background blur supposed to work with this?

erenoglu commented on 2020-10-14 07:28 (UTC)

@TornaxO7, you might have used sudo before and moved some of your files to root ownership. I dont have problem launching teams with a normal user. I suggest you run a "sudo chown -R your_username:your_group /home/your_username"

TornaxO7 commented on 2020-10-11 22:26 (UTC)

I'm getting this error message if I want to start teams:

zsh: permission denied: teams

Why do I have to use sudo for that?

erenoglu commented on 2020-10-08 08:42 (UTC)

So @Japhir, you're simply using this package for incoming video and audio/mic on Chromium. Too much hassle frankly. I use teams-for-linux electron app and it works fine,although shows one person at a time, which OK for me. Hope MS fixes this audio problem at least quickly, not sure why it's happening and why can't they open pulseaudio devices correctly.

japhir commented on 2020-10-05 14:18 (UTC)

For those who also experience issues with sound/mic input not working (using pulseaudio) and screensharing crashing the client immediately (on sway/wayland), here's the way I've been handling meetings with colleagues lately: - still use this app to connect to video, because it allows me to see multiple people simultaneously (with the web app/teams-for-linux you only see one person at a time) - connect to the meeting through chromium, disable incoming video, use this to connect to the mic and audio. If I have to screenshare, do so from here. I can only share X11 applications (like emacs) and chromium tabs (so I can open PDFs etc. in there if needed). I hope this helps some of you, I'm still waiting for Microsoft to fix this stuff and to give us access to the mosaic view with all attendant videos showing simultaneously!

NateR100 commented on 2020-09-25 18:22 (UTC)

With BSPWM and Teams (no compositor) when closing the window I get a permanent black bar over any other windows I open in its place - end up having to kill and relaunch X.

Anyone else?

javikore commented on 2020-09-23 15:45 (UTC) (edited on 2020-09-23 15:46 (UTC) by javikore)

Hi using i3wm on manjaro , get this info out of here and I'm walking ok for now :)

The symptoms would be a black screen with a red border. If you have this, can you try renaming this file (so it is not used) /usr/share/teams/resources/app.asar.unpacked/node_modules/slimcore/bin/rect-overlay

We are working on the solution on our side.

Shibumi commented on 2020-09-22 10:00 (UTC)

Is Screensharing working for anyone on Sway?

paragordius commented on 2020-09-21 14:51 (UTC)

I have to kill Pulseaudio before starting Teams to get it to actually send audio to my Scarlett 2i2. I wonder if it's just using ALSA?

teunissenstefan commented on 2020-09-18 11:39 (UTC)

@diefans not working for me with picom either.

Hkyx commented on 2020-09-17 18:45 (UTC)

@defians not working for my with picom or picom-tryone

diefans commented on 2020-09-16 21:50 (UTC)

the black screen with red border can be fixed by running a compositor like picom or compton. Has anybody an idea to reduce cpu usage of teams?

zilvervos commented on 2020-09-08 16:00 (UTC) (edited on 2020-09-08 16:00 (UTC) by zilvervos)

On Skype and Zoom, audio input works okay, but on MSTeams it seems I get no audio input from my mic. No good way to test the mic in MSTeams, so no clue how to properly test (and ideally solve) this.

A few months ago sound worked on MSTeams. Unfortunately a lot of organisations use MSTeams so I need it to run properly to be able to fully participate in online meetings.

zilvervos commented on 2020-09-08 16:00 (UTC)

On Skype and Zoom, audio input work okay, but on MSTeams it seems I get no audio input from my mic. No good way to test the mic in MSTeams, so no clue how to properly test (and ideally solve) this.

A few months ago sound worked on MSTeams. Unfortunately a lot of organisations use MSTeams so I need it to run properly to be able to fully participate in online meetings.

Hkyx commented on 2020-09-04 16:29 (UTC) (edited on 2020-09-04 16:29 (UTC) by Hkyx)

Since last update, when I share my screen, it show a black screen with red borders on the screens. The people don't see anything of what I share too. Worked correctly before last update but I did teams and arch/manjaro so which create that...

mbma commented on 2020-09-03 11:57 (UTC)

Anyone experiencing spontaneous crashes when trying to share your screen. Worked perfectly until very recently. (last week?). Tried the fix below to no avail.

Abh15h3k commented on 2020-09-01 07:08 (UTC)

there's no option to share system audio. what do i do?

wasperen commented on 2020-08-27 07:42 (UTC)

You may want to include this fix in the PKGBUILD:

Weebull commented on 2020-08-26 09:18 (UTC)

I'm now not able to connect to any of my pulseaudio devices. Has this happened to anyone else. I've done a full re-install, including deleting all my user config (.config/Microsoft).

fardenz commented on 2020-08-17 15:00 (UTC)

My friends are also experiencing the same flickering while I share screen. As reported by @LukasDoe and @L0rne Any fix known?

Also I can't try @L0rne temporal solution as I can't share just one application window, it is just allowing me to share the whole screen.

pinsl commented on 2020-08-14 13:36 (UTC)

I could not get this working without org.freedesktop.secrets installed. I could not press the ok button on the small credentials popup that shows up on first login. So It was stuck there. After installing gnome-keyring it works fine.

I'd list org.freedesktop.secrets as a required dependency.

nimbusflow commented on 2020-07-27 05:42 (UTC)

The bug has been reported on the MS Teams feedback forums, in case you guys want to upvote:

louisnow commented on 2020-07-22 14:47 (UTC)

@fxsti01 There's another workaround for that bug without having to downgrade.

fxsti01 commented on 2020-07-22 14:43 (UTC)

Screensharing issue, black screen with red line around it, Microsoft bug. installed older version,, works fine. Manually downloaded deb package, get sha256sum from that, edit build files, specify for version and sha256sum, installs and works fine. Set package to not check for updates.

LukasDoe commented on 2020-07-18 16:28 (UTC) (edited on 2020-07-18 16:28 (UTC) by LukasDoe)

@sgni19 I use the default screen resolution FullHD

@L0rne I tried that out. This also happens with a single window in front.

L0rne commented on 2020-07-16 08:14 (UTC)

@LukasDoe Yes i have noticed the same issue. In my experience this only happens if you share a screen with overlapping windows. Sharing a screen with only one window seems to stop the flickering.

sgnl19 commented on 2020-07-15 13:12 (UTC)

Screensharing issue - maybe this helps: Could be a screen resolution issue.

LukasDoe commented on 2020-07-15 07:55 (UTC)

I have an issue with the client. If I make a screensharing session my screen is flickering for the other participants. Have someone else similar observations / expierences?

UnicornsOnLSD commented on 2020-07-06 11:28 (UTC) (edited on 2020-07-06 11:28 (UTC) by UnicornsOnLSD)

This may be for a super small amount of people, but disabling my Oculus Rift CV1 USB devices fixed my microphone. You can either just unplug it or copy the following rules into /etc/udev/rules.d/disable-usb-device.rules

ACTION=="add", ATTR{idVendor}=="2833", ATTR{idProduct}=="0211", RUN="/bin/sh -c 'echo 0 >/sys/\$devpath/authorized'"
ACTION=="add", ATTR{idVendor}=="2833", ATTR{idProduct}=="3031", RUN="/bin/sh -c 'echo 0 >/sys/\$devpath/authorized'"

Mexx77 commented on 2020-07-03 07:21 (UTC)

thanks @louisnow. the workaround fix' it for me: mv /usr/share/teams/resources/app.asar.unpacked/node_modules/slimcore/bin/rect-overlay /usr/share/teams/resources/app.asar.unpacked/node_modules/slimcore/bin/rect-overlay-broken

louisnow commented on 2020-07-02 15:13 (UTC)

For anyone suffering from the black screen with a red border when trying to screen share, Microsoft has acknowledged the problem and there's a temporary workaround.

norg commented on 2020-07-02 13:27 (UTC)

You can use a X compositor as a workaround. For example when I run picom screen share works again (I run i3wm via xinitrc so no compositor active by default)

louisnow commented on 2020-07-02 13:04 (UTC) (edited on 2020-07-02 15:35 (UTC) by louisnow)

@Mexx77 To downgrade, uninstall teams. Clone the repo. git clone Checkout to the right commit and run makepkg -scri

Now to prevent automatic upgrades, add it to IgnorePkg

russkel commented on 2020-07-02 12:57 (UTC)

@maurice-mueller I have actually tried that earlier today but same issue - no share screen button. My computer must be missing something...

maurice-mueller commented on 2020-07-02 12:55 (UTC) (edited on 2020-07-02 12:55 (UTC) by maurice-mueller)

Workaround for screen sharing: the web app with Chrome browser can share your screen as well. I'm using that for now.

Mexx77 commented on 2020-07-02 12:47 (UTC) (edited on 2020-07-02 13:23 (UTC) by Mexx77)

@louisnow @asamuel same here. with teams if I share my screen, monitor goes black with red border. How did u downgrade?

russkel commented on 2020-07-01 23:48 (UTC)

@NGeorgescu so screensharing did work? I am running this package on Manjaro and can't get any luck with the screensharing button even showing.

NGeorgescu commented on 2020-07-01 18:59 (UTC)

Ok so if you are having screensharing problems, you need to downgrade. My temporary solution is to grab the old (March 2020) .deb from here, debtap it, and then delete the dependencies, and pacman -U the .zst file. Not sure if this is a stupid way to do things until a fix is published or if some more elegant arch-like solution exists for downgrading from the AUR.

costisp commented on 2020-07-01 13:18 (UTC)

Thank you so much @jvybihal for the guidance.

The default arg for curl was -C - which resumes transfers. Apparently there was something wrong with a previously failed download. I couldn't find where the partially downloaded file was, so I removed the flag in my ~/.makepkg.conf.

Thanks very much for the help and apologies for polluting the comments section with a question apparently unrelated to this package.

jvybihal commented on 2020-07-01 10:27 (UTC)

@costisp do you have modified curl command options in DLAGENTS of /etc/makepkg.conf? Try DL with those options defined there?

costisp commented on 2020-07-01 10:23 (UTC) (edited on 2020-07-01 10:26 (UTC) by costisp)

I get the error bellow when trying to install this package.
But I can download the package just fine if I do
curl -O

I am new to Arch. Any ideas how can I debug this?


Building teams...
==> Making package: teams (Wed 01 Jul 2020 11:12:26 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading teams_1.3.00.16851_amd64.deb...
** Resuming transfer from byte position 70105596
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0   222    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 416
==> ERROR: Failure while downloading
Failed to build teams

louisnow commented on 2020-06-30 12:05 (UTC) (edited on 2020-06-30 12:06 (UTC) by louisnow)

@asamuel I downgraded teams for now. Here's a thread on Microsoft's forum with a very similar problem although it's supposed to be fixed with the latest update. I don't have a 3440 x 1440 monitor though, just two 1080p monitors.

entropie commented on 2020-06-30 07:27 (UTC)

I always get 2 MS Teams Symbols on the system tray on Manjaro Deepin, both are working tho.

asamuel commented on 2020-06-30 05:19 (UTC)

I'm facing the same issue as @louisnow after updating to I'm on Manjaro KDE with single monitor. If I share my screen, monitor goes black with red border.

louisnow commented on 2020-06-29 20:08 (UTC)

After updating teams, the entire monitor goes black with a red border when I share my screen. I'm using i3 with two monitors if that makes any difference.

ralberts commented on 2020-06-26 15:15 (UTC)

Is anyone else getting the message "We're still developing Teams for Linux" when you start up the application?

twelveeighty commented on 2020-06-26 14:12 (UTC)

@hendry Teams has its own systray icon. So if you have a WM/DE that supports it, you'll see a Teams icon there. There's a Quit option there that exits Teams cleanly. The systray works in both KDE and i3, so I assume it'll be there for most WM/DEs.

hendry commented on 2020-06-26 05:11 (UTC)

Anyone know how to ummm, kill / exit teams? Seem immune to pkill teams

jphustman commented on 2020-06-25 20:56 (UTC)

The newer 'beta' versions are here:

I disconnected from my work network (ethernet) and tethered in through my cell phone. I got a completely different sign in screen. On the network I get a little purple box that I can never authenticate through.

When tethering, I got the screen that shows up as if you are trying to log in through the web browser... Interesting in deed. I'm going to try the 'insiders' one that is using version

xamindar commented on 2020-06-25 14:46 (UTC)

Any reason we don't use the more up-to-date ones from here?

tomeinstein commented on 2020-06-25 12:27 (UTC) (edited on 2020-06-25 12:27 (UTC) by tomeinstein)

Does someone know why lately Teams can't connect to internet? I deleted all config files in .config/Microsoft/'Microsoft Teams' and reset iptables configuration to accept everything but none seems to work.

zman0900 commented on 2020-06-22 22:31 (UTC)

This may be specific to my company, but the only way I am able to complete the initial login is to disconnect from the VPN. Once logged in, I can reconnect to VPN and teams continues to work fine, including after restarting it.

jphustman commented on 2020-06-22 21:33 (UTC)

I never can connect, it says 'Taking you to your organization's sign in page' and gives me the logon box, but when I put my credentials in it never connects. It just sits at "Taking you to your organizations sign-in page" with the dots spinning and spinning and spinning. Eventually popping the purple logon box back up.

cuevaskoch commented on 2020-06-17 14:33 (UTC)

This isn't necessarily related to this package, but chiming in on mic chat: on my install, using KDE, Teams was automatically assigned to an audio input device I don't use. I swapped it out in the KDE system settings and everything works great.

Soldat56 commented on 2020-06-10 06:42 (UTC) (edited on 2020-06-10 06:43 (UTC) by Soldat56)

@japhir Yeah same... It seems to work through Chromium...

Edit: It might be because of KDE... I seem to get it working on another arch install, this time woth XFCE.

japhir commented on 2020-06-05 08:38 (UTC)

I'm also experiencing mic problems. Managed to get it working in the web version through chromium. I saw some things about running it as root and/or adding the user to the groups video and pulse but neither seems to work for me.

erenoglu commented on 2020-05-18 17:07 (UTC)

I have the same mic problem and had to revert to Windows due to this.

Soldat56 commented on 2020-05-14 09:03 (UTC)

Somehow, I cannot use my mic... It tries to manage it on its own and I do not succeed to get it working. I got a USB mic working on digital duplex

trescott2000 commented on 2020-05-07 09:44 (UTC) (edited on 2020-05-07 09:45 (UTC) by trescott2000)

@jat255 and anyone else with this problem:

PROBLEM: After login I get: "Access restricted / We're still developing Teams for Linux / Thank you."

SOLUTION: I copied Ubuntu's /etc/os-release file to my system. Re-start Teams.

booshlinux commented on 2020-05-05 12:36 (UTC)

Can confirm this package uses excessive cpu at times. Judging by M$'s history I would not doubt the claims. I'm not starting any debates though :-)

xamindar commented on 2020-05-05 12:16 (UTC) (edited on 2020-05-05 12:16 (UTC) by xamindar)

@zehph, are you sure you are not talking about the other teams package?

That one would act the way you describe when I had it installed. This one, however, doesn't use nearly as much cpu.

ogarcia commented on 2020-05-04 11:56 (UTC)

@zehph if you have any clue about mining with ms-teams, report upstream, if not, please don't spread FUD

zehph commented on 2020-05-04 11:48 (UTC)

I've checked the PKGBUILD and it didn't appear to have anything wrong, but after installed it was consuming too much CPU and the computer would get hot af and the fans would slow down as soon as I closed teams... I didn't say anything because I have no evidence, but I've dusted off my tinfoil hat and removed the package from my system.

jvybihal commented on 2020-05-04 11:40 (UTC)

Basically said, this PKGBUILD just takes .deb package provided by Microsoft, and unzips it into your filesystem.

You can inspect the package by donwloading it from and open it in archive manager of your choice (for example File Roller, engrampa, Ark, etc.).

I don't get what you are trying to say about bitcoin and other stuff. If you dont like binaries provided, shout @ Microsoft.

zehph commented on 2020-05-04 11:33 (UTC)

Anyone else noticed the spikes in processor usage and references to a renderer with a flag to disable a function to spare said renderer and another saying token? I then "grep'd" for bitcoin and I found references in timeshift pointing to /usr/share/teams if I'm not mistaken, I can't verify the paths anymore because I uninstalled the package, but someone more savyy with this kind of stuff should REALLY give a thourough look on this package, because I could almost fry an egg on my notebook If I left Teams open for too long!

booshlinux commented on 2020-04-29 14:01 (UTC)

Does this version support dynamic backgrounds for video chats?

fuckarchlinux commented on 2020-04-29 01:42 (UTC)

As others have said like webcam and mic to not work after a clean build. For me, It was able to detect webcam and mic out of the box under Dell Inspiron 13 7000 Series.

zehph commented on 2020-04-28 22:56 (UTC)

The app has a slight problem, at least in the 2 WM that I've used (I3 and DWM) the app doesn't close to tray, and the close button doesn't work. The only ways so it will always be in a Workspace/Tag or I have to kill, but then I don't get notifications, obviously.

titaniumbones commented on 2020-04-28 04:25 (UTC)

@juanmah if your camera isn't working, it's possible that you need to go into preferences and change the camera source. My webcam (Thinkpad T490) somehow generates two camera inputs, even though there's only one physical camera; and only one of those inputs actually shows a picture.

thumbless commented on 2020-04-27 17:45 (UTC)

@jvybihal Ooh it works now cool.

jvybihal commented on 2020-04-27 07:52 (UTC)

@thumbless I am using yay, and it works fine here. Try yay -Scc && yay -S teams and make a clean build.

thumbless commented on 2020-04-26 08:09 (UTC)

When trying to install this by yay I get

error: missing package metadata in /home/ninjja/.cache/yay/teams/teams- error: '/home/ninjja/.cache/yay/teams/teams-': invalid or corrupted package

altermetax commented on 2020-04-24 00:07 (UTC)

The Teams Preview for Linux is affected by the same bug other Electron apps are having due to the update to glibc 2.31.

Here's the bug report for Discord, which is pretty identical to Teams:

If anyone has contacts with someone at Microsoft who works on Teams, please report this since it's critical. I reported it on their bug reporting tool ( but it is a bit clunky and I don't know if they'll ever notice it.

jarnold commented on 2020-04-23 13:23 (UTC)


You said:

If it doesn't work for someone: Look which browser you're using! For example Firefox doesn't work with it's latest version: >

Is this related to this package?

TornaxO7 commented on 2020-04-21 11:29 (UTC)

@jarnold what do you mean?

TornaxO7 commented on 2020-04-20 13:54 (UTC)

The camera doesn't work but the rest is fine

juanmah commented on 2020-04-15 12:19 (UTC)

The camera is not working!

Audio OK, by the way.

jat255 commented on 2020-04-10 20:28 (UTC)

Just tried this package, and after logging in, I got a message "Access restricted / We're still developing Teams for Linux / Thank you." Anyone see this also?

glenntanner3 commented on 2020-04-10 15:02 (UTC) (edited on 2020-04-10 15:04 (UTC) by glenntanner3)

@aulemahal I came here about the same; after ending a call I close and reopen teams (due to memory usage and toggle my headphones back from HSP/HFP to A2DP). I find if I go into audio and only change my headphones it cases problems later on.

ogarcia commented on 2020-04-09 11:23 (UTC)

@pepijndevos @jvybihal Seems a RUA issue Anyway, --no-same-owner is a default option of tar for ordinary users

jvybihal commented on 2020-04-09 09:39 (UTC)

@pepijndevos try insatlling bubblewrap-suid, that should hopefully help you.

I am not familiar with rua at all, but I found this, it should give some clarification Tbh, I did not read it thru the end, so I dont know if that was succesfully solved, but it feels liek a problem of rua and not the PKGBUILD.

I tried to build google-chrome-dev in rua, it also fails without bubblewrap-suid.

pepijndevos commented on 2020-04-09 09:20 (UTC)

This package fails to build using rua, which uses some sort of chroot. Would you consider adding --no-same-owner to the tar command? This fixes the problem.

jarnold commented on 2020-04-06 14:16 (UTC) (edited on 2020-04-06 14:16 (UTC) by jarnold)

@TornaxO7 How would you go about changing the browser agent?

aulemahal commented on 2020-04-04 14:49 (UTC) (edited on 2020-04-04 14:51 (UTC) by aulemahal)

After leaving a call, I noticed that my mic was still recording, even though nothing on Teams seemed to indicate any use of my mic. In PulseAudio's control panel, it showed up as "skype". Is this a bug of this package? Or a known Teams bug? I sure hope it's not a feature... Using version

ogarcia commented on 2020-03-31 15:55 (UTC)

@cleversonahum seens a problem with Manjaro build scripts, but you can download file by hand and do makepkg

cleversonahum commented on 2020-03-31 15:44 (UTC)

package source not reachable: using Manjaro. I can download the file using wget and browser

samSPV commented on 2020-03-31 11:41 (UTC)

Just encase anyone here has the same issue as my previous post my timezone was wrong.

Setting time correctly fixed the issue

jvybihal commented on 2020-03-31 11:36 (UTC)

@samSPV so it's probably Microsoft's software problem. Contact support.

samSPV commented on 2020-03-31 11:32 (UTC) (edited on 2020-03-31 11:32 (UTC) by samSPV)

So this was working in fine last week. I started work on monday and can no longer login.

Same happens in both foxfire and chrome, I get Infinity redirected until it logs me out.

jvybihal commented on 2020-03-30 08:25 (UTC)

@alberto2000 works just fine.

alberto2000 commented on 2020-03-30 08:24 (UTC)

package source not reachable:

jvybihal commented on 2020-03-30 07:54 (UTC)

@sigvald I think this is not job for package, I believe package should never ever touch files in users dir. Also it would not help, because the teams app recreates that file, if it does not exist.

See my comment here and try workaround I suggested.

sigvald commented on 2020-03-30 07:49 (UTC)

This program brings with it one particular aspect of Windows environments that annoy me: namely that every program considers themselves so much more important than every other program that they think they should be running all the time. For others who want to prevent Teams from autostarting, delete the following file:


May I even suggest that the PKGBUILD be modified to delete this file after installation? Perhaps while printing a message for how to activate it again? I find this behaviour very un-UNIX-like.

TornaxO7 commented on 2020-03-28 21:44 (UTC) (edited on 2020-03-28 21:46 (UTC) by TornaxO7)

If it doesn't work for someone:
Look which browser you're using!
For example Firefox doesn't work with it's latest version:

ginhands commented on 2020-03-28 11:08 (UTC)

@interja interesting to know that it does work, I'm using I3 and X, I'll keep digging. Maybe I'll switch window managers and see what happens. Thanks for the reply.

Interja commented on 2020-03-26 12:46 (UTC)

@ginhands using gnome with X worked for me.

ginhands commented on 2020-03-25 09:54 (UTC)

Should screen sharing work on this package? AFAIK it works out of the box on Ubuntu, but when I install this package the screen share icon is hidden.

usuariopolivalen commented on 2020-03-20 11:27 (UTC)

PD: now for me is working well withouth freezes

usuariopolivalen commented on 2020-03-20 11:26 (UTC)

is there any repo for this package?

damico commented on 2020-03-19 18:31 (UTC)

Hi, for some reason my notebook camera is not working. It says: no available camera found. Just to know, Skype for example, works fine with camera. Someone know if this is a bug or how to fix it?

usuariopolivalen commented on 2020-03-18 11:50 (UTC)

@undelaterreta, can you fill the bug please? i have not much time these days for disgrace.

usuariopolivalen commented on 2020-03-18 11:43 (UTC)

I am using plasma, for more info..

undelaterreta commented on 2020-03-17 17:13 (UTC)

@agm28011997 I'm having the same issue. Idk how fix it, but using Teams on the browser (brave in my case) it works without freezes.

jvybihal commented on 2020-03-17 15:38 (UTC) (edited on 2020-03-17 15:39 (UTC) by jvybihal)

@agm28011997 you can try filing bug here.

usuariopolivalen commented on 2020-03-17 15:34 (UTC)

for me teams when I am joing a group work is crashing almost my pc. I can not enter a word.. the only fix to close the app. My girlfriend in manaro( like me) is having the same problem, both of us with amd cpu+igpu

jvybihal commented on 2020-03-16 08:17 (UTC)

@hamelg It works for some people - i would suggest asking miscrosoft directly ;)

hamelg commented on 2020-03-16 08:07 (UTC)

Is there any workaround to enable the two-factor auth ? I can't login with it on my corporate account :(

jvybihal commented on 2020-03-14 13:08 (UTC)

You could try something like > ${HOME}/.config/autostart/teams.desktop && chmod 0000 ${HOME}/.config/autostart/teams.desktop

Just create that teams.desktop, leave it empty and deny any write to it ;)

andreas_e commented on 2020-03-14 12:56 (UTC)

Not a build or install problem, but Teams creates an autostart entry after every app start in Gnome. Has anyone solved that yet? Otherwise I would just switch to the web client.

wizard32 commented on 2020-02-03 12:02 (UTC)

I turned off a couple of notification and same settings applied also to my mobile app. I think it could be good option to separate options from applying only in the current installation app.

jakub commented on 2020-01-31 18:01 (UTC) (edited on 2020-01-31 18:02 (UTC) by jakub)

Is there a way to change systray icon? I use dark theme in Plasma and icon is blurred. Because icon color is rather dark too, it causes that it's just not really visible/easy to find on systray. Any advices? Screenshot:

tgm4883 commented on 2020-01-24 20:50 (UTC)

Not really packaging related, but not sure where else to mention this. I've noticed that on both the 1.2 and 1.3 versions that after a call ends that PulseAudio says that Skype is still using the microphone and speakers (I don't use skype). Once I close and reopen teams this goes way

0Merlin0 commented on 2020-01-15 10:32 (UTC)

@fasseg: I had problems with it, but then I did some digging and installing gnome-keyring fixed it for me.

obrez commented on 2020-01-10 21:37 (UTC)

@zman0900 I am also not able to log in with 2 form factor.

fasseg commented on 2020-01-08 08:31 (UTC)

Has anyone got trouble logging in using the SSO (eg. ADFS) feature? Clicking on the "Submit" button in the SSO login dialog does nothing for me.

ogarcia commented on 2019-12-18 07:24 (UTC)

@zman0900 I have two-factor with SMS and login works OK

zman0900 commented on 2019-12-18 03:53 (UTC)

Is anyone able to log into a work account that has two-factor auth enabled? For me it either rejects my password immediately or seems to hang forever.

ogarcia commented on 2019-12-13 16:15 (UTC)

For people who have problems with audio, I'm using USB headphone with pulseaudio without problems, even using jack output and USB input works fine. Please do a double check in mixer because the problem could be in levels.

knatter commented on 2019-12-13 10:55 (UTC)

Microphones via USB headset do not work. It is shown in the settings but does not work.

tgm4883 commented on 2019-12-12 18:27 (UTC)

@theangryangel I had a similar audio issue but it was fixed after restarting teams. I don't think teams likes having the audio input added to the system after it starts (my headset is connected via docking station).

The only issue I'm having now is constant mid-high CPU usage (40% CPU usage) after ending a call when the application is idle in the system tray.

theangryangel commented on 2019-12-11 18:05 (UTC)

Anyone having issues with audio? Output works fine, but I cannot get it to record from my Mic. It doesn't show up in pulse as even trying to open a recording stream afaik.

felipebalbi commented on 2019-12-11 15:41 (UTC)

It would be great to have an option to disable the notifications. It looks super weird on i3. But hey, great work getting this packaged up

jvybihal commented on 2019-12-11 15:41 (UTC)

Cool, thanks everyone.

ogarcia commented on 2019-12-11 15:35 (UTC)

@Muflone and @jvybihal, thank you too!

@jvybihal done! And feel free to update it without problems.

Muflone commented on 2019-12-11 15:28 (UTC) (edited on 2019-12-11 15:28 (UTC) by Muflone)

please consider adding a replace and conflict with ms-teams

also the URL should be replaced with the project home page or official website

Muflone commented on 2019-12-11 15:26 (UTC)

thank you @jvybihal and @ogarcia for settling the things so easily.

I'm therefore deleting the ms-teams package, now useless.

jvybihal commented on 2019-12-11 15:23 (UTC)

@Muflone ok :)

Also, I think teams-for-linux-official-bin by @dennisoehme should merge too, I saw he put some nice work into PGP validation and it is always nice to have.

ogarcia commented on 2019-12-11 15:23 (UTC)

@muflone, the package that is a duplicate of ms-teams is that is a different version of teams only for insider users. This package is the open one, I think that both packages must exist since are differents versions.

I added @jvybihal as co-maintainer in both packages, this and

@jvybihal I think that names must be teams and teams-insiders as original ones. People find this package before ms-teams because enter teams word in search box and suggest this one.

Muflone commented on 2019-12-11 15:18 (UTC) (edited on 2019-12-11 15:18 (UTC) by Muflone)

@jvybihal I think the teams name suits better. You could co-maintain it along with @ogarcia

Then we can delete the ms-teams package

jvybihal commented on 2019-12-11 15:03 (UTC)

I agree that the duplicates need to merge into one. I contacted @ogarcia about a month ago with PRQ#16712. He suggested keeping name teams-insiders - which kind of makes sense, because it's the naming MS uses, but I (as some others) like ms-teams much better. So I decided not to argue and let it be, without reply - I knew my package was not originally aimed for the insiders version, I just wanted to create the ground for official release once it came out. And now it did, and I switched my package to it.

It is beyond my understanding why we have 3 packages of the same thing now, and what is the reasoning behind it.

Anyway, I like ms-teams name, but I don't care too much about it, so merging everything into 'teams' is fine with me, if others like it better. I can co-maintain it, but I do not insist on it.

wizard32 commented on 2019-12-11 14:57 (UTC) (edited on 2019-12-11 14:58 (UTC) by wizard32)

Works fine to me. The only issue that I have so far is the auto-correction and the spell check is not working any more. Any other here with the same issue?

Muflone commented on 2019-12-11 14:38 (UTC) (edited on 2019-12-11 14:49 (UTC) by Muflone)

@ogarcia this package is a duplicate of which was created 3 months ago, while this package was created yesterday

we have to make a choice here:

1- this package will be removed and ms-teams will keep the previous name

2- you let the ms-team package to take this package and we can merge ms-teams into teams

davidhaller commented on 2019-12-11 08:50 (UTC)

Chrome installs certificates user-wide (I believe the location was ~/.pki), this might be the reason Teams can see your company certificate.

ogghi commented on 2019-12-11 07:41 (UTC)

I don't think so, as I don't have any chrome/chromium installed in my laptop since I re-installed with Arch... Also nothing written here in the dependencies?

je-vv commented on 2019-12-11 05:20 (UTC) (edited on 2019-12-11 05:20 (UTC) by je-vv)

Does "teams" on gnu+linux depends on chromium/chrome, or at least reads chromium/chrome settings somehow? If a dependency, should it be included as such?

See, I authenticated for the company account, and it rejected me since I don't have double authentication, but after adding my personal company certificate to chromium, it just worked. Which makes me suspect whether teams is using chromium/chrome to authenticate, or it uses its setting given it's sort of based on chromium/chrome...

gobonja commented on 2019-12-10 22:19 (UTC)

Works great!

ogghi commented on 2019-12-10 19:07 (UTC)

Thanks, seems to work like a charm here! :)