Arch Linux User Repository

@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.

@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

@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.

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

@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.

@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.

@dmp1ce I have the same issue that @waasl pointed out on the second part of his comment - The build is successful, however running bisq-desktop or /usr/bin/bisq-desktop or /opt/bisq/bisq-desktop (or even clicking the bisq icon) doesn't work, and the error is the same as his: line 13: ./gradlew: No such file or directory. I'd like to emphasize this isn't an issue only with yay, because it also happens with paru and also when installing it manually with git and makepkg. I was able to reproduce the issue on 2 different computers, it happened regardless if I was updating this bisq package, or if I was installing it for the first time. However, running /opt/bisq/bin/desktop does work and does start bisq, so please try to look at what is happening here, I'm just a user and I don't know what's going on here.

@waasl I'm not sure. I'm familiar with pamac. Maybe just use yay for now? I build and test with clean-chroot-manager which builds from a very clean environment.

Can't install with pamac:

==> Starting build()...
  -> Building bisq...
/var/tmp/pamac-build-otto/bisq/PKGBUILD: line 30: ./gradlew: Permission denied
==> ERROR: A failure occurred in build().
    Aborting...

Instead installed with:

yay -S bisq

On run in terminal:

$ env JAVA_HOME=/usr/lib/jvm/java-11-openjdk /usr/bin/bisq-desktop

output:

/usr/bin/bisq-desktop: line 13: ./gradlew: No such file or directory

please help

@FreddieChopin, Thanks! I applied the changes and the build worked fine.