Arch Linux User Repository

I see your point @alerque, but I believe most of the time plain latest "electron" is just fine. The app will run with no issues. And pinning the electron version brings other problems, like when the app still uses a pretty old version of electron which has been already dropped from the Arch repos. And if you want it, you'll have to grab it from AUR, sometime by building it. So if latest "electron" works flawlessly, why not using it, rather than waiting for the dependency to get too old.

Now if latest "electron" doesn't work anymore, then yes, there's no option but pinning to the latest one that works fine, or if possible the one the app was built against.

That's just my $0.02... But there's the option to attempt to always match the electron version used to build the app, but this in my mind is not needed, not always at least...

@je-vv I think you miss-understood me. I didn't say that it bundled electron, I sadi that it was compiled against a specific version of electron. The dependency on this package was electron which was bogus because the ASAR file installed here will not run under just any-old version of Electron. Some versions may work, others will not, and pinning it to the one it was built against is best. Hence the dependency here got update to electron29. I understand how the system Electron stuff works just a bit: I'm the Arch maintainer for all Electron versions. I reported the electron as bogus because I started getting bug reports on that package that it was breaking this one, when in fact it was this package that had an incorrect dependency.

@alerque, not true, first the app.asar from slack is bein executed with the system electron (provided by Arch, or derivative distro), you can take a look at slack.sh. Moreover, if you take a look at the PKGBUILD (or you do pacman -Ql slack-electron) you'll notice the electron that comes from the deb slack package is not copied over.

slack-electron is different than slack-desktop in the sense that it uses the system electron provided by the distro, and not the inner electron coming with the original deb package.

The electron dependency in this package is bogus. Its a binary app compiled by upstream against a specific version of Electron, it is not expected to run using any/current version of Electron only the one is was built for.

The only thing is that we need to keep an eye on each following slack release, to see when slack stops disabling sreen sharing. To avoid doing the substitution from the entire app.asr. Greetings !

@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, :)