Bisq 0.5.1 Debian 32bit Packaging problem? #849

ElLamparto · 2017-07-02T17:13:37Z

After successful install, Bisq does not start: /opt/Bisq/Bisqe/en/libpackager.so not found.

Indeed there is no /opt/Bisq/Bisqe directory. libpackager.so is located in /opt/Bisq.

ManfredKarrer · 2017-07-02T20:25:37Z

That is strange. Bisqe is nowhere used. I assuem u have downlaoded form github and checked the sig.
maybe just delete /opt/Bisq/ and install new.

ElLamparto · 2017-07-03T18:17:43Z

Yes, I checked your signature.

gpg --verify Bisq-32bit-0.5.1.deb.asc Bisq-32bit-0.5.1.deb
gpg: Signature made Sat 01 Jul 2017 03:32:59 CEST using RSA key ID F379A1C6
gpg: Good signature from "Manfred Karrer manfred@bitsquare.io"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1DC3 C8C4 316A 698A C494 039C F5B8 4436 F379 A1C6

ManfredKarrer · 2017-07-03T22:29:21Z

Try to remove /opt/Bisq/ and install new...

ElLamparto · 2017-07-04T19:18:21Z

I did. The same result.
Then I created /opt/Bisq/Bisqe/en/ and copied libpackager.so there. --> Bisq segfaulted at startup.

ManfredKarrer · 2017-07-04T22:13:09Z

Can u try to run from source?
https://github.com/bitsquare/bitsquare/blob/master/doc/build.md

the segfault is prob. bc of the new linux kernel issue.
adding that jre option (-BjvmOptions=-Xss1280k) should avoid it.

ghost · 2017-07-05T19:35:42Z

FYI. I can confirm new Kernel 4.4.0.83 released for Ubuntu 16.04. Works with latest 0.5.1 Bisq.

ElLamparto · 2017-07-06T18:24:39Z

I am still on Debian 8 (Jessie).

java -version
java version "1.7.0_131"
OpenJDK Runtime Environment (IcedTea 2.6.9) (7u131-2.6.9-2~deb8u1)
OpenJDK Server VM (build 24.131-b00, mixed mode)

uname -a
Linux [...] 3.16.0-4-686-pae #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) i686 GNU/Linux

ElLamparto · 2017-07-19T07:55:10Z

I suspected java version to be the cause. IMHO changing java version should be mentioned in the release note.
Next week I will upgrade Jessie to Stretch which probably has java 8 on board. That should fix the problem.
I'll keep you informed via this ticket.

ManfredKarrer · 2017-07-19T09:31:44Z

The java version was always Java 8. Java 7 does not work with Bisq. If you run the installer you don't need to care as the jre is packed in the app. Only if you run from source you need to follow exactly the build.md instructions.

ElLamparto · 2017-07-22T10:56:44Z

I tried 0.5.3, the same result.
[...]:/opt/Bisq$ ./Bisq 
/opt/Bisq/Bisqe/en/libpackager.so not found.

I checked env vars, I found:
PWD=/opt/Bisq

Soon I'll upgrade to Stretch which should be comparable to the current Ubuntu version.... I'll let you know.

ElLamparto · 2017-07-23T11:17:25Z

