4 ms·

The web-based one works perfectly on Linux. If anything it's better than the native Windows app. Office 365 actually works better in Firefox in Linux than any

The web-based one works perfectly on Linux. If anything it's better than the native Windows app. Office 365 actually works better in Firefox in Linux than any other browser in Windows. It's like they've kind of given up on the whole OS thing, and have just decided to go with Linux.

aorth 1y ago
True! I've been doing this for years on Linux. I use a dedicated Chromium instance in app mode: /usr/bin/chromium --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --user-data-dir=/home/myuser/.config/chromium-ilri --app=https://teams.microsoft.com Works incredibly well (put this in a `.desktop` file with `Exec=` and you can launch it via your desktop's launcher). Some of the settings may not be needed anymore, as Chromium has come a long way in terms of Wayland support. I use Firefox for everything else, but haven't tried Teams there.
- cromka 1y ago
  Would be great if it was also possible to have it open the Team URIs in that App Mode instance instead of the browser itself — I assume it does not.
  - homebrewer 1y ago
    What kind of URLs does it use? If it's anything with a unique prefix (like Telegram's tg://), you can add it to the desktop file: MimeType=x-scheme-handler/foobar; and run `update-mime-database`. If not, I would write a shell wrapper and set it as the default browser; something to the effect of: #!/usr/bin/bash set -eu for arg in "$@"; do if [[ $arg == *whatever-url-teams-uses.com* ]]; then exec gtk-launch teams "$@" fi done exec gtk-launch firefox "$@" (gtk-launch uses flags from the .desktop file so you don't have to repeat them)
- snickerer 1y ago
  The only thing that does not work for me with Teams as chromium 'app' is the screen sharing (on Wayland). Does your --enable-features fix this?
  - E39M5S62 1y ago
    Which compositor/environment? Starting the correct xdg portal helped me when I ran Sway.
  - dfc 1y ago
    You need xdg-desktop-portal . Its probably automatic in some environments but with sway I have to set it up manually. Its one of those annoying things I forget about whenever I set up a new machine. https://wiki.archlinux.org/title/XDG_Desktop_Portal https://wiki.archlinux.org/title/XDG_Desktop_Portal
    - snickerer 1y ago
      Thanks. On Debian trixie, xdg-desktop-portal-wlr is broken. I had to compile in manually, but this did the trick.
  - b3nji 1y ago
    Works for me, using Fedora with Plasma. Just fire it up in Brave, and install it as a PWA. The one thing that bothers me is it can't tell if I'm at my machine when I'm not actively using it. People keep thinging I've bugered off from my desk.
  - MrDrMcCoy 1y ago
    Screen sharing from the browser usually works for me, but if ever it doesn't, as a workaround you can use OBS with a virtual webcam to share windows and screens as an overlay to the webcam stream. It's very easy.
Too 1y ago
If by perfect you mean that you can’t have two chats open next to each other and toggling between chats is slow as molasses then yes.
- javcasas 1y ago
  It also doesn't use 1.5 CPU cores non-stop.
- ErroneousBosh 1y ago
  Are you running it on a particularly potatoey PC? On my fairly ancient Core i7-8700 I can have a video call open in one screen and be editing in Resolve on another.
  - dijit 1y ago
    There's something weird going on honestly. On an i9-14900K, arguably one of the fastest CPUs in the previous few years (and excusing their design defect that causes them to die); Teams is significantly slower than on the Quallcom Snapdragon X-Elite, or my Macbook. It seems to perform the same as it would on an i9 platform as it does on i5 laptop's of the same generation (in terms of input latency and drawing to the screen etc;) I know it's apples/oranges, that ARM CPUs are substantially different than x86 ones, but the fact that it seems to be the same on significantly lower clocked (and lower consumptive) chips indicate to me that something very bizarre is happening when it comes to Teams. ARM chips seem to be significantly better for electron applications, but something unique exists within Teams here.
    - tomsmeding 1y ago
      Hypothesis: that Qualcomm and that Macbook have higher memory bandwidth than your i9 system. This is dependent on your memory and your mainboard, not so much on the CPU itself. Perhaps Teams just uses way too much memory, and actually uses it all the time.
      - dijit 1y ago
freedomben 1y ago
Exactly, I've been very pleasantly surprised at how well teams works in the browser on Linux. Much better than zoom!
giancarlostoro 1y ago
I worked in an all Linux dev shop. Our Lead refused to install Electron apps and ran them in Chrome tabs instead. It just worked. I dont remember how we ran Teams back then though.
pmontra 1y ago
It works but it takes a long time to load. I've got two customers that both use Slack for everything except calls. One does calls in Meet and the other one in Teams. I asked to the Teams one and they told me that Teams works for everybody every time. Slack sometimes has problems with the video or audio setup. Too bad, because huddles are only one click away.
aidenn0 1y ago
My experience is the complete opposite. Granted I haven't tried O365 in about a year since it was so unusable in Firefox. As far as teams goes, I use it in the same version chromium on the same OS on two different computers; one works fine most of the time (main issue is it sometimes switches the audio back to the first item listed by Linux, which is not my USB headset). The other computer is terrible. Somewhere between 4-48 hours it pops up a tiny (maybe 40px) banner at the top saying "you need to sign in again" meanwhile there are no notifications and any messages I send are silently queued with no obvious indication that they haven't been delivered. Before I figured this out, I was just randomly out of communication with my coworkers, with both sides thinking we were sending the other person messages that they were ignoring. Clicking the "sign in" button on the banner just seems to reload teams and doesn't even ask me to sign in.

