Arch Linux User Repository

I'm successfully using slack-desktop so far (thanks to your hint mierota) - was it just then switching back to slack-electron (I haven't tried) which stopped working, or some time after installation & sign-in slack-desktop stopped working too?

No I didn't. I was able to login through slack-desktop and get back to electron version, but now even this doesn't work. Can't login at all.

pacman -Q | grep elect

electron 1:25-1 electron21 21.4.4-1 electron24 24.6.2-1 electron25 25.2.1-1

I've updated the package to run with an up-to-date electron version (25).

I currently don't have time to investigate the login issues further at the moment, let me know if you find a solution.

Cannot login with this version (4.33.73-1) or the older ones. Had to install slack-desktop, login, and then again install slack-electron which then didn't ask me to login (I was logged in with slack-desktop version).

Found Slack (unusually) logged out this morning; logging back in through the browser as required doesn't seem to trigger anything, and manually clicking 'open in app' just launches another instance also not signed in.

Not sure if this is an app/electron issue not picking up the 'magic link' (grep processes for 'slack://' or 'magic-link' while it's trying to launch) or a server-side issue?

I've tried with electron22 (v22.3.16) as it was and also electron[25] (v25.2.1) with the same result.

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