signalapp / Signal-Desktop

I used to use signal-desktop and it's disappeared from the binaries for quite some time now. so lost it.

There hasn't been a binary for FreeBSD 14 for a long now. But looking at "freshports" maybe one for v15 but no-one is going to be on that version now.

Have been trying to build it from the ports for quite a while (few months) but even that is STILL failing today (22nd June 2024). Doesn't anyone test that?


Don't get me wrong. I LOVE FreeBSD, have done since version 5. But the issue with maintainers - needs to be resolved for ALL PORTS.

As when there isn't a maintainer then it all goes to crap. For such a good OS, this needs to be worked out. Surely I'm not the only person on this planet that thinks that?
 
acheron said:
Yeah, I'm sorry for this situation. You can have more information on this problem here:
PR 270565
I provide prebuild package for 13.3 and 14.1 amd64 here: https://cocyte.westeurope.cloudapp.azure.com/signal-desktop/

What's the error when you compile signal-desktop yourself?
Click to expand...
Thanks for providing them, I upgraded mine to version 7.13. Here is the pkg repo configuration if you want to download it for 14.1 too.
Code: 
~> cat /usr/local/etc/pkg/repos/Local.conf
Local: {
        url: "file:///usr/ports/packages"
}

Signal: {
        url: "https://cocyte.westeurope.cloudapp.azure.com/signal-desktop/141amd64-signal-default/"
}
 
This has been happening for a little while now. At this time, according to freshports ONLY a binary is available on FreeBSD 15 for the latest version. Yet nothing for v14, which I'm currently on.

Have been trying to compile it myself every now and then but it still keeps failing.


Seems to fail here the most: -

Code: 
===>  Building for libsignal-node-0.50.0
echo 'yarn-offline-mirror "../yarn-offline-cache"' > /usr/ports/net-im/libsignal-node/work/libsignal-0.50.0/.yarnrc
echo 'nodedir "/usr/local"' >> /usr/ports/net-im/libsignal-node/work/libsignal-0.50.0/.yarnrc
cd /usr/ports/net-im/libsignal-node/work/libsignal-0.50.0/node &&  /usr/bin/env HOME=/usr/ports/net-im/libsignal-node/work  PYTHON=/usr/local/bin/python3.11  RUSTFLAGS=-Clink-dead-code  XDG_CACHE_HOME=/usr/ports/net-im/libsignal-node/work/.cache RUSTC_BOOTSTRAP=aes,polyval XDG_DATA_HOME=/usr/ports/net-im/libsignal-node/work  XDG_CONFIG_HOME=/usr/ports/net-im/libsignal-node/work  XDG_CACHE_HOME=/usr/ports/net-im/libsignal-node/work/.cache  HOME=/usr/ports/net-im/libsignal-node/work TMPDIR="/usr/ports/net-im/libsignal-node/work" PATH=/usr/ports/net-im/libsignal-node/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/root/bin PKG_CONFIG_LIBDIR=/usr/ports/net-im/libsignal-node/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local  LOCALBASE=/usr/local  CC="cc" CFLAGS="-O2 -pipe  -fstack-protector-strong -fno-strict-aliasing "  CPP="cpp" CPPFLAGS=""  LDFLAGS=" -fstack-protector-strong " LIBS=""  CXX="c++" CXXFLAGS="-O2 -pipe -fstack-protector-strong -fno-strict-aliasing  " BSD_INSTALL_PROGRAM="install  -s -m 555"  BSD_INSTALL_LIB="install  -s -m 0644"  BSD_INSTALL_SCRIPT="install  -m 555"  BSD_INSTALL_DATA="install  -m 0644"  BSD_INSTALL_MAN="install  -m 444" yarn install --frozen-lockfile --ignore-optional --offline
yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error Can't make a request in offline mode ("https://registry.yarnpkg.com/node-gyp-build/-/node-gyp-build-4.8.0.tgz")
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/net-im/libsignal-node
*** Error code 1


Can anyone tell me what's going on?
 
If you click on "Support" and select "Bug reports", then search for "signal--desktop" and sort the result on "changed date" so you get the latest changes on top, then second from the top you find bug_278049 that should contain what is going on.
 
Dunno what's going on. I have no problem on my builder and my desktop. I've also checked the FreeBSD build cluster and it builds fine there.
You can remove --offline in the do-build target in the Makefile (not sure if --frozen-lockfile needs to be removed)

Just in case, can you give me the output of
sha256 /usr/ports/distfiles/libsignal-node-0.50.0-yarn-cache.tar.gz
 
