Arch Linux User Repository

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.

@andy44 did you read the pinned comment? have you bothered to check if your system complies the prerequisites?

Need patch to run this PKGBUILD

$ makepkg -sri                                                                                                                                                               
==> Making package: slack-desktop 4.27.154-1 (Thu 30 Jun 2022 11:07:28)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found slack-desktop-4.27.154-amd64.deb
  -> Found slack-desktop.patch
==> Validating source files with b2sums...
    slack-desktop-4.27.154-amd64.deb ... Passed
    slack-desktop.patch ... Passed
==> Extracting sources...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
/home/<user>/aur-programs/slack-desktop/PKGBUILD: line 25: patch: command not found
==> ERROR: A failure occurred in package().
    Aborting...

Anyone else experiencing tray/notification issues?

When the app is minimized to the tray and I get a message, I get a desktop notification with the "View Msg" "link" and when I click it, it does bring the app to the foreground, but it also bring the next app in the tray (in this case qbittorrent) to the foreground.

I haven't looked at code, but I would imagine there's probably 2 code paths doing the same thing to bring the app to the front, but in 1 path there's an off-by-one error?

@lostpolaris thanks you saved my day :) I was not able to add another workspace otherwise.

Opening multiple workplaces at the same time works for me.

For anyone who is using KDE as their environment, here is a solution to help you log in through the desktop app

https://stackoverflow.com/questions/70867064/signing-into-slack-desktop-not-working-on-4-23-0-64-bit-ubuntu

Hi,

leaving this here since it bummed me out for a longer time:

With 4.23 and even 4.24 Google SSO did not work for me anymore as @33Fraise33 suggested on another thread, what works is opening the SSO link in Firefox instead of Chrome.

I also noticed 4.23.0 not working with my companies SSO. I had to downgrade back to 4.21.1 to get slack working again.

Can confirm issue with current upstream version (4.23.0-1). Logging in to workspaces is, at best, flaky. Downgrading to 4.21.1-1 solves the issue (0829f7d72650).

Version 4.23.0-1 does not allow me to login via Google SSO from the browser. Downgraded to 4.21 and it worked there.

@rgcv same here... but for me it never launches when I use the "Ozone Platform" options

@fardog appreciate the feedback. my solution was to downgrade it, 4.22 seems... decent enough, and I need screensharing in general to work on wayland, for one (daily driving sway).

