Fedora RPM installs broken launcher in /opt/bisq/bin/Bisq — fails to launch GUI app

[xhttps]

Description

The RPM installs /opt/bisq/bin/Bisq as the launcher, but it's an ELF shared object, not a runnable binary or script. The .desktop file points to it, so launching from the app menu or terminal fails.

Running it directly gives: Error: Unable to access jarfile /opt/bisq/lib/app/desktop.jar

This makes the entire install unusable. A proper launcher script that runs the required JARs is missing.

Version

1.9.21

Steps to reproduce

1. Install the rpm package on fedora
2. Look in your app launcher -> it probably won't appear
3. Run /opt/bisq/bin/Bisq

Expected behaviour

Either:

• Provide a working launcher script in /opt/bisq/bin/Bisq -Or make /opt/bisq/bin/Bisq a proper binary wrapper that loads JavaFX and the needed JARs.

Actual behaviour

• The application does not show up in the app menu, even though it installs a .desktop file.
• Manually launching the binary at /opt/bisq/bin/Bisq fails unless run as root with xhost +SI:localuser:root workaround.
• When attempting to run it normally, it throws a JavaFX error related to display access:

Authorization required, but no authorization protocol specified Exception in thread "main" java.lang.UnsupportedOperationException: Unable to open DISPLAY

Screenshots

Device or machine

Fedora Workstation 42, Wayland

Additional info

[boring-cyborg[bot]]

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

[suvayu]

I'm also on Fedora, I see a similar, but not identical issue. Bisq fails to launch with this error:

Failed to find JVM in "/opt/bisq/lib/runtime" directory.

I also noticed the sub-directories under /opt/bisq/ lack read and execute permissions for other. So a regular user cannot read any of the files. I fixed them manually

# find /opt/bisq/ -type d -print0 | xargs -0 chmod o+x

[f321x]

I may have a related issue. After installing the v1.9.21 rpm with dnf i did not get a desktop entry (KDE, Fedora 42). When trying to run /opt/bisq/bin/Bisq manually it says i don't have sufficient permissions. So i changed the permissions of the bisq directory (sudo chmod -R o+rX /opt/bisq/) after which i was able to launch Bisq. Something seems off with the installer.

[janvlug]

I may have a related issue. After installing the v1.9.21 rpm with dnf i did not get a desktop entry (KDE, Fedora 42). When trying to run /opt/bisq/bin/Bisq manually it says i don't have sufficient permissions. So i changed the permissions of the bisq directory (sudo chmod -R o+rX /opt/bisq/) after which i was able to launch Bisq. Something seems off with the installer.

Confirming for Fedora 43, Fedora GNOME Wayland.