Ps. I just installed 0.5.3 on another Debian 8 machine --> the same result :(

ManfredKarrer · 2017-07-23T11:22:16Z

So its again that "/opt/Bisq/Bisqe/en/libpackager.so not found."?

ManfredKarrer · 2017-07-23T11:26:42Z

I just checked my ubuntu VM and libpackager is at: /opt/Bisq/libpackager.so
So for some strange reason your OS is installing it to that Bisqe/en/ package. No idea, maybe some OS language issue, which language do u use? I suspect the the e at the end of Bisqe is added for english or espanol? Wehn u move manually the stuff from /opt/Bisq/Bisqe/en/ to /opt/Bisq/ does that help?

ElLamparto · 2017-07-23T17:43:38Z

No, I have /opt/Bisq/libpackager.so (what is correct).
Directory /opt/Bisq/Bisqe/en/ does not exist.
The OS language is English.

Once I created /opt/Bisq/Bisqe/en/ and copied libpackager.so there. --> Bisq segfaulted at startup.

So libpackager.so is in the correct place. For some reason, Bisq searches for it in the non-existing folder /opt/Bisq/Bisqe/en/.

The problem appeared with 0.5.1 (or maybe 0.5.0 which I skipped).

ManfredKarrer · 2017-07-23T20:38:33Z

Very strange. Can u try latest installer 0.5.3. but dont assume its the installer.

ElLamparto · 2017-07-26T09:27:06Z

I upgraded my OS to Debian 9.1 (Stretch).
The problem still exists. However I noticed the following:

If I start Bisq from my home dir, I get:

If I start Bisq from /opt/Bisq, I get:

You see the not printable character after Bisq?

I have an impression, that a variable holding the library path is not initialized or is missing the zero termination... I do not know Java at all, but in those two examples the library path is different and obviously contains some rubbish..

ManfredKarrer · 2017-07-26T09:36:46Z

@cedricwalter Do you have any idea? Never saw that issue before and never got it on my Ubuntus MV...

cedricwalter · 2017-07-26T20:24:15Z

Bug in JDK 8, in the javafx launcher, solved in openjdk 9
https://bugs.openjdk.java.net/browse/JDK-8157913
http://bugs.java.com/view_bug.do?bug_id=8157913

There is a workaround we can implement
Unpack packager-created packages, replace launcher by custom implementation, repackage manually.

Here is a changeset from another project that did the workaround:
cryptomator/cryptomator@6006d65

Another workaround is what you did: create /opt/Bisq/Bisqe/en/ and copy libpackager.so there. Cannot understand why you get a segfault as a reward through....

ManfredKarrer · 2017-07-26T21:05:43Z

The segfault might be because of missing -BjvmOptions=-Xss1280k which fixed the issue with recent linux kernel issues. See: https://forum.bisq.io/t/bitsquare-dont-opens-ubuntu-16-04/2312/33

ManfredKarrer · 2017-07-26T21:10:44Z

@cedricwalter Thanks for researching and finding! Any idea why that only seems to be a problem in one case so far? Never got reported it earlier. Should affect all linux users, no?

ElLamparto · 2017-08-10T08:25:25Z

The strange thing is that with previous versions I've done quite a few upgrades without problems.

Manfred, @cedricwalter, could any of you create for me an executable that works? I need Bitsquare and I know next to nothing about Java.

Thank you...

ManfredKarrer · 2017-08-10T11:14:37Z

@ElLamparto As I don't know how to solve that issue I cannot do anything here. But you can run form source code. See https://github.com/bitsquare/bitsquare/blob/master/doc/build.md

ElLamparto · 2017-08-10T18:33:34Z

If you gave me Bisq from your Ubuntu VM, wouldn't it work on my Debian?

ManfredKarrer · 2017-08-10T18:46:41Z

You mean that I give you the extracted app directory. Send me an email if you like I can send you.

ElLamparto · 2017-08-12T19:19:26Z

I installed xubuntu 16.04 (LTS) on a VM and then Bisq.
Bisq segfaulted immediately after start.

Which version of Ubuntu do you use?

ManfredKarrer · 2017-08-12T19:41:29Z

Ubuntu 14.04. Can u try to start with vm arg: -Xss1280k

ElLamparto · 2017-08-12T19:54:00Z

I know nothing about Java.
How to start Bisq with that vm arg? Please give me the syntax.
Thanks.

ElLamparto · 2017-08-26T13:28:45Z

CAN ANYONE HELP??

I tried:
java -Xss1280k -jar /opt/Bisq/app/Bisq-0.5.3.jar

I got:
Cryptography restrictions removal not needed
Exception in thread "main" java.lang.NoClassDefFoundError: javafx/application/Application
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)
at java.net.URLClassLoader.access$100(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:368)
at java.net.URLClassLoader$1.run(URLClassLoader.java:362)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:361)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at io.bisq.gui.app.BisqAppMain.doExecute(BisqAppMain.java:80)
at io.bisq.core.app.BisqExecutable.execute(BisqExecutable.java:70)
at io.bisq.gui.app.BisqAppMain.main(BisqAppMain.java:75)
Caused by: java.lang.ClassNotFoundException: javafx.application.Application
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 15 more

I also tried export _JAVA_OPTIONS='-Xss1280k' and then run Bisq, but it segfaulted. As far as I remember, it had something to do with extending heap size.

ManfredKarrer · 2017-08-27T10:25:23Z

If you run from source code you need to follow exactly the instructions in /doc/build.md.

ElLamparto · 2017-08-27T17:11:07Z

Ok. I just try to have Bisq operational without compiling...

ElLamparto · 2017-09-03T07:27:38Z

I tried compiling bisq according to install_on_unix.sh. The process seemed to work correctly (incl. protobuf) until:

mvn clean package verify -DskipTests -Dmaven.javadoc.skip=true

which failed with:
[WARNING] The POM for org.libdohj:libdohj-core:jar:0.14.1 is missing, no dependency information available

Attached is the log.
FailedBuild.zip

mrosseel · 2017-09-03T11:31:32Z

https://github.com/bisq-network/libdohj
also needs to be checked out and installed in your local maven repository (mvn clean install)

ElLamparto · 2017-09-03T12:46:35Z

Thank you. Sorry, I do not know maven.

To what place check it out precisely?
And then what is the exact syntax ("mvn clean install")?
Finally, should I execute again "mvn clean package verify -DskipTests -Dmaven.javadoc.skip=true"?

mrosseel · 2017-09-03T15:32:53Z

