-
-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing native libsignal-client in v0.8.4 #643
Comments
That's strange, which distribution and cpu architecture do you have? |
I get the same error on Debian 10 (x86_64). |
ditto :) I've tried to compile libsignal-client on my system. I've got an older version of rust, so I've encountered some errors. Will try again once I have a bit more time. |
I have compiled the libsignal-client java library (turned out it requires the latest nightly release of the rust compiler), and replaced the original with it:
Now it works fine with signal-cli v0.8.4. For the reference, here's the compiled binary file. Let me know if I can do anything else to troubleshoot this on my system. |
Maybe upstream now compiles on a newer distribution, with a more recent libc version than debian 10 has ... |
Same here. |
yep, upstream libsignal-client builds the library with ubuntu latest, which has a newer glibc version.
|
Another case of this (CentOS 7): #606 (comment), #413 (comment) |
I've got a similar error when sending a message using signal-cli v0.8.4.1: This is on a Raspberry Pi (Debian 10 -buster based), with libsignal-client and libzkgroup updated with local builds. |
This is probably a different issue (i.e. not caused by an older version of Are you using the newer versions of the native libraries? (Updated since signal-cli 0.8.3). The current |
Make sure to remove the libraries and add the new ones without path. |
@exquo Hi, Thank you for that answer. That makes now sense to me. Now I think about it, and reading the 'remove' bit., it might be that I did not remove the previous version correctly I'll try the ones posted by @bublath and post an update when I got that tested on my side. |
FYI: I've started a GitHub CI/CD that compiles the native libraries automatically when new signal-cli versions are released. The linux version is compiled on Ubuntu 18, so should work on "older" |
debian 10
What's the suggested solution for it? |
I have a precompiled library that should work with debian 10 here: |
In the meantime I decided to upgrade my server from debian10 to 11 (bullseye), which solved that "problem". |
Hello guys, I have the same problem on windows 10 x64 here : WARN ServiceConfig - Failed to call libsignal-client: D:\Users\arthu\AppData\Local\resource14946054837028231560.so: Can't load this .dll (machine code=0x0) on a AMD 64-bit platform To be clear I am a absolute rookie on those stuff, and I'm already very surprised I got that far, if someone has an idea, it would be awesome. thanks a lot |
Looks like starting from signal-cli 0.12.0 and libsignal-client 0.30.0 Ubuntu 20.04 is now too old also:
|
You can replace the library with the automated builds that are available here: https://github.com/exquo/signal-libs-build |
I approached this differently. I used Docker to run local Ubuntu container with the latest glibc and mount my home directory into the container. Then I installed
|
Just installed the latest signal-cli release v0.8.4 and got
This is on linux, and the previous signal-cli versions have worked fine without needing any manual steps from https://github.com/AsamK/signal-cli/wiki/Provide-native-lib-for-libsignal.
I've checked, and the
libsignal_jni.so
is bundled in the jar file:So, not sure what's missing.
The text was updated successfully, but these errors were encountered: