Package Details: signal-desktop-beta 7.58.0beta1-1

Git Clone URL: https://aur.archlinux.org/signal-desktop-beta.git (read-only, click to copy)
Package Base: signal-desktop-beta
Description: Signal Private Messenger for Linux - Beta version.
Upstream URL: https://signal.org
Keywords: secure-messenger signal signal-desktop
Licenses: GPL3
Conflicts: signal-desktop-beta-bin
Submitter: Edu4rdSHL
Maintainer: Edu4rdSHL
Last Packager: Edu4rdSHL
Votes: 16
Popularity: 0.147354
First Submitted: 2020-08-17 19:09 (UTC)
Last Updated: 2025-06-11 19:35 (UTC)

Dependencies (33)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 Next › Last »

reclusivesage commented on 2021-08-28 21:38 (UTC) (edited on 2021-11-16 21:59 (UTC) by reclusivesage)

Edit (Nov 16, 2021): I accidentally fixed this issue by relinking to the Signal mobile app, after I moved to a new device.

I wonder if anyone else is having an issue with Signal Desktop Beta. (I doubt the cause is from the AUR package, but I'd like to be sure.)

For the latest two versions (v5.16.0-beta.1 and v5.15.0-beta.2) in the past 3 days, I haven't been able to use the Beta version because a warning in a red box shows up with the contents of:

This version of Signal Desktop has expired. Please upgrade to the latest version to continue messaging. Clicl to go to signal.org/download

This is what it looks like: https://i.imgur.com/DlssuXc.jpg

The bad part about this warning is that I an unable to do anything once this warning comes up.

I am not sure if I unintentionally set this glitch because 3 versions ago (in v5.15.0-beta.1) - I was able to change the Beta's settings to notify if there are new updates or to attempt auto-updating - and then the options subsequently disappeared in the latest 2 versions, potentially leaving me unable to change these now gone options. (Since I'd have to use AUR methods to update, not get an auto-update, like in Windows or MacOS.)

reclusivesage commented on 2021-08-14 01:44 (UTC)

Thanks for fixing it quickly!

Edu4rdSHL commented on 2021-08-14 01:26 (UTC)

reclusivesage, fixed.

reclusivesage commented on 2021-08-14 01:18 (UTC)

Hm, I seem to be getting another validity check error:

==> Validating source files with sha512sums...
    signal-desktop-beta-5.14.0beta2.tar.gz ... Passed
    signal-desktop-beta.desktop ... FAILED
    expire-from-source-date-epoch.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Edu4rdSHL commented on 2021-07-19 09:27 (UTC)

reclusivesage, fixed.

reclusivesage commented on 2021-07-19 01:57 (UTC) (edited on 2021-08-14 01:17 (UTC) by reclusivesage)

What can I do? I received a validation error when running $ makepkg -si:

==> Validating source files with sha512sums...
    signal-desktop-beta-5.10.0beta1.tar.gz ... FAILED
    signal-desktop-beta.desktop ... Passed
    expire-from-source-date-epoch.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

Edit: Thanks for fixing it! (Didn't get to say earlier)

Edu4rdSHL commented on 2021-06-22 23:29 (UTC)

Signal Dekstop Beta releases are being handled in a wrong way resulting in the stable version being more up to date than the beta one at some points, please vote https://github.com/signalapp/Signal-Desktop/issues/5358 if you think that it needs to be fixed.

Edu4rdSHL commented on 2021-06-04 08:11 (UTC)

Build in a clean chroot environment, it's clearly a problem on your end and not a packaging issue. Signal Desktop doesn't build with nodejs > 15.

fow0ryl commented on 2021-06-04 08:03 (UTC)

Could not build signal-desktop-beta 5.4 or 5.3 This package requires nodejs-lts-fermium, while other packages required nodejs. -> Deadlock in package dependencies

MajorMayer commented on 2021-06-01 06:51 (UTC)

All right i will report in on their Github.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 Next › Last »