Package Details: bisq 1.9.9-1

Git Clone URL: (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:
Licenses: AGPL3
Conflicts: bisq-bin, bisq-git
Provides: bisq
Submitter: dmp1ce
Maintainer: dmp1ce (freimair)
Last Packager: dmp1ce
Votes: 56
Popularity: 0.082299
First Submitted: 2017-07-05 14:43 (UTC)
Last Updated: 2023-01-08 20:53 (UTC)

Pinned Comments

freimair commented on 2021-12-02 13:19 (UTC) (edited on 2021-12-09 20:42 (UTC) by freimair)

To address the recent errors with failing checksums:

There is an upstream issue:

not much we can do for now.

freimair commented on 2021-02-02 12:23 (UTC) (edited on 2021-02-02 12:23 (UTC) by freimair)

I just updated the build to fetch the newly available signed source tarball off github. finally.

If you stumble over the message that a key is not trusted just do a gpg --recv-keys 29CDFD3B and you should be good

Latest Comments

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

dmp1ce commented on 2023-01-09 17:00 (UTC)

@dmrobotix, see

I'm not sure if this is something I can fix in the PKGBUILD.

dmrobotix commented on 2023-01-09 16:31 (UTC) (edited on 2023-01-09 16:32 (UTC) by dmrobotix)

I'm getting the following error with bsdtar and yay is unable to finish building and installing the latest version as a result.

bsdtar: Option --no-read-sparse is not supported Usage: List: bsdtar -tf <archive-filename> Extract: bsdtar -xf <archive-filename> Create: bsdtar -cf <archive-filename> [filenames...] Help: bsdtar --help ==> ERROR: Failed to create package file. -> error making: bisq

dmp1ce commented on 2022-12-28 21:28 (UTC) (edited on 2022-12-28 21:33 (UTC) by dmp1ce)

@janders, what you did is exactly right for updating and should be safe to install. I figured out why my build wasn't working and I should have 1.9.8 pushed shortly.

There is also the bisq-bin package if this one doesn't work for some reason.

janders commented on 2022-12-28 19:26 (UTC) (edited on 2022-12-28 19:29 (UTC) by janders)

The latest update (1.9.8) is required, no trades are allowed with older versions. Since the AUR doesn't have the 1.9.8 yet, this is what I did to the PKGBLD file:

Edit the pkgver line to be:


I downloaded the source code from GitHub, calculated the SHA256 checksum, and edited the sha256sums line with it:


I was then able to build and install the package. But I'm not exactly sure if this is safe to run. Is what I've done sane? What drawbacks, risks, or implications are there to doing this?

dmp1ce commented on 2022-12-24 10:57 (UTC)

I'm having trouble with the build. Does anyone have a suggestion?

Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :
Project :common => no found

FAILURE: Build failed with an exception.

* Where:
Build file '/build/bisq/src/bisq-1.9.8/build.gradle' line: 200

* What went wrong:
A problem occurred evaluating root project 'bisq'.
> Cannot run program "git": error=2, No such file or directory

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at


pinball_wizard commented on 2022-03-03 18:33 (UTC)


Great! Fixed it!

dmp1ce commented on 2022-03-03 11:55 (UTC)

@jvybihal I had trouble getting bisq to build without the wrapper. I am getting the following errors:

Welcome to Gradle 7.4!

Here are the highlights of this release:
 - Aggregated test and JaCoCo reports
 - Marking additional test source directories as tests in IntelliJ
 - Support for Adoptium JDKs in Java toolchains

For more details see

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'bisq'.
> Dependency verification failed for configuration ':classpath'
  5 artifacts failed verification:
    - log4j-2.17.1.pom (org.apache.logging.log4j:log4j:2.17.1) from repository MavenRepo
    - log4j-api-2.17.1.jar (org.apache.logging.log4j:log4j-api:2.17.1) from repository MavenRepo
    - log4j-api-2.17.1.pom (org.apache.logging.log4j:log4j-api:2.17.1) from repository MavenRepo
    - log4j-core-2.17.1.jar (org.apache.logging.log4j:log4j-core:2.17.1) from repository MavenRepo
    - log4j-core-2.17.1.pom (org.apache.logging.log4j:log4j-core:2.17.1) from repository MavenRepo
  If the artifacts are trustworthy, you will need to update the gradle/verification-metadata.xml file by following the instructions at

  Open this report for more details: file:///build/bisq/src/bisq-1.8.2/build/reports/dependency-verification/at-1646308114172/dependency-verification-report.html

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at

BUILD FAILED in 2m 11s

Do you have any suggestions? Maybe the wrapper is setting the "classpath"?

dmp1ce commented on 2022-03-03 11:30 (UTC)

@pinball_wizard You may want to checkout this:

Perhaps you are missing a font package.

pinball_wizard commented on 2022-02-22 21:11 (UTC) (edited on 2022-02-22 21:12 (UTC) by pinball_wizard)

Hi! I have build correctly, but when I install bisq package and start it i have this error with JavaFX...any advice?

Error: JavaFX detected no fonts! Please refer to release notes for proper font configuration
feb-22 22:03:28.979 [JavaFX Application Thread] ERROR Error during app init java.lang.ExceptionInInitializerError: null
    at bisq.desktop.main.MainView$1.computeValue(
    at bisq.desktop.main.MainView$1.computeValue(
    at javafx.beans.binding.ObjectBinding.get(
    at javafx.beans.binding.ObjectExpression.getValue(
    at com.sun.javafx.binding.ExpressionHelper.addListener(
    at javafx.beans.binding.ObjectBinding.addListener(
    at bisq.desktop.main.MainView.initialize(
    at bisq.desktop.common.view.InitializableView.initialize(
    at javafx.fxml.FXMLLoader.loadImpl(
    at javafx.fxml.FXMLLoader.loadImpl(
    at javafx.fxml.FXMLLoader.load(
    at bisq.desktop.common.fxml.FxmlViewLoader.loadFromFxml(
    at bisq.desktop.common.fxml.FxmlViewLoader.load(
    at bisq.desktop.common.view.CachingViewLoader.load(
    at com.sun.javafx.application.PlatformImpl.lambda$runLater$10(
    at java.base/ Method)
    at com.sun.javafx.application.PlatformImpl.lambda$runLater$11(
    at Method)
    at java.base/
Caused by: java.lang.NullPointerException: null
    at com.sun.javafx.font.LogicalFont.<init>(
    at com.sun.javafx.font.LogicalFont.getLogicalFont(
    at com.sun.javafx.font.LogicalFont.getLogicalFont(
    at com.sun.javafx.font.PrismFontFactory.createFont(
    at com.sun.javafx.font.PrismFontLoader.loadFont(
    at javafx.scene.text.Font.<init>(
    at javafx.scene.text.Font.getDefault(
    at javafx.scene.control.Tooltip.<clinit>(
    ... 25 common frames omitted

dmp1ce commented on 2022-02-16 01:10 (UTC)

@jvybihal, I agree. Thanks for the suggestion and the reference to your package.