Search Criteria
Package Details: slack-electron 4.41.105-1
Package Actions
| 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: | 29 |
| Popularity: | 0.45 |
| First Submitted: | 2020-07-05 17:00 (UTC) |
| Last Updated: | 2024-12-14 22:18 (UTC) |
Dependencies (6)
- electron31
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- libx11 (libx11-gitAUR)
- libxkbfile
- libappindicator-gtk3 (optional) – for notification indicator in the status bar on GNOME
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next › Last »
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
electron20rather thanelectron; this will avoid things breaking whenelectronmoves 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?
languitar commented on 2022-08-18 11:25 (UTC)
Is anyone else with a wayland setup experiencing crashes when trying to start a screenshare since a few weeks? For me, after selecting the output to share, slack always terminates with
Fatal Wayland protocol error 3 on interface xdg_surface (object 72). Shutting down.
juanignaciosl commented on 2022-08-01 08:36 (UTC) (edited on 2022-08-01 08:39 (UTC) by juanignaciosl)
For people using Gnome and Wayland, this might be helpful for getting better performance and window decorations (top bar and so on): edit
~/.config/electron17-flags.conf/and add the following lines:flying-sheep commented on 2022-06-22 16:05 (UTC)
When I try to log into a workspace, I get an infinite loop of the app opening a tab and the tab opening a new instance of the app lol.
a172 commented on 2022-04-08 23:19 (UTC)
@lmartinex-mirror, electron apps have a tendency to run in xwayland. To run them natively in wayland, use the args
--enable-features=UseOzonePlatform --ozone-platform=wayland. Try it with these args and see if you get the blank screen.lmartinez-mirror commented on 2022-04-07 16:36 (UTC)
It worked for me under Wayland, sway. If it works better for other people under electron17, you can revert it.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 Next › Last »