aorth 1y ago

True! I've been doing this for years on Linux. I use a dedicated Chromium instance in app mode: /usr/bin/chromium --ozone-platform=wayland --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --user-data-dir=/home/myuser/.config/chromium-ilri --app=https://teams.microsoft.com Works incredibly well (put this in a `.desktop` file with `Exec=` and you can launch it via your desktop's launcher). Some of the settings may not be needed anymore, as Chromium has come a long way in terms of Wayland support. I use Firefox for everything else, but haven't tried Teams there.

cromka 1y ago
Would be great if it was also possible to have it open the Team URIs in that App Mode instance instead of the browser itself — I assume it does not.
- homebrewer 1y ago
  What kind of URLs does it use? If it's anything with a unique prefix (like Telegram's tg://), you can add it to the desktop file: MimeType=x-scheme-handler/foobar; and run `update-mime-database`. If not, I would write a shell wrapper and set it as the default browser; something to the effect of: #!/usr/bin/bash set -eu for arg in "$@"; do if [[ $arg == *whatever-url-teams-uses.com* ]]; then exec gtk-launch teams "$@" fi done exec gtk-launch firefox "$@" (gtk-launch uses flags from the .desktop file so you don't have to repeat them)
snickerer 1y ago
The only thing that does not work for me with Teams as chromium 'app' is the screen sharing (on Wayland). Does your --enable-features fix this?
- E39M5S62 1y ago
  Which compositor/environment? Starting the correct xdg portal helped me when I ran Sway.
- dfc 1y ago
  You need xdg-desktop-portal . Its probably automatic in some environments but with sway I have to set it up manually. Its one of those annoying things I forget about whenever I set up a new machine. https://wiki.archlinux.org/title/XDG_Desktop_Portal https://wiki.archlinux.org/title/XDG_Desktop_Portal
  - snickerer 1y ago
    Thanks. On Debian trixie, xdg-desktop-portal-wlr is broken. I had to compile in manually, but this did the trick.
- b3nji 1y ago
  Works for me, using Fedora with Plasma. Just fire it up in Brave, and install it as a PWA. The one thing that bothers me is it can't tell if I'm at my machine when I'm not actively using it. People keep thinging I've bugered off from my desk.
- MrDrMcCoy 1y ago
  Screen sharing from the browser usually works for me, but if ever it doesn't, as a workaround you can use OBS with a virtual webcam to share windows and screens as an overlay to the webcam stream. It's very easy.

Too 1y ago

If by perfect you mean that you can’t have two chats open next to each other and toggling between chats is slow as molasses then yes.

javcasas 1y ago
It also doesn't use 1.5 CPU cores non-stop.
ErroneousBosh 1y ago
Are you running it on a particularly potatoey PC? On my fairly ancient Core i7-8700 I can have a video call open in one screen and be editing in Resolve on another.
- dijit 1y ago
  There's something weird going on honestly. On an i9-14900K, arguably one of the fastest CPUs in the previous few years (and excusing their design defect that causes them to die); Teams is significantly slower than on the Quallcom Snapdragon X-Elite, or my Macbook. It seems to perform the same as it would on an i9 platform as it does on i5 laptop's of the same generation (in terms of input latency and drawing to the screen etc;) I know it's apples/oranges, that ARM CPUs are substantially different than x86 ones, but the fact that it seems to be the same on significantly lower clocked (and lower consumptive) chips indicate to me that something very bizarre is happening when it comes to Teams. ARM chips seem to be significantly better for electron applications, but something unique exists within Teams here.
  - tomsmeding 1y ago
    Hypothesis: that Qualcomm and that Macbook have higher memory bandwidth than your i9 system. This is dependent on your memory and your mainboard, not so much on the CPU itself. Perhaps Teams just uses way too much memory, and actually uses it all the time.
    - dijit 1y ago

freedomben 1y ago

Exactly, I've been very pleasantly surprised at how well teams works in the browser on Linux. Much better than zoom!

giancarlostoro 1y ago

I worked in an all Linux dev shop. Our Lead refused to install Electron apps and ran them in Chrome tabs instead. It just worked. I dont remember how we ran Teams back then though.

pmontra 1y ago

It works but it takes a long time to load. I've got two customers that both use Slack for everything except calls. One does calls in Meet and the other one in Teams. I asked to the Teams one and they told me that Teams works for everybody every time. Slack sometimes has problems with the video or audio setup. Too bad, because huddles are only one click away.

aidenn0 1y ago

My experience is the complete opposite. Granted I haven't tried O365 in about a year since it was so unusable in Firefox. As far as teams goes, I use it in the same version chromium on the same OS on two different computers; one works fine most of the time (main issue is it sometimes switches the audio back to the first item listed by Linux, which is not my USB headset). The other computer is terrible. Somewhere between 4-48 hours it pops up a tiny (maybe 40px) banner at the top saying "you need to sign in again" meanwhile there are no notifications and any messages I send are silently queued with no obvious indication that they haven't been delivered. Before I figured this out, I was just randomly out of communication with my coworkers, with both sides thinking we were sending the other person messages that they were ignoring. Clicking the "sign in" button on the banner just seems to reload teams and doesn't even ask me to sign in.