Package Details: slack-electron 4.38.115-1

Git Clone URL: https://aur.archlinux.org/slack-electron.git (read-only, click to copy)
Package Base: slack-electron
Description: Slack Desktop (Beta) for Linux, using the system Electron package
Upstream URL: https://slack.com/downloads/linux
Keywords: desktop electron slack
Licenses: LicenseRef-SlackProprietary
Conflicts: slack-desktop
Provides: slack-desktop
Submitter: WhiredPlanck
Maintainer: carsme
Last Packager: carsme
Votes: 26
Popularity: 1.58
First Submitted: 2020-07-05 17:00 (UTC)
Last Updated: 2024-05-03 04:08 (UTC)

Dependencies (6)

Required by (1)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »

OJFord commented on 2023-03-17 10:42 (UTC) (edited on 2023-03-17 10:50 (UTC) by OJFord)

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

je-vv commented on 2023-01-24 17:47 (UTC)

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.

sime commented on 2023-01-06 18:37 (UTC)

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 ?

npfeiler commented on 2022-11-22 02:25 (UTC) (edited on 2022-11-22 02:38 (UTC) by npfeiler)

proposal for

--ozone-platform-hint=auto

je-vv commented on 2022-09-30 02:31 (UTC)

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

lmartinez-mirror commented on 2022-09-30 01:53 (UTC) (edited on 2022-09-30 01:54 (UTC) by lmartinez-mirror)

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

jonathon commented on 2022-09-02 09:23 (UTC)

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

gmontanola commented on 2022-08-24 21:21 (UTC)

@languitar I'm experiencing the same here. Already tried to use different Electron versions (17 to 20) but all fail to work. Using 17 does not lead to a crash but instead I screenshare a gray screen.

kyckl1ng commented on 2022-08-21 19:44 (UTC)

Works fine for me on electron 20 so far. Also Wayland window decorations were fixed in 20.0.2 which finally makes for a kinda flawless Wayland experience. Unfortunately I know too little about electron to tell if it will get backported.

Maybe consider bumping electron version here?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »