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

Build fails with:

==> Starting build()...
Unknown Syntax Error: Unsupported option name ("--pure-lockfile").

$ yarn install [--json] [--immutable] [--immutable-cache] [--refresh-lockfile] [--check-cache] [--check-resolutions] [--inline-builds] [--mode #0]
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: teams-for-linux-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
teams-for-linux - exit status 4

EDIT: Looks like it uses the locally installed yarn version, which was yarn v4 that I had installed. It is fixed after setting the version to the one that is specificed in the package.json on github.

@nursoda pre-releases are clearly marked as such, when you look at them.

@pschichtel: How to tell it's a prerelease? I was looking here: https://github.com/IsmaelMartinez/teams-for-linux/releases Wrong place?

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.

I had these hints while building … Upstream issues? Both of them?

node:166375) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[3/4] Linking dependencies...
warning "electron-builder > app-builder-lib@24.13.3" has unmet peer dependency "electron-builder-squirrel-windows@24.13.3".

@snack, from:

https://github.com/IsmaelMartinez/teams-for-linux/discussions/1163#discussioncomment-9023906

I see a comment that on 1.4.19 the icon number was fixed, but probably --useMutationTitleLogic was needed. In case you have to move back to 2.0... I don't know if with later versions that's not required, we're already on 1.4.30...

teams-for-linux has a reach set of args that I would recommend exploring, that makes things easier than changing electron stuff, :)

@je-vv I have just installed pipewire and then sharing screen works perfectly. Thanks a lot!

@Mthw, it built just fine some hours ago for me, on /var/log/pacman.log:

[ALPM] upgraded teams-for-linux (1.4.29-1 -> 1.4.30-1)

So yes, building ok...

@mluque, are you actually using xwayland? Have you tried running teams-for-linux natively on wayland? I think that's much better than trying to running as a xwayland app...

I'm using:

teams-for-linux --closeAppOnCross --disableAutogain --ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations

That allows running teams-for-linux natively on wayland. And I have no issues sharing my screen.

On wayland, the only way to share screen is through a desktop portal with pipewire. See:

https://wiki.archlinux.org/title/PipeWire#WebRTC_screen_sharing

I would recommend not adding strict dependencies on xwayland stuff, perhaps have them as opt depends. And teams-for-linux is working natively on wayland just fine, including screen sharing. One just needs pipewire and the proper desktop portal, which BTW, are still required if wanting to use something like xwaylandvideobridge.

And as the requirements for a proper desktop portal and pipewire are still there on wayland, I see no purpose on running teams-for-linux on xwayland, and adding on top a video bridge. I do believe you better try native wayland teams-for-linux. I wouldn't like to install the video bridge, when it so happens I don't need it BTW, that's why perhaps it might be an opt dep...

Just my $0.02...