Package Details: signal 1.16.3-1

Git Clone URL: (read-only)
Package Base: signal
Description: Signal Private Messenger for the Desktop
Upstream URL:
Keywords: messenger secure
Licenses: GPL3
Conflicts: signal-desktop, signal-desktop-beta, signal-desktop-bin
Provides: signal
Submitter: onny
Maintainer: dbirks (Jake)
Last Packager: dbirks
Votes: 155
Popularity: 8.287105
First Submitted: 2016-08-17 22:58
Last Updated: 2018-10-17 20:33

Latest Comments

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

je-vv commented on 2018-10-19 06:11

Found the issue. As it was associated to installing packages, it ended up due to the "npm" cache set to an unreachable directory (left from another malformed AUR package probably). But to prevent such issues, could you apply the following patch?

diff -Naur signal-orig/PKGBUILD signal/PKGBUILD
--- signal-orig/PKGBUILD        2018-10-19 00:56:34.046423706 -0600
+++ signal/PKGBUILD     2018-10-19 00:57:16.887711270 -0600
@@ -33,6 +33,7 @@
 build() {
   cd "${pkgname}-git-repo"

+  export npm_config_cache="$srcdir/npm_cache"
   _npm_prefix=$(npm config get prefix)
   npm config delete prefix

This would make npm cache isolated just for signal, and not be affected for prior dirty caches, neither leave dirty caches. And for sure it would prevent using wrong caches, as I was doing. That'd be much appreciated.

BTW, if you're wondering, the environment variable is a more robust solution, than finding out current cache setting, storing it, changing it, and restoring it back. The reason is that the build process can crash in between changing it and restoring it, leaving the npm cache mistakenly configured moving forward for any other nmp stuff using cache.

Thanks !

je-vv commented on 2018-10-18 05:57

Getting failure when attempting to build 1.16.3-1:

ALL DONE $ grunt Running "exec:build-protobuf" (exec) task $ yarn build-module-protobuf $ pbjs --target static-module --wrap commonjs --out ts/protobuf/compiled.js protos/*.proto && pbts --out ts/protobuf/compiled.d.ts ts/protobuf/compiled.js

installing chalk@^2.4.1 installing jsdoc@^3.5.5 installing uglify-js@^3.3.25 installing espree@^3.5.4 child_process.js:644 throw err;

Error: Command failed: npm --silent install chalk@^2.4.1 jsdoc@^3.5.5 uglify-js@^3.3.25 espree@^3.5.4
at checkExecSyncError (child_process.js:601:13)
at Object.execSync (child_process.js:641:13)
at modInstall (/home/vasqueja/.cache/aurutils/snapshot/signal/src/signal-git-repo/node_modules/protobufjs/cli/util.js:129:19)
at Object.exports.setup (/home/vasqueja/.cache/aurutils/snapshot/signal/src/signal-git-repo/node_modules/protobufjs/cli/util.js:156:5)
at Object.<anonymous> (/home/vasqueja/.cache/aurutils/snapshot/signal/src/signal-git-repo/node_modules/protobufjs/cli/pbjs.js:7:6)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
error Command failed with exit code 1. info Visit for documentation about this command. error Command failed with exit code 1. info Visit for documentation about this command. Exited with code: 1. Error executing child process: Error: Process exited with code 1. Warning: Task "exec:build-protobuf" failed. Use --force to continue.</anonymous>

Aborted due to warnings. error Command failed with exit code 3. info Visit for documentation about this command. error Command failed with exit code 1. info Visit for documentation about this command. ==> ERROR: A failure occurred in build(). Aborting...

It seems like trying to install some stuff fails. I'm building this time at home, to prevent any firewall/proxy issues at work. Any hints? Thx !

je-vv commented on 2018-09-09 00:12

I've been experiencing with 1.16, that when trying to delete messages, if signal has just been launched, then messages get deleted. But after a few seconds from being launched, then the messages remain, which is really weird. Anyone facing this? Would this be an AUR built signal problem, or rather upstream?

Update: Reported upstream already.

alexandria commented on 2018-08-25 03:17

Just a heads up: if anyone is having problems with the latest updates (as of 1.15.5, but actually including previous updates) having a regression where the UI is veeeery slow... that's a known bug you can find here:

Since the old PKGBUILDs for 1.14.3 are broken now, I forked a PKGBUILD to downgrade to 1.14.3 for anyone who needs it:

I accidentally locked myself out of uploading this on AUR. Sorry to anyone inconvenienced by that. This message will be posted on both Signal packages to make sure anyone who needs it sees it! :)

Jake commented on 2018-08-15 20:59

@je-vv: I have looked at the history of the Gruntfile and it still runs the "getExpireTime" task, which uses gitinfo. Also the grunt gitinfo plugin is the same version as it was in January.
It works fine though on my system with the tarball (outside of a git repo), so far i can't reproduce this error with any setup or version, but i don't see a reason why it should work now for people that encountered this problem in the past. The bug report(2376) got closed with basically "assemble the tasks yourself, if you don't like how we do it" and i would rather avoid replicating the build steps in the pkgbuild or patching the build system just for this... so see it as fairly permanent.

je-vv commented on 2018-08-15 18:14

Is it still the case that using the released tarball doesn't work? I've read in past comments about it, but wondering if that's a permanent condition, or rather a temporary one... Thx !

Jake commented on 2018-08-10 22:45

Yes, this is indeed required, thanks for the notice Daniel. I have added it with the 1.15.4 release.

daniel.sch commented on 2018-08-10 22:10

It works again after manually installing openssl-1.0, so this should probably be added as a dependency.

Jake commented on 2018-08-10 10:23

WaltzOfWoe: Thanks a lot, that does really work. Not a newer version, but the normal sqlcipher release instead of the fork.

Also it does not include all the openssl binaries anymore. The readme states "On Linux we dynamically link against the system OpenSSL." That is perfect!

WaltzOfWoe commented on 2018-08-10 02:15

Bug Manually set dependency @journeyapps/sqlcipher to newer version and it works