Package Details: signal-desktop-bin 1.27.4-1

Git Clone URL: (read-only)
Package Base: signal-desktop-bin
Description: Private messaging from your desktop
Upstream URL:
Keywords: messenger secure
Licenses: GPL3
Conflicts: signal
Provides: signal-desktop
Submitter: jbbr
Maintainer: jbbr (buzo)
Last Packager: jbbr
Votes: 166
Popularity: 3.923915
First Submitted: 2017-10-31 20:04
Last Updated: 2019-10-10 19:58

Pinned Comments

tinxy commented on 2019-05-31 15:47

Signal Desktop does not work if your /tmp is mounted with option noexec -- see

As a workaround one can use an alternative dir like so:

mkdir -p "$HOME"/tmp/signal

export TMPDIR="$HOME"/tmp/signal


buzo commented on 2018-10-30 10:50

Apparently upstream removes the old package immediately when releasing a new version. So if you encounter a 404 error when building, just click on “Flag package out-of-date” above. Thanks!

Latest Comments

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

modulitos commented on 2018-09-18 21:09

@jbbr Thank you for the info. I'll remember to flag the package for future 404's.

And thanks to everyone who maintains this package! I am feeling the positive vibes :)

ogasser commented on 2018-09-18 08:35

buzo: Ok, thanks for keeping the package up-to-date!

buzo commented on 2018-09-18 08:34

ogasser: Thanks, we're already having our own cron jobs. The update just occurred at night for both of us.

ogasser commented on 2018-09-18 08:21

buzo: It's just a suggestion and might reduce the number of "I'm getting a 404 for this package" postings ;) If you would like I can also run the cronjob and send the email to you and jbbr.

buzo commented on 2018-09-18 08:16

ogasser: The time-to-realease was five hours and 14 minutes. That is not bad for an AUR package, isn't it? What do you expect?

ogasser commented on 2018-09-18 08:05

A suggestion to spot new versions sooner: Can any of the package maintainers run a cron job checking if the latest version is still available on the server and send an email if it is not? This way we could reduce the time-to-release of this AUR package.

jbbr commented on 2018-09-18 06:14

@modulitos: This happens when a new minor release is available on the upstream APT-Repository. For some reason they immediately make the previous release unavailable (404) which causes this PKGBUILD to fail with an 404 error. I updated the package to 1.16.1 which should fix this issue.

Please use the "Flag package out-of-date" action in the future, thanks :)

modulitos commented on 2018-09-18 05:20

I am getting an error when updating this package, caused by a 404 at the url:

Is anyone else having this issue as well? Perhaps I am missing something?

Jonhoo commented on 2018-09-16 16:00

@Perseids I try to keep relatively few AUR packages installed for exactly that reason :) But I do see your reasoning, and the resulting security is probably good enough for most users!

Perseids commented on 2018-09-15 21:45

@Jonhoo: Personally, I'm content with downloading it over HTTPs and having it verified with the additional checksums in the PKGBUILD file. It's not like any other executable I install would be any less capable of completely screwing the security of my system. I would not go through the extra trouble for each and every other AUR package, so why bother here?