Arch Linux User Repository

@je-ve, fantastic work, thanks for the patch! Included in 4.36.136-2. Screen sharing works yet again for me :)

Here it's the package patch, to stop slack from preventing screen sharing:

% cat slack-electron.patch
diff -Naur laur/slack-electron/PKGBUILD others/slack-electron/PKGBUILD
--- laur/slack-electron/PKGBUILD        2023-12-22 16:05:07.571399860 -0600
+++ others/slack-electron/PKGBUILD      2024-01-03 19:14:40.472181329 -0600
@@ -38,6 +38,7 @@
     -e 's|^(Exec=.+/slack)(.+)|\1 -s\2|' \
     -e 's/^Icon=.+slack\.png/Icon=slack/' \
     "usr/share/applications/slack.desktop"
+  sed -i -e 's|,"WebRTCPipeWireCapturer"|,"LebRTCPipeWireCapturer"|' usr/lib/slack/resources/app.asar
 }

 package() {

On the package the app.asar is under the resources sub-directory, as apposed to the installed SW...

Notice one still needs to call:

slack --ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations -s

@carsme, perhaps you can add the sed command as shown in the patch, :)

Thanks a lot !

OK, got screen sharing as well, with several workarounds. It's currently disabled by slack, and it's because its' far from stable, bur on can make it work... Source: github issue Screen sharing on wayland. From there:

found that Slack explicitly disables WebRTCPipeWireCapturer in a process argument.

So adding:

sudo sed -i -e 's/,"WebRTCPipeWireCapturer"/,"LebRTCPipeWireCapturer"/' /usr/lib/slack/app.asar

Is the key

As of now, electron26-bin is no longer required, since electron got upgraded to electron27 on Arch. And with electron27, slack does not segfault either. So no changes on PKGBUILD required.

However I'm unable to share screen on huddles at all. Using:

slack --ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations -s

Also tried:

slack --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations,WebRTCPipeWireCapturer -s

And no luck, :(

What you share is a black screen only, :(

As teams-for-linux had issues with electron prior to 28, and with 28 it can shared screen, I tried with electron28-bin, but again no luck.

So slack no longer segfaults, but I have found no way to share screen on huddles with slack, :(

Has someone gotten screen sharing on huddle working?

I can actually confirm what @carsme commented. Using electron26 does actually work fine.

Go for it @carsme, having to install electron26-bin from AUR sounds fine with me, and it's the only way to make it work any ways, at least for non gnome users, :)

Well, to me it always segfaults with:

--ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations

Or with:

--ozone-platform-hint=auto --enable-webrtc-pipewire-capturer --enable-features=WaylandWindowDecorations,WebRTCPipeWireCapturer

Whether building and running with electron25, electron24 or electron23. So I don't know.

I use wayfire though, and xdg-desktop-portal-wlr as default and xdg-desktop-wlr-gtk for things not covered for the former...

Perhaps gnome does some gnome only tricks, but the electron version doesn't seem to be the key. It does fail differently though. Eearlier than electron25, slack doesn't even attempt to launch, on 25 it does attempt it.

It works for me on Gnome Wayland, I have the following installed but I'm not sure which one it uses:

extra/electron25 25.9.4-1 (60.4 MiB 212.7 MiB) (Installed)
extra/electron24 24.8.8-1 (59.1 MiB 207.7 MiB) (Installed)
extra/electron 1:25-1 (3.6 KiB 0.0 B) (Installed)

I have not been able to run slack-electron in Wayland for a couple of months due to a segfault. I just tried with electron26-bin and that seems to work fine, any strong opinions against depending on electron=26? Anyone else experiencing segfaults?

Do huddle, both the audio/video conference and screen sharing, work without xorg-xwayland, or it's required? Pure wayland with "--ozone-platform-hint=auto" is still of no help? What about "--enable-features=WebRTCPipeWireCapturer" and/or "--enable-webrtc-pipewire-capturer"?

Even with xorg-xwayland, any other special config? I guess if using xwayland, then the ozone platform config shouldn't be used, or is it harmeless?

Can I say, even by using xwayland, that slack-electron works fine on wayland then?

Any hint from slack on when pure wayland will be feasible?

Thanks for the package

Please consider adding an optdepends on xwaylandvideobridge to work around the wayland screen sharing issue.

Cheers