Package Details: signal-desktop-beta 7.52.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.44
First Submitted: 2020-08-17 19:09 (UTC)
Last Updated: 2025-04-19 00:51 (UTC)

Dependencies (33)

Required by (0)

Sources (2)

Latest Comments

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

presidentwolf commented on 2022-02-21 18:04 (UTC)

Build is failing with: 

[build:release   ]   • building        target=deb arch=x64 file=release/signal-desktop-beta_5.33.0-beta.1_amd64.deb
[build:release   ]   ⨯ cannot execute  cause=exit status 127
[build:release   ]                     errorOut=/home/person/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86_64/lib/ruby/bin.real/ruby: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
[build:release   ]

Sounds like this was removed recently from glibc and is now available from libxcrypt-compat in AUR. Can we add this as a dep?

reclusivesage commented on 2022-01-13 03:17 (UTC)

I also get a similar error that behaves the same.

This is what I see when trying to debug Signal Desktop Beta in a terminal emulator:

$ signal-desktop-beta 
Set Windows Application User Model ID (AUMID) { appUserModelId: 'org.whispersystems.signal-desktop-beta' }
NODE_ENV production
NODE_CONFIG_DIR /usr/lib/signal-desktop-beta/resources/app.asar/config
NODE_CONFIG {}
ALLOW_CONFIG_MUTATIONS undefined
HOSTNAME undefined
NODE_APP_INSTANCE undefined
SUPPRESS_NO_CONFIG_WARNING undefined
SIGNAL_ENABLE_HTTP undefined
userData: /home/uSER/.config/Signal Beta
config/get: Successfully read user config file
config/get: Successfully read ephemeral config file
making app single instance
{"level":30,"time":"2022-01-13T03:10:48.933Z","pid":747808,"hostname":"hOST","msg":"crashReporter: enabled"}
[748294:0112/221049.036925:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
^C^C

Edu4rdSHL commented on 2022-01-12 23:25 (UTC) (edited on 2022-02-02 23:08 (UTC) by Edu4rdSHL)

In beta releases from 5.29.0beta1 onwards I'm not able to launch the app, it doesn't crash as well, just hangs. I thought that it was something related to Nvidia and tried using the --disable-gpu flag but doesn't work as well. Here's the output log: https://paste.rs/sEw

Can someone confirm if it's working in your case? I'm still waiting for the -bin version to see if it works.

EDIT 12/01/2022 : -bin is working fine, so it's a problem here... I will continue investigating but I don't have much time, if someone can help me to find the root cause I would appreciate it.

EDIT 02/02/2022 (Nice date btw): The issue has been fixed, the problem was indeed on my side, it was the wrapper for /usr/bin/signal-desktop-beta created for 5.23 ¿? when the SQLite problem happened, it was causing the problem. Using a symlink directly fixed the problem:

Commit: https://aur.archlinux.org/cgit/aur.git/commit/?h=signal-desktop-beta&id=cabb29a6b8709d293e5844d145dc935c6d446043

reclusivesage commented on 2021-12-15 19:27 (UTC) (edited on 2021-12-15 19:38 (UTC) by reclusivesage)

Edit: Never mind, I was long overdue for updating Arch Linux because this error disappeared afterwards.

I received an error in prepare() involving a component called playwright when I follow either choice in its directions:

[4/5] Building fresh packages...
[15/33] ⠐ playwright
[9/33] ⠈ playwright
[-/33] ⠈ waiting...
[-/33] ⠈ waiting...
error /home/uSER/AUR/signal-desktop-beta/src/Signal-Desktop-5.27.0-beta.1/node_modules/playwright: Command failed.
Exit code: 1
Command: node install.js
Arguments: 
Directory: /home/uSER/AUR/signal-desktop-beta/src/Signal-Desktop-5.27.0-beta.1/node_modules/playwright
Output:
/home/uSER/AUR/signal-desktop-beta/src/Signal-Desktop-5.27.0-beta.1/node_modules/playwright-core/lib/utils/registry.js:558
        throw new Error('\n' + (0, _utils.wrapInASCIIBox)([`An active lockfile is found at:`, ``, `  ${lockfilePath}`, ``, `Either:`, `- wait a few minutes if other Playwright is installing browsers in parallel`, `- remove lock manually with:`, ``, `    ${rmCommand} ${lockfilePath}`, ``, `<3 Playwright Team`].join('\n'), 1));
              ^

Error: 
╔═════════════════════════════════════════════════════════════════════════════╗
║ An active lockfile is found at:                                             ║
║                                                                             ║
║   /home/uSER/.cache/ms-playwright/__dirlock                                 ║
║                                                                             ║
║ Either:                                                                     ║
║ - wait a few minutes if other Playwright is installing browsers in parallel ║
║ - remove lock manually with:                                                ║
║                                                                             ║
║     rm -rf /home/uSER/.cache/ms-playwright/__dirlock                        ║
║                                                                             ║
║ <3 Playwright Team                                                          ║
╚═════════════════════════════════════════════════════════════════════════════╝
    at Registry.install (/home/uSER/AUR/signal-desktop-beta/src/Signal-Desktop-5.27.0-beta.1/node_modules/playwright-core/lib/utils/registry.js:558



==> ERROR: A failure occurred in prepare().
    Aborting...

Edu4rdSHL commented on 2021-11-16 22:52 (UTC)

Hello, reclusivesage. Thanks for the heads-up, it has been fixed in -2, commit: https://aur.archlinux.org/cgit/aur.git/commit/?h=signal-desktop-beta&id=fc9645f2a0da03618788f00d03fda2cc00844643

reclusivesage commented on 2021-11-16 22:03 (UTC) (edited on 2021-11-18 17:18 (UTC) by reclusivesage)

Edit (Nov 18, 2021): This package now uses the LTS Gallium version of nodejs but uses current npm - thanks!

I received this error below. Did this happen because something in the build process expects newer and current Node.js version than the fermium LTS version?

[4/5] Building fresh packages...
[5/5] Cleaning modules...
success Saved lockfile.
$ yarn build:acknowledgments && yarn build:fuses && patch-package && electron-builder install-app-deps && rimraf node_modules/dtrace-provider
yarn run v1.22.17
error signal-desktop@5.25.0-beta.1: The engine "node" is incompatible with this module. Expected version ">=16.5.0". Got "14.17.3"
error Commands cannot run with an incompatible environment.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
==> ERROR: A failure occurred in prepare().
    Aborting...

Edu4rdSHL commented on 2021-10-15 18:35 (UTC)

Hello, arangelololo. Can you please confirm if you are using this package and not signal-desktop-beta-bin? Also, is the issue reproducible with signal-desktop from official repos or signal-desktop-beta-bin?

And please link the issue that you have opened in the upstream repo.

arangelololo commented on 2021-10-15 11:02 (UTC) (edited on 2021-10-15 21:55 (UTC) by arangelololo)

The mk (Macedonian) translation of Signal-Desktop does not load. My locale is changed to mk_MK.UTF8 and I can see the mk translations for GNOME for instance but not for Signal-Desktop.

The upstream project suggest to report a bug with the third party that created the package prior to reporting it there? Can you please check if this works for you or if there's something you can do about it?

Thanks!

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!

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