Package Details: bisq 1.9.14-1

Git Clone URL: https://aur.archlinux.org/bisq.git (read-only, click to copy)
Package Base: bisq
Description: Cross-platform desktop application that allows users to trade national currency (dollars, euros, etc) for bitcoin without relying on centralized exchanges
Upstream URL: https://bisq.network
Licenses: AGPL3
Conflicts: bisq-bin, bisq-git
Provides: bisq
Submitter: dmp1ce
Maintainer: dmp1ce
Last Packager: dmp1ce
Votes: 63
Popularity: 0.51
First Submitted: 2017-07-05 14:43 (UTC)
Last Updated: 2023-10-18 00:14 (UTC)

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

wag commented on 2024-02-16 15:33 (UTC)

@kostrse I don't think this is a good idea for this package. We are building from source here, so we need to use the specific java version recommended by the developers of the app. In their build instructions on github, the devs specify: Bisq currently works with JDK 11 and JDK 15, and later they state: If you do not have JDK 11 installed, check out scripts in the scripts directory or download it manually from https://jdk.java.net/archive/. (Source: https://github.com/bisq-network/bisq/blob/master/docs/build.md). This makes you think that JDK 11 is the optimal version to build Bisq. I don't think we should losen the dependency here, since users may face several bugs (or the app may not compile at all) when using a version of java that isn't recommended by upstream. Then, these same users could come here to complain that this package is broken, buggy, etc. In short, this isn't a good idea.

@chovy this issue is not related to this package, but rather to an inability of gpg to retrieve the key from the key server. Maybe it can be fixed by running gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys B493319106CC3D1F252E19CBF806F422E222AA02 , and then try installing this package again. However, I recommend you check if your DNS config is working properly, and maybe change your DNS server also, then try again. I never had any issue using cloudflare's 1.1.1.1.

kostrse commented on 2023-12-18 00:08 (UTC)

Would be great to not have a hard dependency on specific version of JDK. Could you losen the dependency?

chovy commented on 2023-12-02 14:47 (UTC)

:: (1/1) Parsing SRCINFO: bisq
gpg: error reading key: No public key

 :: PGP keys need importing:
 -> B493319106CC3D1F252E19CBF806F422E222AA02, required by: bisq
:: Import? [Y/n] 
:: Importing keys with gpg...
gpg: keyserver receive failed: Server indicated a failure
 -> problem importing keys

chovy commented on 2023-11-28 14:05 (UTC)

:: PGP keys need importing: -> B493319106CC3D1F252E19CBF806F422E222AA02, required by: bisq :: Import? [Y/n] :: Importing keys with gpg... gpg: keyserver receive failed: Server indicated a failure -> problem importing keys

wag commented on 2023-11-04 22:44 (UTC)

@waasl , good to see your problem was solved. So in reality your problem was kinda the opposite of what I was thinking: this PKGBUILD makes sure to compile bisq with java-11-openjdk (good to know that, actually), so the issue was that your system was trying to run the app with a much older version of java (8). But I knew that setting the right archlinux-java environment would fix it in the end, one way or another.

But there is still the issue of needing to call directly /opt/bisq/bin/desktop to be able to run Bisq, which works, but isn't ideal. The maintainer should try to look at this issue and solve it. My humble guess is that the problem lies in the /opt/bisq/bisq-desktop file, where it tries to start Bisq with this command: ./gradlew :desktop:startBisqApp . However, I don't know what would be the best way to solve this.

waasl commented on 2023-11-03 07:25 (UTC)

@wag Thank you, you solved my issue!

archlinux-java get

output:

java-8-openjdk

this command solved my issue (I did not even need to rebuild):

sudo archlinux-java set java-11-openjdk

wag commented on 2023-10-28 04:06 (UTC) (edited on 2023-10-28 04:09 (UTC) by wag)

@waasl , For me running /opt/bisq/bin/desktop always works and starts bisq, regardless if I built it with yay -S bisq, with paru -S bisq, or manually with git and makepkg. In my humble opinion, the issue seems to be on the /opt/bisq/bisq-desktop file, where it tries to start bisq with ./gradlew :desktop:startBisqApp ...

In your case though, it looks like you've compiled bisq with a more recent version of java than the supported one... Are you sure you have java-11-openjdk set as your default java environment before compiling bisq?? That could be the issue there on your system. Run:

archlinux-java get

And verify whether it outputs java-11-openjdk. If not, you need to run this command before building bisq:

sudo archlinux-java set java-11-openjdk

Then, make sure to clean-build bisq again.

waasl commented on 2023-10-22 21:15 (UTC)

terminal:

$ /opt/bisq/bin/desktop

output:

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: bisq/desktop/app/BisqAppMain has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
    at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:621)

This happens after a fresh install with

yay -S bisq

dmp1ce commented on 2023-10-22 00:59 (UTC)

@wag and @waasl, I'm not sure about the issue. I'm not working on solving the issue right now. Perhaps try bisq-bin until I can apply a fix.

wag commented on 2023-10-21 20:03 (UTC) (edited on 2023-10-21 20:11 (UTC) by wag)

@dmp1ce and @waasl , Ok so I just found out the file /opt/bisq/bisq-desktop (actually a bash script, I haven't noticed before, thought it was a binary) of the current build (1.9.14-1) tries to start bisq with this command:

./gradlew :desktop:startBisqApp

So of course it won't work. I have no idea what this ./gradlew file or directory is doing there. I tried replacing

./gradlew :desktop

with

/opt/bisq/bin/desktop 

(there should be a blank space at the end, after "desktop"), so I replaced that on the /opt/bisq/bisq-desktop file, and now running bisq-desktop or /usr/bin/bisq-desktop now works and bisq starts. Of course, clicking on the icon also started working again. But as I said before, I'm just a simple user messing around with this stuff, I have no idea if "my fix" is ideal or not. Waiting for the maintainer to have a look at this.