On a Windows 11 host, I have Ubuntu 24.04 installed via WSL2. There I installed Java with sudo apt-get install openjdk-8-jdk, which gave me a Java 1.8.0_402.
When I launch Fiji with jaunch + this JDK, it gets stuck at Launching user interface:
You can see that there a second splash screen is showing at this point (or maybe the first one just changed as the flat laf takes over) as there are two progress bars and two "Fiji"'s, one slightly inset to the other.
My Jaunch startup debug is:
[DEBUG] Input arguments processed:
[DEBUG] * hints -> [OS:LINUX, ARCH:X64, --debug]
[DEBUG] * vars -> {app-dir=/home/hinerm/Fiji.app, config-dir=/home/hinerm/Fiji.app/config/jaunch, executable=/home/hinerm/Fiji.app/fiji-linux-x64}
[DEBUG] * userArgs.runtime -> []
[DEBUG] * userArgs.main -> []
[DEBUG] * userArgs.ambiguous -> []
[DEBUG]
[DEBUG] Modes applied:
[DEBUG] * hints -> [OS:LINUX, ARCH:X64, --debug, LAUNCH:JVM]
[DEBUG]
[DEBUG] /--------------------------\
[DEBUG] | CONFIGURING RUNTIME: JVM |
[DEBUG] \--------------------------/
[DEBUG]
[DEBUG] Root paths to search for Java:
[DEBUG] * /usr/lib/jvm/java-1.8.0-openjdk-amd64
[DEBUG] * /home/hinerm/Fiji.app/java/linux-amd64/zulu8.60.0.21-ca-fx-jdk8.0.322-linux_x64
[DEBUG] * /usr/lib/jvm/java-8-openjdk-amd64
[DEBUG]
[DEBUG] Suffixes to check for libjvm:
[DEBUG] * lib/server/libjvm.so
[DEBUG] * jre/lib/amd64/server/libjvm.so
[DEBUG] * lib/server/libjvm.so
[DEBUG] * jre/lib/amd64/server/libjvm.so
[DEBUG] * lib/server/libjvm.so
[DEBUG] * jre/lib/amd64/server/libjvm.so
[DEBUG]
[DEBUG] Discovering Java installations...
[DEBUG] Analyzing candidate JVM directory: '/usr/lib/jvm/java-1.8.0-openjdk-amd64'
[DEBUG] Guessing OS name...
[DEBUG] Reading release file...
[DEBUG] Invoking `"/usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java" Props`...
[DEBUG] -> OS name: LINUX
[DEBUG] Guessing CPU architecture...
[DEBUG] -> CPU architecture: X64
[DEBUG] Guessing Java version...
[DEBUG] * rootString -> java-1.8.0-openjdk-
[DEBUG] * versions8u -> []
[DEBUG] * versionsPrefixed -> [1.8.0]
[DEBUG] -> Java version: 1.8.0
[DEBUG] Successfully discovered Java installation:
[DEBUG] * rootPath -> /usr/lib/jvm/java-1.8.0-openjdk-amd64
[DEBUG] * libjvmPath -> /usr/lib/jvm/java-1.8.0-openjdk-amd64/jre/lib/amd64/server/libjvm.so
[DEBUG] * binJava -> /usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java
[DEBUG] * hints -> [OS:LINUX, ARCH:X64, --debug, LAUNCH:JVM, JAVA:8, JAVA:0+, JAVA:1+, JAVA:2+, JAVA:3+, JAVA:4+, JAVA:5+, JAVA:6+, JAVA:7+, JAVA:8+]
[DEBUG]
[DEBUG] Classpath to calculate:
[DEBUG] * /home/hinerm/Fiji.app/jars/imagej-launcher*.jar
[DEBUG]
[DEBUG] Classpath calculated:
[DEBUG] * /home/hinerm/Fiji.app/jars/imagej-launcher-6.0.2.jar
[DEBUG]
[DEBUG] JVM arguments calculated:
[DEBUG] * -Dij.debug=true
[DEBUG] * -Dscijava.log.level=debug
[DEBUG] * -XX:+UseG1GC
[DEBUG] * -Dpython.cachedir.skip=true
[DEBUG] * -Dplugins.dir=/home/hinerm/Fiji.app
[DEBUG] * -Dimagej.splash=true
[DEBUG] * -Dimagej.dir=/home/hinerm/Fiji.app
[DEBUG] * -Dij.dir=/home/hinerm/Fiji.app
[DEBUG] * -Dfiji.dir=/home/hinerm/Fiji.app
[DEBUG] * -Dfiji.executable=/home/hinerm/Fiji.app/fiji-linux-x64
[DEBUG] * -Dij.executable=/home/hinerm/Fiji.app/fiji-linux-x64
[DEBUG] * -Djava.library.path=/home/hinerm/Fiji.app/lib/linux64
[DEBUG] * -Dscijava.context.strict=false
[DEBUG] * -Dpython.console.encoding=UTF-8
[DEBUG] Added classpath arg: -Djava.class.path=/home/hinerm/Fiji.app/jars/imagej-launcher-6.0.2.jar
[DEBUG]
[DEBUG] Calculating max heap (75%)...
[DEBUG] System reported memTotal of 12469739520
[DEBUG] Added maxHeap arg: -Xmx8919m
[DEBUG]
[DEBUG] Calculating main class name...
[DEBUG] mainProgram -> net.imagej.launcher.ClassLauncher
[DEBUG]
[DEBUG] Main arguments calculated:
[DEBUG] * -ijjarpath
[DEBUG] * jars
[DEBUG] * -ijjarpath
[DEBUG] * plugins
[DEBUG] * net.imagej.Main
Our Fiji distros have a bundled zulu8.60.0.21-ca-fx-jdk8.0.322-linux_x64 JDK and when I unset JAVA_HOME and point to this bundled Java, Fiji starts no problem.
I tested on Windows with another 1.8.0_422 jdk and had no problem launching.
Current debugging questions:
On a Windows 11 host, I have Ubuntu 24.04 installed via WSL2. There I installed Java with
sudo apt-get install openjdk-8-jdk, which gave me a Java1.8.0_402.When I launch Fiji with jaunch + this JDK, it gets stuck at
Launching user interface:You can see that there a second splash screen is showing at this point (or maybe the first one just changed as the flat laf takes over) as there are two progress bars and two "Fiji"'s, one slightly inset to the other.
My Jaunch startup debug is:
Our Fiji distros have a bundled
zulu8.60.0.21-ca-fx-jdk8.0.322-linux_x64JDK and when I unsetJAVA_HOMEand point to this bundled Java, Fiji starts no problem.I tested on Windows with another
1.8.0_422jdk and had no problem launching.Current debugging questions: