Package Details: slack-desktop 3.2.1-5

Git Clone URL: (read-only)
Package Base: slack-desktop
Description: Slack Desktop (Beta) for Linux
Upstream URL:
Licenses: custom
Submitter: ogarcia
Maintainer: ogarcia
Last Packager: ogarcia
Votes: 320
Popularity: 14.672469
First Submitted: 2015-10-19 09:59
Last Updated: 2018-08-17 06:52

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Kunda commented on 2018-08-17 10:55

From the Manjaro forums: maybe the flatpack is the way to go?

ogarcia commented on 2018-08-17 09:56

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

sispus commented on 2018-08-17 09:42

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

ogarcia commented on 2018-08-17 09:31

@sispus please, use pacman -Syyu to update your system. Current version of glibc is 2.28-4. -> ->

sispus commented on 2018-08-17 09:25

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.

ogarcia commented on 2018-08-17 08:43

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

marmotz commented on 2018-08-17 08:33

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

ogarcia commented on 2018-08-17 06:53

@taolin96 hack dropped! Thanks for report!

taolin96 commented on 2018-08-17 00:21

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

prosoitos commented on 2018-08-16 19:31

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