For giggles

After using signal-desktop-7.11.0_1 on FreeBSD 15.0-CURRENT, I deleted the package then added signal-desktop-6.48.1_6 from the FreeBSD Project repo for FreeBSD:13:amd64/quarterly.

A run of signal-desktop presented an error (no surprise) in its GUI:

Code: 
Unhandled Promise Rejection

Error: DBVersionFromFutureError: SQL: User version is 1050 but the expected maximum version is 980.
    at updateSchema ([REDACTED]/ts/sql/migrations/index.js:1785:11)
    at Object.initialize ([REDACTED]/ts/sql/Server.js:422:40)
    at MessagePort.<anonymous> ([REDACTED]/ts/sql/mainWorker.js:84:35)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:757:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
    at Worker.<anonymous> ([REDACTED]/ts/sql/main.js:58:26)
    at Worker.emit (node:events:517:28)
    at MessagePort.<anonymous> (node:internal/worker:242:53)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:757:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28)
 
Not for giggles

I added signal-desktop-7.13.0.pkg from the non-official repo for FreeBSD:14:amd64 – to 15.0-CURRENT.

Code: 
% su -
Password:
root@mowa219-gjp4-zbook-freebsd:~ # uname -aKU
FreeBSD mowa219-gjp4-zbook-freebsd 15.0-CURRENT FreeBSD 15.0-CURRENT main-n270938-617688369784 GENERIC-NODEBUG amd64 1500019 1500019
root@mowa219-gjp4-zbook-freebsd:~ # setenv ABI FreeBSD:14:amd64
root@mowa219-gjp4-zbook-freebsd:~ # setenv IGNORE_OSVERSION yes
root@mowa219-gjp4-zbook-freebsd:~ # pkg add https://cocyte.westeurope.cloudapp.azure.com/signal-desktop/141amd64-signal-default/All/signal-desktop-7.13.0.pkg
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Fetching signal-desktop-7.13.0.pkg: 100%  112 MiB   3.5MB/s    00:33   
Installing signal-desktop-7.13.0...
the most recent version of signal-desktop-6.48.1_6 is already installed
root@mowa219-gjp4-zbook-freebsd:~ # pkg delete --yes signal-desktop-6.48.1_6
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Updating database digests format: 100%
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
        signal-desktop: 6.48.1_6

Number of packages to be removed: 1

The operation will free 402 MiB.
[1/1] Deinstalling signal-desktop-6.48.1_6...
[1/1] Deleting files for signal-desktop-6.48.1_6: 100%
==> Running trigger: desktop-file-utils.ucl
Building cache database of MIME types
root@mowa219-gjp4-zbook-freebsd:~ # pkg add https://cocyte.westeurope.cloudapp.azure.com/signal-desktop/141amd64-signal-default/All/signal-desktop-7.13.0.pkg
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Fetching signal-desktop-7.13.0.pkg: 100%  112 MiB   4.0MB/s    00:29   
Installing signal-desktop-7.13.0...
Extracting signal-desktop-7.13.0: 100%
==> Running trigger: desktop-file-utils.ucl
Building cache database of MIME types
root@mowa219-gjp4-zbook-freebsd:~ # exit
logout
% signal-desktop
[24163:0625/164441.526217:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018
Set Windows Application User Model ID (AUMID) { AUMID: 'org.whispersystems.signal-desktop' }
NODE_ENV production
…

Success, the application runs, I used my Android handset to link it.

The warning, and bootstrap recommendation, are necessarily ignored in the 15.0-CURRENT context.
 
knaggsy2000 said:
… nothing for v14, …
Click to expand...

The Electron version requirement of net-im/signal-desktop changed a few days ago, it no longer matches the requirement of editors/vscode.

With the current infrastructure, the FreeBSD Project builds (and provides packages for) no more than one version of Electron.
 

Attachments

  • 1719331206858.png
    1719331206858.png
    74.7 KB · Views: 65
  • 1719331266840.png
    1719331266840.png
    29.3 KB · Views: 69
Tried to compile it again from ports and STILL failing.

Code: 
error /usr/ports/net-im/signal-desktop/work/Signal-Desktop-7.13.0/node_modules/@signalapp/better-sqlite3: Command failed.
Exit code: 127
Command: npm run download && npm run build-release


yarn install v1.22.19
[1/4] Resolving packages...
[2/4] Fetching packages...
error Can't make a request in offline mode ("https://registry.yarnpkg.com/node-gyp-build/-/node-gyp-build-4.8.0.tgz")
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
*** Error code 1

Why doesn't it even compile on v14.1 but yet does on v15 (according "freshports")?
 
Cath O'Deray said:
The Electron version requirement of net-im/signal-desktop changed a few days ago, it no longer matches the requirement of editors/vscode.

With the current infrastructure, the FreeBSD Project builds (and provides packages for) no more than one version of Electron.
Click to expand...

VSCode has updated via "pkg" and is still working.
 
Forgive my naivety, but I didn't realise (or didn't notice) that signal-desktop was going to be missing from the upgrade to 14.1 - but I was encouraged to upgrade from 13.2
When is signal-desktop going to make it to the official repositories, and what is the hold up?
I rely on it quite a lot. Thanks,
 
