Fast, simple and secure messaging app from your desktop

Edit Package signal-desktop
https://github.com/signalapp/Signal-Desktop/

Signal Desktop is an Electron application that links with your Signal Android
or Signal iOS app.

Refresh
Refresh
Source Files
Filename Size Changed
Signal-Desktop-1.14.4.tar.gz 0020024905 19.1 MB
prepare.sh 0000000837 837 Bytes
signal-desktop 0000000061 61 Bytes
signal-desktop-1.14.4.tar.xz 0067203772 64.1 MB
signal-desktop.changes 0000006916 6.75 KB
signal-desktop.desktop 0000000276 276 Bytes
signal-desktop.spec 0000002551 2.49 KB
Revision 7 (latest revision is 298)
i thod's avatar i thod (ithod) accepted request 624400 from i thod's avatar i thod (ithod) (revision 7)
- update to 1.14.4
  * Added a new option to disable spell checking for users who write
    in multiple languages that differ from their system locale.
  * Automatically clean up old debug information, remove logging
    unnecessary for troubleshooting purposes, and improve debug
    log submission.
  * Fixed: After upload, debug logs were not accessible
  * Show error if debug log fails to upload.
  * Fixed: Application does not start up on Linux w/tmp mounted as
    noexec
  * Fixed: When attempting to record voice note with media permission
    disabled, popup would be blank
Comments 12

Bruno Pitrus's avatar

Do you know how often electron makes ABI-breaking changes? If minor updates are OK, it might be worth doing something like this:

Requires: nodejs-electron%{?_isa} >= %{electron_req_version}

Requires: nodejs-electron%{?_isa} < 17 (or whatever is current version + 1)

My Bitwarden binaries built with Electron 13 ( https://build.opensuse.org/package/show/home:dziobian:gulgul-ultron/bitwarden ) work fine on 16, but Signal does not, so there seem to be at least two types of binary Node modules.


Andreas Schneider's avatar

Signal requires header files for electron which are being downloaded. Same for nodejs, so the header files in the vendor tarball need to match exactly the nodejs and electron version to be able to build it.

Yes, it is quite a mess.


Bruno Pitrus's avatar

The nodejs headers are provided in nodejs16-devel and can be used adding --nodedir=/usr/include/node16 to npm command line. Unfortunately the SuSE distribution of electron does not include devel headers. Ouch.

My question was different tho. I was asking whether binaries built against electron 16.0.1 can run with electron 16.0.2.


Andreas Schneider's avatar

Yes, that should work. I was even able to run signal-desktop built against electron 13 with electron 15. However signal-desktop build with 15 and running with 16 doesn't work. Minor version updates should work.

I will look into node includes soon. However it still downloads electron headers from the web. Maybe we can package them too.


Andreas Schneider's avatar

If I do export npm_config_nodedir=/usr/include/node16

node-gyp doesn't find the header:

make: Entering directory '/tmp/signal-desktop-1Tah1oUK/Signal-Desktop-5.29.0/node_modules/fs-xattr/build'
  CC(target) Release/obj.target/xattr/src/async.o
In file included from ../src/async.c:6:
../src/error.h:5:10: fatal error: node_api.h: No such file or directory
    5 | #include <node_api.h>
      |  


Bruno Pitrus's avatar

The environment variable seems to not work, you need to use --prefix=…. See how i did it in my spec for bitwarden


Andreas Schneider's avatar

That's just a workaround. I think right fix is that the common.gypi sets the include path correctly.


Jos Poortvliet's avatar

I also see the remove-heif support patch, that's uncool, I'll miss out on lots of dog and food pictures!

Seriously, anything that can be done to have working heif support? As disabling that means 99% of the pics I get don't show :D Or does it work and does this patch do something else... Sorry, just curious I guess.


Andreas Schneider's avatar

Tell your friends to use royalty free image formats.


P's avatar

Thank you for your dedication and hard work! This is so much appreciated!!!


Will McCullen's avatar

I agree. Thank you for all you do. Just out of curiosity, is anyone else having issues with spellcheck working?

openSUSE Build Service is sponsored by