Arch Linux User Repository

Co-maintainer spots are open.

@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

The issue with using specific versions of electron, is also they bring dropped by Arch, like electron16 did. So it's always wise to keep trying newer electron versions and test if it works, when becoming available. Otherwise you can end up with the same freetube issue. The version upstream hadn't changed for a while, and it works fine with electron20, but on AUR it still uses electro16, :(

So, sticking with particular electron version is also dangerous. I do prefer depending on, and using electron (latest one) unless for some reason it breaks the package, and only then stick with the latest that work...

You're probably right. I'll pin to electron20.

Just something to consider is pinning the depends to electron20 rather than electron; this will avoid things breaking when electron moves to 21.