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

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

This build can not use the camera. It says it has no permission to use it. Maintainer says it is the fault of the AUR package maintainer: https://github.com/IsmaelMartinez/teams-for-linux/issues/1567#issuecomment-2679793833

Any idea how to grant camera permission to it?

Weird @carlosnewmusic, it builds fine on two computers. What I could see from the log you posted is trying to create a new directory over a read-only FS:

npm error code 1
npm error path /var/cache/private/pamac/teams-for-linux/src/teams-for-linux-1.12.6/node_modules/electron
npm error command failed
npm error command sh -c node install.js
npm error Error: EROFS: read-only file system, mkdir '/.cache'

It might be an artifact from pamac, which I don't use, but why trying to create a cache directory in the root directory (/), no non-root user should be able to create directories there, but again I'm not clear what is pamac trying to do there. Can you try plain makepkg? I use aurutils to help me out, which directly uses makekpkg. Greetings !

build error https://pastebin.com/DxHZzPMi