Skip to content
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

Does not start in VirtualBox Debian (latest) guest #3686

Closed
dimaatmelodromru opened this issue Nov 25, 2019 · 7 comments
Closed

Does not start in VirtualBox Debian (latest) guest #3686

dimaatmelodromru opened this issue Nov 25, 2019 · 7 comments
Labels
a:bug is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation on:Linux waiting for author

Comments

@dimaatmelodromru
Copy link

Description

Does not start in VirtualBox Debian (latest) guest

Since Bisq freezes my OS Ubuntu 19.10 I was trying to start it in VirtualBox Debian (latest) guest, 4GB RAM.
Nope. No messages. Nothing.

Version

1.2.3

Steps to reproduce

Expected behaviour

Actual behaviour

Screenshots

Device or machine

Additional info

@dimaatmelodromru
Copy link
Author

logs:

cl1p.net - The internet clipboard cl1p.net/rbtdn
Here is your stuff. Thanks for using cl1p. Tell your friends!

Nov-25 18:36:03.562 [main] INFO b.c.s.CoreSetup:

Log files under: /home/user/.local/share/Bisq/bisq
Nov-25 18:36:03.620 [main] INFO b.c.u.Utilities: System info: os.name=Linux; os.version=4.19.0-6-amd64; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot(TM) 64-Bit Server VM)
Nov-25 18:36:03.788 [main] INFO b.c.s.CoreNetworkCapabilities: Set Capability.RECEIVE_BSQ_BLOCK
Nov-25 18:36:04.138 [main] INFO b.c.app.Version: Version{VERSION=1.2.3, P2P_NETWORK_VERSION=1, LOCAL_DB_VERSION=1, TRADE_PROTOCOL_VERSION=2, BASE_CURRENCY_NETWORK=0, getP2PNetworkId()=10}
Nov-25 18:36:04.143 [main] INFO b.c.s.CoreSetup: Path to Bisq jar file: /opt/Bisq/app/desktop-1.2.3-all.jar
Nov-25 18:37:09.944 [main] INFO b.c.s.CoreSetup:

Log files under: /home/user/.local/share/Bisq/bisq
Nov-25 18:37:10.017 [main] INFO b.c.u.Utilities: System info: os.name=Linux; os.version=4.19.0-6-amd64; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot(TM) 64-Bit Server VM)
Nov-25 18:37:10.209 [main] INFO b.c.s.CoreNetworkCapabilities: Set Capability.RECEIVE_BSQ_BLOCK
Nov-25 18:37:10.611 [main] INFO b.c.app.Version: Version{VERSION=1.2.3, P2P_NETWORK_VERSION=1, LOCAL_DB_VERSION=1, TRADE_PROTOCOL_VERSION=2, BASE_CURRENCY_NETWORK=0, getP2PNetworkId()=10}
Nov-25 18:37:10.621 [main] INFO b.c.s.CoreSetup: Path to Bisq jar file: /opt/Bisq/app/desktop-1.2.3-all.jar
Nov-25 18:38:03.542 [main] INFO b.c.s.CoreSetup:

Log files under: /home/user/.local/share/Bisq/bisq
Nov-25 18:38:03.619 [main] INFO b.c.u.Utilities: System info: os.name=Linux; os.version=4.19.0-6-amd64; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot(TM) 64-Bit Server VM)
Nov-25 18:38:03.841 [main] INFO b.c.s.CoreNetworkCapabilities: Set Capability.RECEIVE_BSQ_BLOCK
Nov-25 18:38:04.346 [main] INFO b.c.app.Version: Version{VERSION=1.2.3, P2P_NETWORK_VERSION=1, LOCAL_DB_VERSION=1, TRADE_PROTOCOL_VERSION=2, BASE_CURRENCY_NETWORK=0, getP2PNetworkId()=10}
Nov-25 18:38:04.356 [main] INFO b.c.s.CoreSetup: Path to Bisq jar file: /opt/Bisq/app/desktop-1.2.3-all.jar
Nov-25 18:49:29.380 [main] INFO b.c.s.CoreSetup:

Log files under: /home/user/.local/share/Bisq/bisq
Nov-25 18:49:29.466 [main] INFO b.c.u.Utilities: System info: os.name=Linux; os.version=4.19.0-6-amd64; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot(TM) 64-Bit Server VM)
Nov-25 18:49:29.840 [main] INFO b.c.s.CoreNetworkCapabilities: Set Capability.RECEIVE_BSQ_BLOCK
Nov-25 18:49:30.423 [main] INFO b.c.app.Version: Version{VERSION=1.2.3, P2P_NETWORK_VERSION=1, LOCAL_DB_VERSION=1, TRADE_PROTOCOL_VERSION=2, BASE_CURRENCY_NETWORK=0, getP2PNetworkId()=10}
Nov-25 18:49:30.432 [main] INFO b.c.s.CoreSetup: Path to Bisq jar file: /opt/Bisq/app/desktop-1.2.3-all.jar
Nov-25 18:49:45.500 [main] INFO b.c.s.CoreSetup:

Log files under: /home/user/.local/share/Bisq/bisq
Nov-25 18:49:45.569 [main] INFO b.c.u.Utilities: System info: os.name=Linux; os.version=4.19.0-6-amd64; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot(TM) 64-Bit Server VM)
Nov-25 18:49:45.729 [main] INFO b.c.s.CoreNetworkCapabilities: Set Capability.RECEIVE_BSQ_BLOCK
Nov-25 18:49:46.074 [main] INFO b.c.app.Version: Version{VERSION=1.2.3, P2P_NETWORK_VERSION=1, LOCAL_DB_VERSION=1, TRADE_PROTOCOL_VERSION=2, BASE_CURRENCY_NETWORK=0, getP2PNetworkId()=10}
Nov-25 18:49:46.078 [main] INFO b.c.s.CoreSetup: Path to Bisq jar file: /opt/Bisq/app/desktop-1.2.3-all.jar
Nov-25 19:12:22.900 [main] INFO b.c.s.CoreSetup:

Log files under: /home/user/.local/share/Bisq/bisq
Nov-25 19:12:22.965 [main] INFO b.c.u.Utilities: System info: os.name=Linux; os.version=4.19.0-6-amd64; os.arch=amd64; sun.arch.data.model=64; JRE=10.0.2+13 (Oracle Corporation); JVM=10.0.2+13 (Java HotSpot(TM) 64-Bit Server VM)
Nov-25 19:12:23.125 [main] INFO b.c.s.CoreNetworkCapabilities: Set Capability.RECEIVE_BSQ_BLOCK
Nov-25 19:12:23.486 [main] INFO b.c.app.Version: Version{VERSION=1.2.3, P2P_NETWORK_VERSION=1, LOCAL_DB_VERSION=1, TRADE_PROTOCOL_VERSION=2, BASE_CURRENCY_NETWORK=0, getP2PNetworkId()=10}
Nov-25 19:12:23.495 [main] INFO b.c.s.CoreSetup: Path to Bisq jar file: /opt/Bisq/app/desktop-1.2.3-all.jar

@ripcurlx
Copy link
Contributor

Related to: #3128, #3657, #3918, #3917, #3787, #3786, #3686, #3677, #3343

@ripcurlx ripcurlx added the is:critical https://bisq.wiki/Critical_bug label Feb 18, 2020
@ghubstan
Copy link
Member

ghubstan commented Feb 24, 2020

I could not reproduce this problem by installing the 1.2.7 .deb release on the latest Debian 10.3 guest vm running with 8 GiB, and with 4 GiB (hosted on an Ubuntu 18.04).

I could also run it on an Ubuntu 19 VM, but with the reported memory leak problem.

I could build & run 1.2.7-SNAPSHOT src, and create a .deb installer pkg, install it to /opt, and run that too.

But I could not run the linux javapackager on debian because it crashed while trying to create an "rpm" using version=1.2.7-SNAPSHOT:

error: line 3: Illegal char '-' (0x2d) in: Version: 1.2.7-SNAPSHOT	

Related to #4006 , #2200

@ripcurlx
Copy link
Contributor

@dimaatmelodromru Could you please try to run v1.2.7 on your system as well, just to know if your bug is already fixed?

@cbeams cbeams added the a:bug label Feb 27, 2020
cd2357 added a commit to cd2357/bisq that referenced this issue May 7, 2020
Update the gradle dependency to JavaFX 14.

This brings to Bisq the latest JavaFX fixes and improvements, especially
 in the areas of UI performance, memory management and security.

JavaFX can be upgraded independently of the JDK used to build the
application, so this change is modular and does not affect other parts
of the build process.

Related / likely related to: bisq-network#350 bisq-network#2135 bisq-network#2509 bisq-network#3128 bisq-network#3307 bisq-network#3308 bisq-network#3343
bisq-network#3430 bisq-network#3657 bisq-network#3677 bisq-network#3683 bisq-network#3686 bisq-network#3786 bisq-network#3787 bisq-network#3892 bisq-network#3917 bisq-network#3918 bisq-network#3936
@chimp1984
Copy link
Contributor

-SNAPSHOT

You have to remove the "-SNAPSHOT" string from any version fields.

@chimp1984
Copy link
Contributor

Can you try out the recommendations at #3918 (comment) ?

cd2357 added a commit to cd2357/bisq that referenced this issue Sep 16, 2020
Update the gradle dependency to JavaFX 14.

This brings to Bisq the latest JavaFX fixes and improvements, especially
 in the areas of UI performance, memory management and security.

JavaFX can be upgraded independently of the JDK used to build the
application, so this change is modular and does not affect other parts
of the build process.

Related / likely related to: bisq-network#350 bisq-network#2135 bisq-network#2509 bisq-network#3128 bisq-network#3307 bisq-network#3308 bisq-network#3343
bisq-network#3430 bisq-network#3657 bisq-network#3677 bisq-network#3683 bisq-network#3686 bisq-network#3786 bisq-network#3787 bisq-network#3892 bisq-network#3917 bisq-network#3918 bisq-network#3936
@cd2357
Copy link
Contributor

cd2357 commented Mar 29, 2021

As per #3686 (comment) above, not reproducible.

I've also been testing most versions since v1.5.0 on the same setup (latest Debian as guest in VirtualBox) with no issues.

@cd2357 cd2357 closed this as completed Mar 29, 2021
Critical Bugs Board automation moved this from To do to Done Mar 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug is:critical https://bisq.wiki/Critical_bug is:priority PR or issue marked with this label is up for compensation on:Linux waiting for author
Projects
Development

No branches or pull requests

6 participants