Arch Linux User Repository

Before marking the package out of date, please first check that the new version is not a pre-release. I'm tracking releases, not pre-releases.

Talk to community members here:

https://matrix.to/#/#teams-for-linux_community:gitter.im

@dmark04 and @paulmelis: I've added --gtk-version=3 to the .desktop-file' exec command as suggested in the electron issue related to this problem: https://github.com/electron/electron/issues/46538

Can only echo @paulmelis

Here's the full error:

No config file found, using default values
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
14:50:40.658 › configPath: /home/dmaier/.config/teams-for-linux
14:50:40.660 › Running under Wayland, switching to PipeWire...
14:50:40.710 › (node:323988) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
    at asarStatsToFsStats (node:electron/js2c/node_init:2:1748)
    at t.lstatSync (node:electron/js2c/node_init:2:4830)
    at t.statSync (node:electron/js2c/node_init:2:5392)
    at module.exports [as findUp] (/opt/teams-for-linux/resources/app.asar/node_modules/escalade/sync/index.js:6:19)
    at [pkgUp] (/opt/teams-for-linux/resources/app.asar/node_modules/yargs/build/index.cjs:1:48105)
    at [guessVersion] (/opt/teams-for-linux/resources/app.asar/node_modules/yargs/build/index.cjs:1:47676)
    at te.version (/opt/teams-for-linux/resources/app.asar/node_modules/yargs/build/index.cjs:1:44679)
    at ue.Yargs (/opt/teams-for-linux/resources/app.asar/node_modules/yargs/build/index.cjs:1:62063)
    at Argv (/opt/teams-for-linux/resources/app.asar/node_modules/yargs/index.cjs:12:16)
    at Object.<anonymous> (/opt/teams-for-linux/resources/app.asar/node_modules/yargs/index.cjs:7:1)

(process:323988): Gtk-ERROR **: 14:50:40.734: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
[1]    323988 trace trap (core dumped)  teams-for-linux --trace-deprecation ../..

This points to a known upstream error in electron: https://github.com/electron/electron/issues/46538

The currently suggested workaround (which also works for me) is to launch with the following keyword teams-for-linux --gtk-version=3

Updated to 2.0.17-1 from 2.0.14-1, which built fine, but when starting teams-for-linux I get an error:

No config file found, using default values
Initialising logger with config: {"transports":{"console":{"level":"info"},"file":{"level":false}}}
11:49:08.885 › configPath: /home/melis/.config/teams-for-linux
11:49:08.943 › (node:20071) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `teams-for-linux --trace-deprecation ...` to show where the warning was created)

(process:20071): Gtk-ERROR **: 11:49:08.948: GTK 2/3 symbols detected. Using GTK 2/3 and GTK 4 in the same process is not supported
Trace/breakpoint trap (core dumped)

I tried a clean rebuild, by removing pkg and src dirs, but the error remains.

Today I upgraded to 2.0.10-1 and suddenly images that I uploaded in chats can no longer be loaded. Just picture placeholders are displayed.

And while I'm editing a message including an image, it says: Cannot load image. Try again later.

Anyone else experiencing this?

UPDATE: Nvm, I can see the pics now, so it seems it must have been a temporary connectivity issue.

@cysec: not sure I can do much about that. If you don't need the debug packages, why not disable generating them?

Getting update failures with this package and https://aur.archlinux.org/packages/slack-desktop-wayland installed at the same time due to the debug packages containing the same build id...

/usr/lib/debug/.build-id/2e/a67fb4a9945e869eb463e0ad868599be33d813 exists in both 'teams-for-linux-debug' and 'slack-desktop-wayland-debug' /usr/lib/debug/.build-id/2e/a67fb4a9945e869eb463e0ad868599be33d813.debug exists in both 'teams-for-linux-debug' and 'slack-desktop-wayland-debug'

Can you make it so that it uses electron34 ? Thank you

@je-vv, you gave me an idea that might have resolved the camera issue. I opened up chromium, signed into teams, and then granted it full camera permissions. Opened teams-for-linux and the camera is working fine now.

FYI just tested teams-for-linux 1.12.7-1 and the camera is working fine.

@xamindar, what Ismael actually replied is that he won't pay attention to a build he doesn't generate. I really dislike this sort of answers, since now it seems the tendency is being like windows releases, a binary provided through some app store and the ability to build doesn't matter, not sure if that actually makes the apps not really free/libre software at least, since one need to be able to build. Rant apart, it's not related with the AUR build, see what he also answered:

they have the same problem in the browser/PWA what means @otaolafranc issue is a microsoft or os configuration

And the OP who he's willing to provide support to just showed up saying he keeps getting the same issue on supported flatpak build.

My suggestion is to keep paying attention to that issue, and revert to the prior version if that was working fine. I don't use a camera so I can't confirm, but I bet the issue is there as the OP indicates. Now I suspect that's something on the chromium side having weird effects on electron, or electron itself for that matter. If you run teams under firejail or some sort of sandbox, perhaps it's worth looking it's profile, to see if camera is block...