Doesn't matter, not inside the bisq directory, somewhere else
that should do it, you can add -DskipTests to speed it up
Yes, libdohj is just a dependency needed to build bisq

ElLamparto · 2017-09-04T08:07:07Z

@mrosseel, thank you very much. I'll try it in the next weekend.
I hope that in the next version, the workaround described by @cedricwalter will be deployed and the install/upgrade will be flawless like always before v0.5.0.

ElLamparto · 2017-09-10T08:10:10Z

Yesterday I compiled libdohj and cloned bisq master.
I got:
[INFO] --- protobuf-maven-plugin:0.5.0:compile (default) @ common ---
[INFO] Compiling 1 proto file(s) to /root/bisq-exchange/common/target/generated-sources/protobuf/java
[ERROR] PROTOC FAILED: /root/bisq-exchange/common/target/dependency/protoc: 1: /root/bisq-exchange/common/target/dependency/protoc: Syntax error: ")" unexpected

[ERROR] /root/bisq-exchange/common/src/main/proto/pb.proto [0:0]: /root/bisq-exchange/common/target/dependency/protoc: 1: /root/bisq-exchange/common/target/dependency/protoc: Syntax error: ")" unexpected

rtentser · 2018-03-26T14:49:39Z

I have the same problem with 0.6.7 on Debian Stretch.

/opt/Bisq/Bisqen/libpackager.so not found.

But copying libpackager.so to Bisqen don't make any difference. I don't have a segmentation fault, the program just fails to work with the same message.

UPD: Upgrade to openjdk-9-jre didn't help.

ElLamparto · 2018-05-30T14:53:40Z

I am a bit dissapointed, since this problem is not even in the roadmap.
Has anybody an experience in running bisq under wine/playonlinux? Is it possible at all?

ManfredKarrer · 2018-05-30T15:34:08Z

@ElLamparto Can you try to run it from source code?

ManfredKarrer · 2018-05-30T15:35:14Z

The roadmap on the webpage is not much maintained. We are short on dev resources and depend on other people to help out with stuff like that. Seems to be some specific OS issue as there for most people it works.

stale · 2019-01-17T22:16:11Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale · 2019-01-25T00:13:52Z

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

stale bot added the was:dropped label Jan 17, 2019

stale bot closed this as completed Jan 25, 2019

Bisq 0.5.1 Debian 32bit Packaging problem? #849

Bisq 0.5.1 Debian 32bit Packaging problem? #849

Comments

ElLamparto commented Jul 2, 2017

ManfredKarrer commented Jul 2, 2017

ElLamparto commented Jul 3, 2017

ManfredKarrer commented Jul 3, 2017

ElLamparto commented Jul 4, 2017

ManfredKarrer commented Jul 4, 2017

ghost commented Jul 5, 2017

ElLamparto commented Jul 6, 2017

ElLamparto commented Jul 19, 2017

ManfredKarrer commented Jul 19, 2017

ElLamparto commented Jul 22, 2017

ElLamparto commented Jul 23, 2017

ManfredKarrer commented Jul 23, 2017

ManfredKarrer commented Jul 23, 2017

ElLamparto commented Jul 23, 2017

ManfredKarrer commented Jul 23, 2017

ElLamparto commented Jul 26, 2017

ManfredKarrer commented Jul 26, 2017

cedricwalter commented Jul 26, 2017 • edited Loading

ManfredKarrer commented Jul 26, 2017

ManfredKarrer commented Jul 26, 2017

ElLamparto commented Aug 10, 2017

ManfredKarrer commented Aug 10, 2017

ElLamparto commented Aug 10, 2017

ManfredKarrer commented Aug 10, 2017 • edited Loading

ElLamparto commented Aug 12, 2017

ManfredKarrer commented Aug 12, 2017

ElLamparto commented Aug 12, 2017 • edited Loading

ElLamparto commented Aug 26, 2017 • edited Loading

ManfredKarrer commented Aug 27, 2017

ElLamparto commented Aug 27, 2017

ElLamparto commented Sep 3, 2017

mrosseel commented Sep 3, 2017

ElLamparto commented Sep 3, 2017

mrosseel commented Sep 3, 2017

ElLamparto commented Sep 4, 2017

ElLamparto commented Sep 10, 2017

rtentser commented Mar 26, 2018 • edited Loading

ElLamparto commented May 30, 2018

ManfredKarrer commented May 30, 2018

ManfredKarrer commented May 30, 2018

stale bot commented Jan 17, 2019

stale bot commented Jan 25, 2019

cedricwalter commented Jul 26, 2017 •

edited

Loading

ManfredKarrer commented Aug 10, 2017 •

edited

Loading

ElLamparto commented Aug 12, 2017 •

edited

Loading

ElLamparto commented Aug 26, 2017 •

edited

Loading

rtentser commented Mar 26, 2018 •

edited

Loading