Zagzigger said:
When is signal-desktop going to make it to the official repositories
Click to expand...
It is back there today.

Zagzigger said:
I didn't realise (or didn't notice) that signal-desktop was going to be missing from the upgrade to 14.1
Click to expand...
This issue has nothing to do with the FreeBSD release you're running. Had you stayed on 13.x, the package would have gone missing too after a quarterly package upgrade. With a few exceptions (when something works on a specific release but doesn't on another), all supported releases have the same packages available.
 
While we are talking about this, the current signal-desktop appears to be an older version? Doesn't let you "link" to your account in your phone and fails with the following:

1723586048935.png


Any advice?
Thanks!

Version 7.13.0 installed from the the official pkg repo.
 
Are you using version 7.13.0 from quarterly or 7.16.0 from latest? If you're tracking quarterly, a package for 7.16.0 is available from the maintainer, or you can build it yourself.

However, I'm surprised that you get such an issue already. Version 7.13.0 is not old, the current official release for Android is 7.13.3. Funnily, I currently have a newer Signal version on my FreeBSD desktop than on my phone...
 
  • Thanks
Reactions: mro
bsduck said:
Are you using version 7.13.0 from quarterly or 7.16.0 from latest? If you're tracking quarterly, a package for 7.16.0 is available from the maintainer, or you can build it yourself.

However, I'm surprised that you get such an issue already. Version 7.13.0 is not old, the current official release for Android is 7.13.3. Funnily, I currently have a newer Signal version on my FreeBSD desktop than on my phone...
Click to expand...

Yeap, 7.13.0.
 
bsduck said:
It is back there today.


This issue has nothing to do with the FreeBSD release you're running. Had you stayed on 13.x, the package would have gone missing too after a quarterly package upgrade. With a few exceptions (when something works on a specific release but doesn't on another), all supported releases have the same packages available.
Click to expand...
Thanks for the explanation - that question did not even occur to me.
 
Cath O'Deray said:
Please, don't add unnecessary noise to bug reports.
Click to expand...
Fair enough, but I think the problem regarding the build is quite relevant and e.g. the suggestion by somebody for a Foundation donation drive for port builder resources is a good idea that might help solve exactly that problem, i.e. fix this "bug". :)
 
pebkac said:
… signal-desktop …
Click to expand...

On 14th August, Mikael Urankar, mikael@ (acheron) wrote:

"I'll update signal-desktop to the latest version "soon", it'll use electron31"

forums.freebsd.org

Electron – devel/electron29 and greater

For reference https://forums.freebsd.org/threads/electron-for-freebsd.64103/ devel/electron28 is deprecated, will expire at the end of this month. devel/electron29 alone is packaged by the FreeBSD Project. Ports that require devel/electron30 include: editors/vscode – Code - OSS...
forums.freebsd.org forums.freebsd.org
 
Cath O'Deray said:
On 14th August, Mikael Urankar, mikael@ (acheron) wrote:

"I'll update signal-desktop to the latest version "soon", it'll use electron31"

forums.freebsd.org

Electron – devel/electron29 and greater

For reference https://forums.freebsd.org/threads/electron-for-freebsd.64103/ devel/electron28 is deprecated, will expire at the end of this month. devel/electron29 alone is packaged by the FreeBSD Project. Ports that require devel/electron30 include: editors/vscode – Code - OSS...
forums.freebsd.org forums.freebsd.org
Click to expand...
I am not sure what you want to say with this reply?

The different Electron-based tools like VScode, Signal etc will for sure also in the future from time to time depend on different Electron versions.

So actually providing enough package builder resources to have several Electron version packages available in parallel will be the only solution to ensure that we always have up to date packages.
 
You must log in or register to reply here.
Back
Top