Arch Linux User Repository

@carsme, with current slack version, 4.33.73-1, slack segfaults on me every now and then. I'm testing with latest plain electron, which currently corresponds points to 25.2.1-1 on my system, and so far so good. So it seems using whether plain electron, or electron-25 is fine, and using electron-22 is not as stable...

Warning: Segfaults on launch for the latest version of Electron. Works with 22.3.12-2.

Slack has always been a mess, but it's a bit buggy for logging in through Google Apps or other OAuth. There has been other issues in the past with this.

Anyway, what worked for me was:

1. Use Firefox as the default browser
2. Remove the -s option from the .desktop file
3. Added the launch flags I wanted.
4. Moved ~/.config/Slack, as it wouldn't work with slack-desktop -> slack-electron for whatever reason.
5. Launched slack via the same command I used in the .desktop, signed in via Firefox
6. Waited 30 seconds for Slack to load, which I used to think about how fun Electron is. There are now two slack instances.. Close the first when the second Slack instance has loaded
7. Sent a test message to myself, loaded a couple of channels to make sure everything had loaded.
8. Close Slack normally, hoping it had saved the configuration.
9. Reopen Slack as normal, everything seems okay.

You can then change it back to your previous browser after.

If you need to change your default browser, this command should do the trick:

1. Get your current default browser: xdg-settings get default-web-browser
2. Change to Firefox xdg-settings set default-web-browser firefox.desktop
3. Do the above steps
4. Change back to the value in #1.

@lmartinez-mirror you could also bump and pin to the known-working electron22 (which is currently in the provides list for electron). That will again prevent possible incompatibility issues for which pinning was originally committed to this PKGBUILD, afaik.

However, as with electron20 that results in annoyances when electron eventually updates and gets a different tagged electronXX in provides: users will have to atomically upgrade electron and install electronYY (where XX is a new version, and YY is the older version currently in use by slack-electron).

In that case I will unpin the electron dependency.

@lmartinez-mirror I agree with @je-vv personally, this is a rolling release distro, pin it if/when it breaks (and is slower to fix properly).

As it is this is the only package I have using electron20, so it's kind of a technicality that it uses the 'system' Electron package - it still installed its own. (What I actually care most about at the moment though is using global electron-flags.conf, so fine.)

Edit - actually, as @je-vv said in follow-up below, it's not working at all for me with electron20, loads a blank white page. Seems fine unpinned, picking up 22, so far.

Hello, current 4.29.149-1 slack-electron, being called by current 20.3.10-1 electron20, shows empty channels, although it does connect.

The fix is to use current 22.0.3-1 electron, instead of electron20. So just changing the dependency in the PKGBUILD, and changing from electron20 to just electron on slack.sh fix the current issues, if one wants to update the package. Otherwise, just changing from electron20 to electron on /usr/bin/slack does the trick as well.

Hi, I still have this the bug when maximize on Wayland, I have electron 20.3.8 and flag on file .config/electron-flags.conf -ozone-platform-hint=auto --enable-features=UseOzonePlatform --enable-features=WaylandWindowDecorations

Do I miss something ?

proposal for

--ozone-platform-hint=auto