This is also true for Arch Linux, so I hopefully join this thread.
Your problem is different. The startjAlbum-sh file of the zip archive will only work if you either use a Java that is pre-linked with JavaFX (our bundled ones are) or manually refer to the "lib" folder of the OpenJFX SDK via a --module-path parameter. You also need to use the --add-modules and specify the 3 JavaFX modules that jAlbum relies on. For a complete example from my Mac, see here:
/Library/Java/JavaVirtualMachines/jdk-13.0.1.jdk/Contents/Home/bin/java --module-path=/Library/Java/javafx-sdk-13/lib --add-modules javafx.graphics,javafx.swing,javafx.web -Xmx2000M -jar ~/Projects/JAlbum/JAlbum.jar
I'm sorry it has become so complicated, but Oracle decided to make the JavaFX module, which was part of Java, an external module. For the non zip releases we bundle a pre-linked Java. With that one, there is no need to fiddle with --add-modules and --module-path.
If you like to roll your own pre-linked Java to run jAlbum on, you can use the jlink command. Here's how we pre-link the Linux Java using jlink:
#/bin/bash
VER=13.0.1
JDKPATH=jdk-${VER}
JREPATH=jre-${VER}-mini
rm -rf ${JREPATH}
${JDKPATH}/bin/jlink -J-Xmx4g --strip-debug --module-path ${JDKPATH}/jmods:javafx-jmods-${VER} --add-modules java.base,java.compiler,java.datatransfer,java.desktop,java.logging,java.prefs,java.scripting,java.xml,javafx.base,javafx.controls,javafx.fxml,javafx.graphics,javafx.media,javafx.swing,javafx.web,jdk.dynalink,jdk.internal.le,jdk.jsobject,jdk.scripting.nashorn.shell,jdk.scripting.nashorn,jdk.xml.dom,jdk.unsupported.desktop,jdk.charsets,jdk.localedata,jdk.crypto.cryptoki,jdk.crypto.ec,java.management --output ${JREPATH}
