Package Details: slack-desktop 4.43.51-1

Git Clone URL: https://aur.archlinux.org/slack-desktop.git (read-only, click to copy)
Package Base: slack-desktop
Description: Slack Desktop (Beta) for Linux
Upstream URL: https://slack.com/downloads
Licenses: custom
Submitter: ogarcia
Maintainer: ogarcia
Last Packager: ogarcia
Votes: 613
Popularity: 4.13
First Submitted: 2015-10-19 09:59 (UTC)
Last Updated: 2025-04-08 06:20 (UTC)

Pinned Comments

ogarcia commented on 2020-02-06 11:44 (UTC) (edited on 2020-02-06 11:44 (UTC) by ogarcia)

Please, don't ask for add lsb-release as dependency. In Arch Linux this package is not needed to run Slack Desktop.

And before asking for any other dependency as make or patch or whatever, please read the wiki.

Latest Comments

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

MarsSeed commented on 2023-06-17 15:36 (UTC) (edited on 2023-06-17 15:38 (UTC) by MarsSeed)

Please remove the included Chrome/Electron engine, and use the Arch repo version as dependency.

Like in this package: slack-electron.

SailReal commented on 2023-05-26 10:12 (UTC)

@mlerota it is exactly the same on my device. If I start screensharing on 4.32.122-1 using Gnome Wayland I get a SIGSEGV. On 4.29.149-1 it works as expected :)

mlerota commented on 2023-05-17 08:03 (UTC)

Crashes when you try to share the screen. Both versions 4.32.122-1 and 4.31.155-1. The one that works is 4.29.149-1. On Gnome Wayland.

ogarcia commented on 2023-03-17 11:40 (UTC)

@boredland @OJFord The desktop file will not be modified any more than it already is because Arch Linux packages should always be as identical as possible to the upstream. The current modifications it has are simply because they are wrong in the original.

On the other hand I am not going to put a 'setconf' dependency to simply modify a line, when by default you already have the patch command because it is mandatory to install any AUR package.

That said, this does not prevent you from modifying the desktop file as you wish. Simply copy the file from /usr/share/applications/slack.desktop to $HOME/.local/share/applications and modify it.

mkdir -p $HOME/.local/share/applications
cp /usr/share/applications/slack.desktop $HOME/.local/share/applications
vim $HOME/.local/share/applications/slack.desktop

Once you have modified it, the .desktop of your home will be used instead of the one in /usr/share/applications/ (You may need to restart the session).

OJFord commented on 2023-03-17 10:29 (UTC)

@ogarcia I see you accepted @bordeland's patch, any chance of a release with that?

Though, if I understand correctly, I can just add it to the .desktop entry myself in the mean time. Any way to have it read $XDG_CONFIG_HOME/electron-flags.conf? Since that's what the wiki points to to enable wayland for all Electron applications, but it seems it isn't picked up by Slack.

boredland commented on 2023-03-01 07:45 (UTC)

hi there! I'd like to propose that we add ozone hints to the .desktop file. Afaik this should work fine for x11 and wayland alike and would be just a quality of life improvement (and render tons of other aur packages useless for most clients).

I created a little patch here: https://github.com/boredland/aur-slack-desktop/commit/69bf61cb53026a3b3eac2e2cc2f28154d8566328

LuisDamiano commented on 2022-12-30 15:25 (UTC)

@BSoD38 Had the same issue, I removed the slack-desktop.patch file without noticing. It worked fine after I rm'd the whole folder and cloned the repo again.

BSoD38 commented on 2022-12-06 08:39 (UTC)

Since 4.29 released, building the app became impossible (I retried on Manjaro's latest stable version that released today).

I get the following output :

Preparing...
Cloning slack-desktop build files...
Generating slack-desktop information...
Checking slack-desktop dependencies...
Resolving dependencies...
Checking inter-conflicts...

Building slack-desktop...
==> Making package: slack-desktop 4.29.149-1 (Tue 06 Dec 2022 09:33:11 CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found slack-desktop-4.29.149-amd64.deb
==> ERROR: slack-desktop.patch was not found in the build directory and is not a URL.
Failed to build slack-desktop

I've switched back to using the flatpak version for now, but it's not ideal.

Subject-17 commented on 2022-11-29 01:46 (UTC) (edited on 2022-12-17 10:17 (UTC) by Subject-17)

@eigenstryker:

❯ yay -S slack-desktop --editmenu --mflags slack-desktop
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  slack-desktop-4.29.144-1

  1 slack-desktop                    (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> A
:: Deleting (1/1): /home/MYUSER/.cache/yay/slack-desktop
:: (1/1) Downloaded PKGBUILD: slack-desktop
  1 slack-desktop                    (Installed) (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> n
:: (1/1) Parsing SRCINFO: slack-desktop
  1 slack-desktop                    (Installed) (Build Files Exist)
==> PKGBUILDs to edit?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> A

 -> $EDITOR is not set
 -> Add $EDITOR or $VISUAL to your environment variables
==> Edit PKGBUILD with?
==> nvim

On line 6, change pkgver=4.29.144 to pkgver=4.28.182

On line 18-19, change b2sums=('BLAH' 'ANOTHER BLAH') to b2sums=('0246dd6ee6983dafad166e41faab30d495c39ad1a66c63bb59174ca1cbe12e275cd961a6873dcbbbe0a497cfeb5786265fcaf85be4134a444d5c2376f3b3753b667ac8b5237d74cbc643433148ec0a4f8ddfe65276d6029cc6941b464938e6c37f904c2369cbe14ca3f1819dd')

You can find this out by clicking in the git repo above, going to logs, and back to the [last working commit.] (https://aur.archlinux.org/cgit/aur.git/commit/PKGBUILD?h=slack-desktop&id=14ed7b0d37e57daf680e5a0d932d5643337c44d0) Although if you copy-pasted my --skipinteg flag from the provided command, it shouldn't matter what you put in place of b2sums.

eigenstryker commented on 2022-11-28 16:40 (UTC)

Will someone please explain the b2sum workaround steps to get Slack working? @Subject-17 @Stephen2