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

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

jbehmel commented on 2019-09-04 15:57

Hello, could you please provide support for firejail? In my understanding the .desktop file should simply point to '/usr/local/bin/signal-desktop'

buzo commented on 2019-06-28 14:59

Really? I guess we need to wait for 1.25.3 then. The beta version is in a separate AUR package, so I don't think it is a good idea to switch to beta here.

sseneca commented on 2019-06-28 12:04

I get the blue screen / start issue on 1.25.1-2

jbbr commented on 2019-06-27 23:37

There is a "blue screen"/start issue with 1.25.2. See for details.

Please avoid updating until 1.25.3 is available.

1.25.3beta contains a fix:

b.vandenheuvel commented on 2019-06-27 07:57

buzo: Yes, it is up to date. I am only holding back cuda to the latest 10.0.

galvez_65 commented on 2019-06-26 14:54

OK 1.25.2 is working now, I had to uninstall 1.25.1 first, purge .config/Signal and then install 1.25.2, and relink my desktop. Thanks

jbbr commented on 2019-06-26 14:32

Works for me too. Unfortunately there is not much we can do from here. Previous deb-packages are not available on upstream server anymore. This bug should be reported on the upstream bug tracker.

There are some similar bug reports for 1.25.2 already: &

Status "Need information", maybe you can help out @kriation, @galvez_65

kriation commented on 2019-06-26 13:36

I updated to 1.25.2 this morning, and experienced the same blue screen as @galvez_65 and @b.vandenheuvel.

I purged ~/.config/Signal, and restarted. Once I re-linked with my device, the application worked properly again.

buzo commented on 2019-06-26 12:36

b.vandenheuvel: Strange. Is your System up-to-date (sudo pacman -Suy)? Do you hold back any packages? (IgnorePkg or IgnoreGroup in /etc/pacman.conf)

b.vandenheuvel commented on 2019-06-26 11:37

buzo: I'm experiencing the same issue as galvez_65 with 1.25.2-1.