@rgcv i can confirm the same unfortunately, segfault under wayland; works fine when running via xwayland though, so i'm just falling back to that for now. i don't have a fix, just a confirmation that you're not alone in the issue.

Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[3902:1221/091652.602765:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is
[3902:1221/091652.606507:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[12/21/21, 09:16:52:663] info:
╔══════════════════════════════════════════════════════╗
║      Slack 4.23.0, linux 5.15.10-arch1-1 on x64      ║
╚══════════════════════════════════════════════════════╝
[12/21/21, 09:16:52:664] info: Configured logger via
{
  "enableConsoleTransport": true,
  "identifierOverride": "webapp-service-worker-console",
  "shouldUseNewBackend": false,
  "loggerInstanceCount": 2
}
[12/21/21, 09:16:52:664] info: Predefined values for process
{
  "NODE_ENV": "production",
  "platform": "linux",
  "type": "browser",
  "timeZone": "America/Los_Angeles",
  "PACKAGE_MANIFEST.productName": "Slack",
  "PACKAGE_MANIFEST.version": "4.23.0",
  "PACKAGE_MANIFEST.commit": "8c4b013",
  "PACKAGE_MANIFEST.branch": "HEAD"
}
[3860:1221/091652.706566:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[3860:1221/091652.706621:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
/home/<redacted>/.dotfiles/bin/slack: line 3:  3860 Segmentation fault      (core dumped) /usr/bin/slack --enable-features=UseOzonePlatform --ozone-platform=wayland $@

Electron packaging guidelines say that if packages comes with prebuilt Electron it should go to /opt https://wiki.archlinux.org/title/Electron_package_guidelines#Directory_structure

@wooque No. Read the FHS.

Shouldn't AUR packages go to /opt, I noticed that all packages I installed are in /opt except Slack

@rgcv isn't the electron version bundled in this package?

Consider using a downgraded version of electron (say electron 15, haven't had many issues with it). With the most recent version of electron (16 at time of writing), I am now only having issues if I enable the WebRTCPipeWireCapturer feature :\ Guess I can't have screensharing

I am also seeing the segmentation fault trying to run on wayland with 4.23.0

Most recent update (4.23.0) breaks if trying to run it in pure wayland mode (with WebRTC enabled).

$ slack --enable-features=UseOzonePlatform --ozone-platform=wayland
Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[2167056:1215/105110.561823:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[2167056:1215/105110.561846:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property
[2167110:1215/105110.591670:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is
[2167110:1215/105110.596663:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[2167056:1215/105110.672593:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[2167056:1215/105110.672640:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
zsh: segmentation fault (core dumped)  slack --enable-features=WebRTCPipeWireCapturer,UseOzonePlatform --ozone-platform=wayland

edit: might have been an inconsistent state in my system, it seems it launches okay... albeit only sometimes. If anyone else runs into something, do tell.

Got this upon start of 4.22.0-1:

$ slack
[3324:1125/082737.173451:ERROR:process_singleton_posix.cc(419)] readlink failed: Not a directory (20)
[3324:1125/082737.173557:ERROR:process_singleton_posix.cc(256)] readlink(~/.config/Slack/SingletonLock) failed: Not a directory (20)
[3324:1125/082737.173582:ERROR:process_singleton_posix.cc(256)] readlink(~/.config/Slack/SingletonLock) failed: Not a directory (20)
[3324:1125/082737.173590:ERROR:process_singleton_posix.cc(280)] Failed to create ~/.config/Slack/SingletonLock: Not a directory (20)
[3324:1125/082737.173602:ERROR:process_singleton_posix.cc(419)] readlink failed: Not a directory (20)
[3324:1125/082737.173610:ERROR:process_singleton_posix.cc(256)] readlink(~/.config/Slack/SingletonLock) failed: Not a directory (20)

I only see ~/.config/Slack which is a file instead of a directory. Deleting that file allows starting, though. Sounds like an improper migration to me.

@FizzyGalacticus, I can't reproduce this error, but I have a ~/$USER/.config/Slack. Maybe try manually making ~/$USER/.config/Slack/local-settings.json. My version of that file just contains {"lastElectronVersionLaunched":"14.0.0","electronFeatureOverrides":[]}, but I would try it with an empty file first. If that doesn't work, try the slack-electron package instead.

Ever since I updated to the lastest version, I'm receiving the following errors:

Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
Couldn't save to /$USER/.config/Slack/local-settings.json: ENOENT: no such file or directory, open '/$USER/.config/Slack/local-settings.json.24822100'
Error: ENOENT: no such file or directory, mkdir '/$USER/.config/Slack/storage'
    at Object.mkdirSync (node:fs:1324:3)
    at w._init (/usr/lib/slack/app.asar/dist/main.bundle.js:342:4874)
    at new w (/usr/lib/slack/app.asar/dist/main.bundle.js:342:4188)
    at new b (/usr/lib/slack/app.asar/dist/main.bundle.js:342:34641)
    at Tx (/usr/lib/slack/app.asar/dist/main.bundle.js:188:26694)
    at configureStore (/usr/lib/slack/app.asar/dist/main.bundle.js:188:27177)
    at U2 (/usr/lib/slack/app.asar/dist/main.bundle.js:188:50506)
    at B2 (/usr/lib/slack/app.asar/dist/main.bundle.js:188:51419) {
  errno: -2,
  syscall: 'mkdir',
  code: 'ENOENT',
  path: '/$USER/.config/Slack/storage'
}
[85690:0100/000000.746763:ERROR:vaapi_wrapper.cc(1104)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[85690:0100/000000.746796:ERROR:vaapi_wrapper.cc(1051)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint VAEntrypointVLD
[85690:0100/000000.746808:ERROR:vaapi_wrapper.cc(1104)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[85690:0100/000000.746816:ERROR:vaapi_wrapper.cc(1051)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint VAEntrypointVLD

Note: I replaced my actual username with $USER

It looks like it's trying to create files/directories at the root of the filesystem instead of in my home directory.

Searching for these errors has lead me absolutely nowhere, and I'm hoping someone may have a solution? I looked at the main.bundle.js file in hopes I could manually update to just put in my home dir, but since it's minified js, it's very difficult to follow.

There's a 4.20 update and they seem to have decided it is no longer beta (at least in their url).
New pkgver: 4.20.0
New sha256: b08207389246837536ea769425d458411c08dc6802ffaae9249092e387461ce5
New url: https://downloads.slack-edge.com/releases/linux/{pkgver}/prod/x64 /${pkgname}-${pkgver}-amd64.deb"

Hi. I am having an issue with the font on code blocks - it looks like I am missing a font, but I am not sure which one. Does anyone know?

Hi, when I start or receive a slack call, the audio settings don't pick up an input (tried multiple microphones). Other applications don't run into this issue (zoom, google meet, chime, to name a few). Has anyone seen this issue before and resolved it? I'm wondering if I need to configure pulseaudio in anyway for this specific application to work with my audio inputs?

Unicode input (ctrl + shift + u) does not seem to work anymore. It could be a change at the Slack side, but just thought I give a heads up to anyone else looking

@alecmev I had the same issue. It appears to be an issue with firefox, not electron. Setting the environment variable GDK_BACKEND=wayland for firefox when I launch it seemed to fix the issue for me.

Can't open links as of a week or two ago. Discord works, so this isn't an Electron and/or Wayland issue. My default browser is Firefox, and I have $BROWSER set to firefox, and xdg-open works fine by itself. Every time I click on a link in Slack, a new sh /usr/bin/xdg-open process is spawned, and they all stay there even after terminating Slack. Any pointers?

Is missing a dependency: libappindicator-gtk3

Without this, it doesn't show the notification indicator in the status bar on Gnome.

I figured out the problem with the browser issue, Slack tries to xdg-open but the xdg-mime query (L827 of /usr/bin/xdg-open on my system) returns

/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US) brave-browser.desktop

Seems like some dingus at Slack decided to set the locale to "en-US" instead of "en_US" like all our locale.gen's support

The workaround is the same, just set the BROWSER manually, since xdg-open falls back to BROWSER if it can't find the correct *.desktop file to open the file (and it can't because the "warning" in the message above is part of the desktop filename returned, which obviously will fail to parse). xdg-open by default falls back to a few default web browsers if it can't find an app, L928-930 on my system:

    BROWSER=www-browser:links2:elinks:links:lynx:w3m
    if has_display; then
        BROWSER=x-www-browser:firefox:iceweasel:seamonkey:mozilla:epiphany:konqueror:chromium:chromium-browser:google-chrome:$BROWSER

This also explains why everybody saw firefox being used instead of their default browsers, or google-chrome. Not sure why this doesn't affect slack-electron...

Why is it called Beta ? So confusing, really sounds like the nightly-build, where in fact is the latest stable build ... confusing

Setting the browser environment variable to fix the Firefox link bug didn't work for me. The links still opened in Firefox and caused Firefox to crash for some reason. Uninstalling Firefox made Slack unable to open links at all. So I tried the slack-electron package thinking that maybe the Slack team just borked their bundled electron build. Sure enough, slack-electron opens links in google-chrome just like I wanted it to. Hope this helps someone else.

@goddva, thanks for the reply and workaround.

For someone who might need:

vim /usr/share/applications/slack.desktop
[Desktop Entry]
...
Exec=env BROWSER=brave /usr/bin/slack -s %U
....

@victortrac @Thornycrackers @lira - I had the same issue with Slack not using my default browser. A quick look of processing spawning, I do see that it uses xdg-open <URL>. But all my settings are correct, so it should open in Chrome... but no luck.

However, Slack do use the BROWSER environment variable if its set, so a BROWSER=google-chrome slack would be my workaround until it gets fixed, or I do have more time to see what really happens...

After the install, slack doesn't seem to launch at all - I'm not really sure how to proceed here. I tried installing 4.10.3, but that didn't launch on my system either!

EDIT: Deleted my ~/.config/slack then tried again - slack now launches

4.11.x broke the default browser for me too. I have the brave as my default and it was opening all the links in firefox. I downgraded to 4.10.3 and everything is working again.

@victortrac 4.11.x broke the default browser for me. I have Firefox as my default and it was opening all the links in chrome. I downgraded to 4.10.3 and everything is working again.

@doctorcolossus - I've had similar issues upgrading slack in the past. Wiping out ~/.config/Slack fixed it for me.

Did 4.11.x break the default browser for anyone? My default browser is brave, but after upgrading to slack 4.11.x, all links started opening in Firefox. All other applications are obeying the mime apps file properly, but slack-dekstop 4.11 completely ignores it. Downgrading to slack-desktop 4.10.x fixes the issue.

Thanks for verifying, @je-vv. Weird though. My system is also fully up-to-date.

@doctorcolossus, it's working as it used to, at least for me, no issues with the upgrade. Though I have a pretty up to date system though.

@skolind, I use LXQt, and the slack icon shows normal, as it has been doing so, on the tray. Though it's been several releases back it doesn't show up on the legacy tray, but rather in what's called now a days notification area, and some years back was called modern tray.

All electron apps have icon misbehaving since quite a while back though, not just slack. Clicking on the tray icon no longer shows/hides the app, one has to right click on the tray icon and then select show/hide or their equivalents for the app. But that's electrons' fault I believe.

I got a segmentation fault trying to run slack after upgrading to this latest release (4.11.0-1). I tried reinstalling a couple of times and rebooting and reinstalling, but it persisted in segfaulting. Did nobody else experience that? I've downgraded back to 4.10.3-1 for now...

I installed and it's working like a charm, but the icon for the tray output no i3(bar) does not show. The app shows up (i can right click etc) but the icon is not showing - it's transparent. Have anyone else experienced this?

@B2Pi I had the same issue with the generic icon with KDE. Installing libappindicator-gtk3 from the community repo resolved the issue for me.

@greenisagoodcolo and anyone else having the JS appTeams error - I had to delete my ~/.config/Slack directory, which allowed Slack to start normally. I then had to re-login to all of my workspaces and re-set some of my preferences.

Hello,

I started getting an error about "appTeams" on open as of last week. I tried removing and reinstalling, didn't work without patch, tried copying patch (but the patch in the repo had git history which when removed failed shasum test), then tried removing the patch from the makepkg and reinstalling.

I'm still getting the error on open, preventing use of app.

A javascript error occured in the main process

Uncaught exception: TypeError: cannot read property 'appTeams' of undefined at validateTeamsState (/usr/lib/slack/resources/app.asar/dist-main.bundle.js:2:1930329) at reduce (/usr/lib/slack/resources/app.asar/dist/main.bundle.js:2-1930925"...

and onwards. Full pic of error message here - can't copy it from this weird electron window (https://imgur.com/a/tRDWcxV)

Is anyone else encounterign this error on the "appTeams" property preventing use of the applications?

@valentjedi It works fine, thx :)

@brsvh I had the same thing. Upon looking at logs it seems that slack assumes lsb-release installed and doesn't handle its absense. Installing lsb-release fixed the issue for me.

It seems to depend on wget as well. I had a segmentation fault (so far not sure why), but this is what I've got:

Cannot upload crash dump: cannot exec /usr/bin/wget

Unexpected crash report id length
Failed to get crash dump id.
Report Id: 
zsh: segmentation fault (core dumped)  slack

After I installed and run it, I get some electron and node error, then the slack will freeze and don't have GUI window too.

Initializing local storage instance at path: /home/brs/.config/Slack/local-settings.json
Failed to get path for key, this may be expected: /home/brs/.config/autostart
(node:244863) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(electron) 'BrowserWindow.getDevToolsExtensions' is deprecated and will be removed. Please use 'session.getAllExtensions' instead.

Installed, and working fine, but the icon in my task switcher is the generic one. Perhaps someone knows how to fix this (I'm using LXQT, and, concomitantly, lxqt-app-switcher)?

@maverick1: Please read the pinned comment, especially the Prerequisites part of the linked wiki page.

I got an error while installing it from yay

==> Starting package()...
/home/maverick/.cache/yay/slack-desktop/PKGBUILD: line 24: patch: command not found
==> ERROR: A failure occurred in package().
    Aborting...
error making: %!s(func() string=0x55b9433c2880)

Without a notification daemon running, Slack will freeze when trying to send a notification.

This issue shows up in other Electron apps too https://github.com/electron/electron/issues/14006.

To fix this install and launch dunst (or any other notification daemon).

Same for me - it hangs all the time, becoming non-interactive, if i wait for couple minutes - it works, but after a while - same problem. What interesting is that the same happens with mailspring app. Probably connected to electron or other library which is used in both apps.

Slack becomes non-interactive for me after a few minutes.

https://s.natalian.org/2020-05-05/slack.mp4

Any ideas how to fix this? Using 4.4.2-1.

Thank you in advance!

For anyone having issues with Slack crashing in Gnome-Shell, make sure that you don't include it in any Auto Move Windows rule. When it initiates a call it spawns a separate window which will crash the whole of Gnome-Shell.

Hi, when I close slack, and it get minimized on the tray, "clicking" on the tray doesn't bring it up at all. I have noticed this for the last 2 versions, and I seem to remember it did work. What I don't remember ever working is that the slack window is up, then there's no way to make it minimize in the tray, by "clicking" the tray. The only way to minimize it the tray was to close window through the WM close button, but that's not doing anything anymore...

Is there a way to work around any of the mentioned issues, or at least the one related to minimizing to tray? Thanks !

@leinher done

Hey Guys, slack logged about 2 million lines in 8 work days. When I open journalctl the only thing I see is info: [DESKTOP-SIDE-EFFECT] Update from desktop for keys ["windows"]. (I use GDM 3.34.1)

I changed the slack.desktop file: Exec=/usr/bin/slack -s %U to mute slacks info/debug log to the journal. Could you please set that as a default?

New release coming > https://slackhq.com/simpler-more-organized-slack (2020-03-18)

Not yet available for those wondering > https://slack.com/release-notes/linux (latest 4.3.2 was released on 2020-01-30)

@laulicus slack works fine here without lsb-release

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.

Please add lsb-release package as dependency. Without that package, slack doesn't start.

Hey Guys, Slack is behaving weirdly. It's got rendering issues. I use awesome window manager. Whenever I move out of slack and open the window again, all I see is my desktop wallpaper and just the window of slack. Any ideas about how to fix it?

you need to include patch as a build dep please

Actually, never mind, I was able to sign in. Just didn't realize that the sign-in page opened in another workspace of my window manager (Sway) :)

Hi,

Please remove the dependency on libcurl-compat and the preload. Slack works fine with libcurl4 :)

Building with rua, I get this error

./usr/bin/slack: Can't set user=0/group=0 for usr/bin/slack bsdtar: Error exit delayed from previous errors.

I had to add --no-same-owner to bsdtar to make it extract. Is it only me?

I tried it again randomly and It's decided to work.

Problem: After launching, clicking "Sign In" or "get started" does nothing.

Version: 4.2.0

Desktop Environment: KDE

Comments: Running from the terminal, nothing particularly concerning can be found. I do get the below warning on start

warn: (T00000000) UnknownFetchManager requested 1 objects but received 0. Missing objects: T00000000

and on clicking sign-in, the below is printed which seems normal fine

info: Got window.open with URL: /ssb/signin

I've tried modifying settings in ~/.config/Slack/local-settings.json to change the log level or redirect to console (I believe the error may be in the web console it's probably using). I also tried deleting this directory.

I'm actually guessing this is a problem with the desktop client itself or my system, but I'm not sure.

I was having the same problem with a blank screen running on XFCE. Seems to have gone away with the update on 12/06.

Anyone else getting a blank screen on recent builds when running in Sway?

@ogarcia That's fair enough tbh, would you be against the idea of adding it as an optional dependency? Also @msenol I think your addition to the arch wiki broke the wiki page for slack

Sorry @circleous and @alsetema, but this is AUR (Arch Linux User Repository). I cannot add dependencies to this package that Arch don't need.

I have added information into wiki https://wiki.archlinux.org/index.php/Slack-desktop

@ogarcia, I think this only happens on Archlinux based distros derivative, the problem occured on my laptop running artix linux and It's not happening on vanilla arch linux.

@ogarcia I experienced this error both in Manjaro and Artix Linux at the time. I got the slack support team involved as well, concluding this was the issue; it might not be a bad idea to add it as a dependency just to be sure

cheers!

@circleous I don't have installed lsb-release and Slack works without problem

please add lsb-release to dependecy, Slack window won't show up according to this error by @alsetema,

warn: Couldn't get Linux distro info from lsb_release, trying fallback to get L inux distro info { "error": { "stack": "Error: Command failed: lsb_release -a --short\n/bin/sh: lsb_release: command not found\n\n at ChildProcess.exithandler (child_process.js:299:12)\n at ChildProcess.emit (events.js:182:13)\n at ChildProcess.EventEmitter.emit (domain.js:442:20)\n at maybeClose (internal/child_process.js:9 62:16)\n at Socket.stream.socket.on (internal/child_process.js:381:11)\n at Socket.emit (events.js :182:13)\n at Socket.EventEmitter.emit (domain.js:442:20)\n at Pipe._handle.close (net.js:606:12)" , "message": "Command failed: lsb_release -a --short\n/bin/sh: lsb_release: command not found\n", "killed": false, "code": 127, "signal": null, "cmd": "lsb_release -a --short", "stdout": "", "stderr": "/bin/sh: lsb_release: command not found\n" },

ok @ogarcia. My linux is Manjaro / Gnome. It may be related to the Manjaro.

@msenol NO. There is a lot of issues caused by install libappindicator-gtk3. If you want install it, you do, but I don't recommend.

pacman -Sy libappindicator-gtk3

solves the issue with tray icon. Can we add this add a dependency?

@ewhitestone Minor version ahead? The latest version is 4.1.1 that match with package version. If you consider that the package is outdated you can use the button Flag package out-of-date and provide the URL of latest version.

How can I help keep this up to date? The current version seemed to have a memory leak, but I upgraded to the latest pretty easily by modifying the version number and hash in the PKGBUILD file.

Is this something that I can contribute back? Slack is a minor version ahead now.

Hey guys, in my computer the tray icon is not always showing up that blue ball anymore when there are new messages - sometimes not even the red one for messages directed to me. Is anybody else experiencing this issue?

To fix the very small tray icon in HiDPI displays, you can add

env XDG_CURRENT_DESKTOP=Unity

To your desktop file. It'd be good to include the fix in the AUR package unless it breaks non-HiDPI displays.

@raul dark mode works for me on the current version 4.0.2-2

is there a channel besides git where we can get this version? https://slackhq.com/dark-mode-for-slack-desktop

I have to add that the packet lsb-release is a dependency of slack. I recently had a problem where Slack's window would not launch at all because it was failing to run the command "lsb-release -a" (see the log below). After installing it the program finally managed to launch.

The logs:

warn: Couldn't get Linux distro info from lsb_release, trying fallback to get L inux distro info { "error": { "stack": "Error: Command failed: lsb_release -a --short\n/bin/sh: lsb_release: command not found\n\n at ChildProcess.exithandler (child_process.js:299:12)\n at ChildProcess.emit (events.js:182:13)\n at ChildProcess.EventEmitter.emit (domain.js:442:20)\n at maybeClose (internal/child_process.js:9 62:16)\n at Socket.stream.socket.on (internal/child_process.js:381:11)\n at Socket.emit (events.js :182:13)\n at Socket.EventEmitter.emit (domain.js:442:20)\n at Pipe._handle.close (net.js:606:12)" , "message": "Command failed: lsb_release -a --short\n/bin/sh: lsb_release: command not found\n", "killed": false, "code": 127, "signal": null, "cmd": "lsb_release -a --short", "stdout": "", "stderr": "/bin/sh: lsb_release: command not found\n" },

Hope it helps

@bakgwailo This fixed it for me, too. I'm also on a reasonably fresh Arch install, so I'm not sure how this got into my local.conf

So, just as a last follow up - I had a bunch of 'junk' in my /etc/fonts/local.conf config file:

<?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <match> <edit mode="prepend" name="family"><string>Noto Sans</string></edit> </match> <match target="pattern"> <test qual="any" name="family"><string>serif</string></test> <edit name="family" mode="assign" binding="same"><string>Noto Serif</string></edit> </match> <match target="pattern"> <test qual="any" name="family"><string>sans-serif</string></test> <edit name="family" mode="assign" binding="same"><string>Noto Sans</string></edit> </match> <match target="pattern"> <test qual="any" name="family"><string>monospace</string></test> <edit name="family" mode="assign" binding="same"><string>Noto Mono</string></edit> </match> </fontconfig>

Moving this file (mv /etc/fonts/local.conf /etc/fonts/local.conf.bak) solved all of my font issues, including the latest version of Slack. Clean install, don't really remember touching it, but it definitely was forcing everything into the Noto world.

I was able to "fix" the font issue by downgrading to 3.4.2-1 (no ttf-loto installed or anything else, noto-fonts still installed), if that helps anyone else.

@pauliokas Where did you end up putting that? Can't get it to work under /etc/fonts/conf.d/ or ~/.config/fonconfig/fonts.conf

My fc-match Slack-Lato stays as:

NotoSans-Regular.ttf: "Noto Sans" "Regular"

even with an fc-cache -f

@klusark is true, removed gconf dependency

@ogarcia gconf is not needed as a dependency

Hi,

anyone also having problems with slack starting today? The moment I start it it just freezes my desktop so you cannot even move the cursor anymore. Have to switch to another tty and kill the process. No clue why.

So I fixed the bold fonts by installing ttf-lato and adding the following to my fontconfig:

<alias>
  <family>Slack Lato</family>
  <prefer><family>Lato</family></prefer>
</alias>

This is not a proper fix, though -- it just makes Slack usable. The problem is that Slack doesn't use the fonts that are packaged with it. Does anyone know why?

I get the following output:

x1carbon6 :: ~ » fc-match Slack-Lato

Vera.ttf: "Bitstream Vera Sans" "Roman"

@lordchaos If you do:

fc-match Slack-Lato

do you see any bold fonts?

I only get:

NotoSans-Regular.ttf: "Noto Sans" "Regular"

I have the following packages installed, but the 'bold font' issue doesn't seem to affect me. I can see bold typefaces fine in Slack.

slack-desktop 4.0.1-1

noto-fonts 20190111-2

ttf-lato 2.015-3

Same issue with the fonts here, but removing noto-fonts is not really a viable solution. Anyone got any other suggestions?

It seems that removing "noto-fonts" package fixed the bold issue for me.

The bold issue is due to conflicting fonts. In my case the set of Noto fonts I'm using (required by Brave) are interfering with Slack Lato fonts.

Bold fonts work fine for me with package 4.0.0-1, as well as in Slack's web app using google-chrome-beta 71.0.3578.30. I'm on Manjaro 18.0.4 with i3.

No bold fonts here either. Same if I use slack on a Chromium-based browser. On Firefox the bold fonts are there.

I'm also no longer seeing bold fonts, is there a new dep that's not being pulled in?

Bold font seems to work for me. I didn't do anything special outside of pulling the latest PKGBUILD and rebuilding and installing.

After 4.0.0 update there is no bold font in app anymore. Is it an upstream bug?

Never mind, apparently I no longer can use Slack behind the corporate firewall at one of my client's locations. It works fine from home.

@ogarcia: yes, I uninstalled slack-desktop and removed the ~/.config/Slack directory. I re-installed the application but with the same results. I'm using KDE 5.16.3 by the way.

@lordchaos do you try removing the ~/.config/Slack directory and restarting? (take note that you lose your configuration)

Version 4 no longer works for me; I starts without error (I no longer see a splash screen though). I get an empty, white window with a menu on top.

Hi, I got a "libffmpeg.so not found" and was able to solve it with: sudo chmod 644 /usr/lib/slack/libffmpeg.so

It might be worth looking at.

You should have installed the base-devel group when building from AUR: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

Missing patch in Dependencies PKGBUILD: line 25: patch: command not found

Looks like there is a bug fix in Xfwm that may address this:

https://bugzilla.xfce.org/show_bug.cgi?id=15399

And a workaround posted here (using xprop):

https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1827302/comments/11

So we have to wait for the Xfwm fix to get into Arch or use the workaround until then. Or rebuild Xfwm with the patch yourself...

Slack icon is missed in list of opened apps. Using Xfce. Does anyone have suggestion?

Is gconf still needed? I removed it locally, and slack still seems to work fine

warning: could not get file information for usr/lib/slack/src/static/.gitkeep warning: could not get file information for usr/lib/slack/ui_resources_200_percent.pak warning: could not get file information for usr/lib/slack/v8_context_snapshot.bin warning: could not get file information for usr/lib/slack/version warning: could not get file information for usr/lib/slack/views_resources_200_percent.pak warning: could not get file information for usr/share/applications/slack.desktop warning: could not get file information for usr/share/licenses/slack-desktop/LICENSE warning: could not get file information for usr/share/pixmaps/slack.png

+1 for xdg-utils as a dependency, 3.3.8 moved the sign-in as a browser re-direct.

+1 to adding xdg-utils to dependencies for sign-in

Update:

I was able to resolve the crash issue by deleting the ~/.config/Slack directory and restarting.

Ping: @Pauligrinder @paulequilibrio

Having the same issue as @Pauligrinder & @paulequilibrio.

I have the same problem as paulequilibrio, any idea on how to fix that?

I have an issue with slack-desktop 3.3.8-1 where the mouse scroll wheel stops working after a few hours. Quitting and restarting fixes the problem until it reoccurs. Is anyone else hitting this?

I've looked around and I don't see where to report the bug upstream. Can someone please point me to where I can do so? In the meantime, I've reverted back to 3.3.7-1 and the problem has not occurred since.

Have a strange issue with slack. After time of using slack it window became white and even slack reboot doesn't help. Reboot of system helps, but is not good.

Had issues with signing in, login url won't open. Please, add xdg-utils to dependencies, installing it resolved my issue.

Not working for me anymore...

I always get the error:

(electron) 'app.makeSingleInstance(cb)' is deprecated. Use 'app.requestSingleInstanceLock() and app.on('second-instance', cb)' instead.

Does anyone know how to solve it?

I am using the community edition of Manjaro with the i3wm. Every time I open slack, it asks me for the password of my computer. Anyone knows why?

Honestly not sure why, but Today phone calls and desktop sharing is working for me... Not sure if a logout or reboot was required after 1st install (I shut the laptop down last night)...

Just in case:

% ldd /usr/bin/slack ... libnode.so => not found ... libffmpeg.so => not found ...

Not sure if that has anything to do with the disability to receive/make calls

Hello, the phone calls are not working for me, however my co-workers are telling me, on ubuntu is works fine. So I'm wondering why this AUR package doesn't allow me to use phone calls. Is there a missing dependency not requested either as optional?

@mat250

Adding that prefix (XDG_CURRENT_DESKTOP=Unity) to the .desktop command field didn't stick until a reboot, but it worked, thank you.

@MirandaStreeter I have the same problem. I fix it following this : https://forum.kde.org/viewtopic.php?t=139804#p400696

The notification icon is too large (the old one too) so the "red point" notification on slack's icon wasn't displayed

Since the latest update (3.3.7-1) with their logo change, the tray icon in my KDE/Plasma looks to be glitched out. It looks entirely white with a black plus sign covering the entire thing.

My libappindicator is up to date, and no other icons looks to be effected. I'm not entirely sure what's causing this. Trying to troubleshoot to no avail. Anyone else facing this issue?

Everything else about Slack is working just fine.

@1ouis with 3.3.4-1 it's all fixed for me even with gpu acceleration enabled.

I'm seeing slack coredumps when my screen goes into suspend and slack is in a different workspace on i3wm/x11.

You can reproduce using xset dpms force suspend while viewing another workspace.

alias slack='slack --disable-gpu' works for now I guess.

@christianmtr I have same problem as you with all electron apps. Seems that electron doesn't work well in wayland and have several screen issues (flickers, black windows, etc), the best workaround is use X11.

UPDATE: Try adding --disable-gpu as option in command line. Maybe this bug is related: https://github.com/electron/electron/issues/12820

I have some probles with this package. I'm running it in gnome-shell over wayland, some times the application window becomes to black (not all window). Do you have this problem?

I can't get the icon (the application icon shown in xprop, tint2, and alt-tab) working. I am using openbox. Has anyone else had this problem?

Has anyone found a way to get the tray indicator working on Gnome 3.30? I'm using https://extensions.gnome.org/extension/615/appindicator-support/ and tried setting XDG_CURRENT_DESKTOP=Unity but to no avail.

Was getting libnotify errors "cannot connect to proxy" that were crashing it. Installed notification-daemon and added it to startup and looks like it fixed that error, but now it's crashing without output. Probably an upstream problem.

Is there a way to start minimized? I want it to auto start + load into the polybar tray but not load the window every time I log in. Arch Linux/i3-gaps/polybar. Thanks

@adrianmo No, patch should not be added as dependency. You need to have base-devel installed:

https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

@ogarcia patch needs to be added as a dependency. Thanks for the package :)

@kunda for me Flatpak was working (except audio) until the last update, where it doesn't open and starts consuming lots of RAM :\

From the Manjaro forums: https://forum.manjaro.org/t/testing-update-2018-08-16-kernels-l1tf-firefox-mate-virtualbox/55209/8 maybe the flatpack is the way to go?

@sispus I don't know why you have packages on hold, but holded packages never update and that is the problem.

I already did it. "there is nothing to do" I saw this line in my pacman.conf file: HoldPkg = pacman glibc manjaro-system

@sispus please, use pacman -Syyu to update your system. Current version of glibc is 2.28-4. -> https://www.archlinux.org/packages/core/x86_64/glibc/ -> https://www.archlinux.org/packages/core/x86_64/lib32-glibc/

Hi, Pamac didn't show me any glibc 2.28 update. There is a lock symbol on glibc 2.27.3 package installed from regular repositories on pamac, I think it means I cannot remove the package. I cannot install glibc-git AUR package also, says:

could not satisfy dependencies: removing glibc breaks dependency 'glibc=2.27' required by lib32-glibc

I refreshed mirror list and cleaned package caches using pamac, no help.

@marmotz I think that your AUR helper is not working well. Current version of glibc stable is 2.28-4, and you can install it from pacman.

@ogarcia Impossible to install glibc>=2.28-4

Please fix dependencies. It's working if I remove ">=2.28-4" but I dont know if it's a good solution.

@taolin96 hack dropped! Thanks for report!

the problematic glibc 2.28 commit is now reverted in the arch glibc package, so I think you can drop the glibc 2.27 hack for this package

Everything is working fine for me, but I noticed a series of these in my logfiles, so I thought that I would report, in case:

Aug 16 10:20:05 prosoitos systemd-coredump[11074]: Process 11059 (slack) of user 1000 dumped core.

follows a series of stack trace, then

-- Subject: Process 11059 (slack) dumped core
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 11059 (slack) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.

@Marcel_K you were right! A simple git clone ... and makepkg, makepkg --install ... did the trick.

Thank you

@Noah-Huppert: you're probably using an AUR helper, aren't you? Please try using the default method by running makepkg yourself.

I got the following error installing:

aura >>= Building `slack-desktop`...
loading packages...
warning: downgrading package glibc (2.28-1 => 2.27-3)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing glibc (2.27-3) breaks dependency 'glibc=2.28' required by lib32-glibc

Could you check if it's now working with glibc-2.28 because a new version of electron have been shipped, and since the last update, slack is working but microphone didn't work anymore when I call someone.

I am having the same issue as tnto. For the time being you can install snapd, via the aur. Then following the instructions here https://snapcraft.io/slack. Make sure to sudo systemctl start snapd and to uninstall previous slack installations.

I've update slack and the error message change.

Now is: stack smashing detected : <unknown> terminated</unknown>

Why would you remove glibc 2.28 from your system? The workaround just lets you use the new glibc version, which is needed for many other packages, and the previous version only for this application.

After installing this glibc-patched slack my system fails to boot into GDM. Had to do systemd.boot=rescue.target init=/bin/bash to even access the machine. journalctl -r reported a lot of errors about glibc during gdm startup. Removing slack-desktop and reinstalling glibc 2.28 returned my system back to normal.

I am using KDE Plasma, and I cant run it after update, I get "[1] 17092 segmentation fault (core dumped) slack".

Thank you for the very quick patch!

Package patched to work with upgraded glibc! Take note that now the package takes up more space because have glibc-2.27-3 inside!

I had the same issue launching Slack. Downgrading glibc and lib32-glibc solved the issue.

# pacman -U /var/cache/pacman/pkg/lib32-glibc-2.27-3-x86_64.pkg.tar.xz /var/cache/pacman/pkg/glibc-2.27-3-x86_64.pkg.tar.xz

The problem that @archelaus is describing is related to glibc-2.28, most electron apps are affected. see the following threads:

https://bugs.archlinux.org/task/59550

https://www.reddit.com/r/archlinux/comments/9573e2/psa_use_flatpak_for_proprietary_applications_to/

Skype AUR has included the workaround described by wbdana and now it works. Maybe you could do the same so the package works automatically while this bug is solved upstream.

https://aur.archlinux.org/packages/skypeforlinux-stable-bin/

I have the same issue as @archelaus. I don't have a solution for it, but I see that the problem is not quite new and you can find something about it in the Google.

Another temporary solution would be to install slack from a snap package.

Running slack returns : Segmentation fault (core dumped)

@wbdana thank you very much. It worked!

@lira I also had the same problem. @hashstat 's solution (with @andris 's edit) worked for me (thanks you two!).

So what I did was:

mkdir /opt/glibc-2.27
sudo bsdtar xf /var/cache/pacman/pkg/glibc-2.27-3-x86_64.pkg.tar.xz --cd /opt/glibc-2.27

sudo patchelf --set-interpreter /opt/glibc-2.27/usr/lib/ld-linux-x86-64.so.2 --set-rpath \$ORIGIN:\$ORIGIN/lib/:/opt/glibc-2.27/usr/lib/ /usr/bin/slack

Then I could run slack normally.

I cannot start the slack. I have the same problem of @bararchy. How can I resolve it?

One can avoid need to specify LD_LIBRARY_PATH by setting also -rpath with patchelf

patchelf --set-interpreter /opt/glibc-2.27/usr/lib/ld-linux-x86-64.so.2 \
    --set-rpath \$ORIGIN:\$ORIGIN/lib/:/opt/glibc-2.27/usr/lib/ \
    /usr/bin/slack

Note that slack-desktop already uses -rpath and /opt/glibc-2.27/usr/lib/ must be added to it as in command above

Thanks @hashstat! I am also facing a problem with links not opening on the browser.

@bararchy Are you launching slack with the modified LD_LIBRARY_PATH as in @hashstat's comment in the end? Because I had the same issue, before I did that.

Thanks @hashstat. There's only one more problem: Clicking links doesn't seem to open the browser.

Thanx @hashstat. It is work for me.

Seems slack-desktop fails to find libffmpeg for me:

https://gist.github.com/bararchy/c9c0fd76d173d5ab1c26cd62cbcc3dbc

also libnode.

Going to /usr/lib/slack i can see both libs.

@polo tyvm! I also was given the URL on freenode - should have asked there first. Thanks again

Arch package archive https://archive.archlinux.org/repos/2018/08/01/core/os/x86_64/

@hashstat N00b question here, but how do I get my hands on glibc-2.27-3-x86_64.pkg.tar.xz? I don't have it in my cache?

I found a workaround that allows slack to use the previous version of glibc without downgrading.

Do the following as root:

# Extract glibc 2.27-3
mkdir /opt/glibc-2.27
bsdtar xf /var/cache/pacman/pkg/glibc-2.27-3-x86_64.pkg.tar.xz --cd /opt/glibc-2.27

# Patch the slack binary to point to glibc-2.27
pacman -S patchelf
patchelf --set-interpreter /opt/glibc-2.27/usr/lib/ld-linux-x86-64.so.2 /usr/bin/slack

Now you can launch slack as any user: LD_LIBRARY_PATH=/opt/glibc-2.27/usr/lib/ slack &>/dev/null &

@raul Downgrading glibc and lib32-glibc worked for me -- thanks! @jardragon901 Here's how I did it (I had a dependency of lib32-glibc, likely for steam):

https://gist.github.com/adambair/f47d7b7fed82f7889a0e0f3e026de4a8

seems i can't downgrade my glibc because of a dependency, hopefully this can be fixed without having to wait for slack to put out a new release

@Svenstaro, found the breaking change: glibc 2.28-1 downgrading to 2.27-3 fixes slack

@Svenstaro yep, seems to be related to a recent gcc update and /usr/lib/slack/libnode.so

Can't start slack. Basically it just segfaults right at the start. Due to missing symbols, gdb is pretty much useless. I'm running full [testing]. Anybody else getting this?

I've hit https://github.com/electron/electron/issues/8127. As suggested in the comments, adding the extra --disable-gpu-driver-bug-workarounds --enable-native-gpu-memory-buffers parameters into the .desktop file fixed the issue for me.

@petr.nehez you can override the desktop file with your own copy. Do the following.

# Copy to your .local folder
cp /usr/share/applications/slack.desktop ~/.local/share/applications

# Edit it
vim ~/.local/share/applications/slack.desktop

Now you can set the Exec entry to anything you want:

Exec=env XDG_CURRENT_DESKTOP=Unity LD_PRELOAD=/usr/lib/libcurl.so.3 /usr/bin/slack %U

It might worth to consider also a patch for Plasma tray icon by adding XDG_CURRENT_DESKTOP=Unity prefix.

https://forum.kde.org/viewtopic.php?f=289&t=139804&sid=126b7c810ffe90ca3247790b364770ea&p=400696#p400696

I'm having issues with launching slack-desktop after quitting it via my WM.

Basically, slack launches successfully on my system after a reboot. If I select file -> quit from the menubar, I can launch slack again and it still works just fine.

The problem seems to be that if I kill slack using my WM bindings (XMonad in this case), it fails to launch again until I reboot my system. The error I get is as follows:

$ slack
Creating Slack Application
dbus[19291]: dbus message iterator has already been closed, or is uninitialized or corrupt
  D-Bus not built with -rdynamic so unable to print a backtrace
Failed to get crash dump id.
Report Id: 5b373b889ed27
[1]    19291 abort (core dumped)  slack

Downgrading to 3.1.1 fixes this - not sure if this is an upstream issue or what.

Of course, it does not work…

My PKGBUILD attempt is here in case anyone is interested: https://paste.xinu.at/N0w5z/

To (fail to) run it, you have to type electron /usr/lib/slack/app.asar in a terminal (providing a slack in /usr/bin is of course doable, but there is no point yet).

I’m going to propose a very different way of packaging this, because in the end I believe this is just yet another electron app. If I succeed, this will land in [community].

I am having issues with time messages are sent. Any message i send has the sent time set to GMT+0, instead of GMT+1. However the recipient recieves it in the normal time. The recipient is running a windows client. Running on KDE Plasma. Issue not fixed with the last upgrade.

Also seeing the same issue as mheese and codedmart

Also seeing the same issues as mheese. Downgraded for now.

The 3.2.1-3 version starts up fine for me, but freezes after half a minute around. The log files have not been very helpful so far. I have no issues when I downgrade to 3.1.1-1.

Any suggestions on how to debug this?

@WorMzy What system do you use without gtk3 actually? :D

@ulgens Works for me on KDE Plasma. Do you have libappindicator-gtk3 installed? That breaks the tray icon for riot-desktop

@WorMzy Done. Added missing gtk3 dependency. ;-)

The gtk2 dependency should've been replaced with gtk3.

slack
slack: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory

:(

Back to the web client for me.

KDE system tray got broken with latest release. It tries to bigger image than it should be, it doesn't fit in the area and gets cropped. Also, clicking on system icon doesn't open the application window anymore.

@z3ntu Yes, you're right. Done!

gtk2 dependency can be removed (and gtk3 added) with the newest version ("ldd /usr/lib/slack/slack | grep gtk")

Please don't send out-of-date requests with current 3.2.0-beta.2 version. Wait for 3.2.0 final.

Perhaps you need to change the package description if that's the case.

Slack Desktop (Beta) for Linux

Edit: Uhh, I see now. It's a beta for a beta. How meta...

I have the same error with the weird freezes. It does the exact same thing with gitter, maybe it’s a third-party lib.

The app freezes everytime there's a notification. This is really annoying and I have to wait for the window manager to throw the Force quit dialogue and then close the app...

Is there a way I can help debug and identify this issue? I am on Manjaro if that helps.

I am also having an issue with spellcheck no longer working.

Hi, anyone have idea how to start up minimized?

Since 3.0.5 update, my spellchecker stopped to work. Is there any solution for it?

Had an issue with some emojis not working. Installing an emoji font resolved it:

https://wiki.archlinux.org/index.php/Fonts#Emoji_and_symbols