Anyone have experience setting up Microsoft Teams?

General Discussion
1

This is probably a long shot. For work I need to have Microsoft Teams up and running. Running the webapp in Firefox works somewhat using the extension to change the user agent. This works for 1-1 video chats but breaks down as soon as more people are involved.

I talso ried installing the flatpak options as well as with dnf, but it breaks down, displaying only blank windows. The output is:

Overriding TZ to Europe/Amsterdam
Gtk-Message: 21:20:03.134: Failed to load module “canberra-gtk-module”
Gtk-Message: 21:20:03.134: Failed to load module “canberra-gtk-module”
(node:2) UnhandledPromiseRejectionWarning: ReferenceError: window is not defined
at /app/extra/teams/resources/app.asar/node_modules/ipc-monitor/renderer/dom-observables.js:31:5
at new Promise ()
at Object. (/app/extra/teams/resources/app.asar/node_modules/ipc-monitor/renderer/dom-observables.js:30:30)
at Object. (/app/extra/teams/resources/app.asar/node_modules/ipc-monitor/renderer/dom-observables.js:62:3)
at Module._compile (/app/extra/teams/resources/app.asar/external/v8-compile-cache/v8-compile-cache.js:192:36)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:704:10)
at Module.load (internal/modules/cjs/loader.js:602:32)
at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
at Function.Module._load (internal/modules/cjs/loader.js:533:3)
at Module.require (internal/modules/cjs/loader.js:640:17)
(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:2) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:2) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 appInitialized listeners added. Use emitter.setMaxListeners() to increase limit
(node:2) UnhandledPromiseRejectionWarning: undefined
(node:2) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

Any leads are greatly appreciated. Thanks!

2

Not the same issue, but I cannot login with a personal account, seems the Linux edition only allows corporate accounts to login.

3

Yep, it worked today after clicking a team invite link and choosing to open it in the flatpak app (with a corporate account). Not sure what changed but this is nice. ClearLinux version is 33800 (downgraded from 33810 due to an unrelated issue).

4

The unhandledRejection event is emitted whenever a promise rejection is not handled. “Rejection” is the canonical term for a promise reporting an error. As defined in ES6, a promise is a state machine representation of an asynchronous operation and can be in one of 3 states: “pending”, “fulfilled”, or “rejected”. Somebody decided that JavaScript programmers couldn’t be trusted with managing promise rejections properly and changed the HTML spec to require browsers to throw “unhandled promise rejection” errors if a rejected promise has no rejection handlers added before code returns to the event loop. The error usually happens in async await functions, and there’s an easy fix.

const functionName = async (arguments) => {
  try {
  // Your code here
  } catch (error) {
  // Handle rejection here
  }
};
5

Hi warrensacko - thanks for your input, although you’re replying to a 2 year old thread with information that is more useful to a MS developer than a Clear Linux user. :frowning: