I will research this issue more I swear when I get 30 minutes to myself, but wanted to make a topic in case it is a bug that needs to be fixed.
I just upgraded to PopOS 22.04. GanttProject won’t launch. Here is my terminal output
┬─[richard@pop-os:~]─[06:22:34 AM]
╰─>$ ganttproject
Searching for Java in /usr/share/ganttproject/runtime/bin/java
...missing or not executable
Searching for Java in /usr/bin/java
...found openjdk version "18-ea" 2022-03-22
...this seems to be an old Java Runtime
Searching for Java in /usr/lib/jvm/java-1.18.0-openjdk-amd64/bin/java
...found openjdk version "18-ea" 2022-03-22
...this seems to be an old Java Runtime
Searching for Java in /usr/lib/jvm/java-18-openjdk-amd64/bin/java
...found openjdk version "18-ea" 2022-03-22
...this seems to be an old Java Runtime
JavaVM executable not found.
You may want to set the path to the root of your Java Runtime installation
in JAVA_HOME environment variable or pass it to ganttproject in --java-home argument
Maybe an issue with the installed version of OpenJDK after the upgrade? Here is what I have installed.
┬─[richard@pop-os:~]─[01:42:28 PM]
╰─>$ sudo apt list --installed | grep jdk
[sudo] password for richard:
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
openjdk-18-jre-headless/jammy,now 18~36ea-1 amd64 [installed,automatic]
openjdk-18-jre/jammy,now 18~36ea-1 amd64 [installed,automatic]
I’ve tried removing GanttProject and re-installing. I haven’t tried removing openjdk and reinstalling yet. Like I said, I’m interested in researching this issue when I have more time later.
BTW, I have tried to launch Java 17 with the same approach I use Java 11.
This is the log of the crash when opening the dialog window to open a file.
C:\Users\00966789r\ganttproject.log
GanttProject 3.1.3103
Settings file:
location: C:\Users\00966789r.ganttproject
size:7319
is readable: true
java.class.path: ;.\eclipsito.jar;.
java.home: C:\Users\00966789r\Downloads\jre-17.0.3-full
java.ext.dirs: null
java.io.tmpdir: c:\temp
java.runtime.version: 17.0.3+7-LTS
java.vendor: BellSoft
java.vm.name: OpenJDK 64-Bit Server VM
java.vm.vendor: BellSoft
java.vm.version: 17.0.3+7-LTS
os.arch: amd64
os.name: Windows 10
os.version: 10.0
sun.java.command: com.bardsoftware.eclipsito.Launch --verbosity 1 --version-dirs plugins;~/.ganttproject.d/updates --app net.sourceforge.ganttproject.GanttProject -log true
user.country: ES
user.dir: C:\Users\00966789r\Downloads\ganttproject-3.1.3100
user.home: C:\Users\00966789r
user.language: es
user.timezone: Europe/Madrid
may 04, 2022 2:38:58 P. M. biz.ganttproject.LoggerImpl error
GRAVE: Can’t set awtAppClassName (needed on Linux to show app name in the top panel)
may 04, 2022 2:38:59 P. M. net.sourceforge.ganttproject.GPLogger log
INFORMACIÓN: Deleting old auto-save files
may 04, 2022 2:39:04 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: Creating main frame…
may 04, 2022 2:39:04 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 1. loading look’n’feels
may 04, 2022 2:39:06 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 2. loading options
may 04, 2022 2:39:07 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 3. creating menus…
may 04, 2022 2:39:07 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 4. creating views…
may 04, 2022 2:39:07 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 5. calculating size and packing…
may 04, 2022 2:39:08 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 6. changing language …
may 04, 2022 2:39:08 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 7. first attempt to restore bounds
may 04, 2022 2:39:08 P. M. biz.ganttproject.LoggerImpl debug
DETALLADO: 8. finalizing…
may 04, 2022 2:39:15 P. M. net.sourceforge.ganttproject.GPLogger logToLogger
ADVERTENCIA: class impl.org.controlsfx.skin.NotificationPaneSkin (in unnamed module @0x5a94eeef) cannot access class com.sun.javafx.scene.traversal.ParentTraversalEngine (in module javafx.graphics) because module javafx.graphics does not export com.sun.javafx.scene.traversal to unnamed module @0x5a94eeef
java.lang.IllegalAccessError: class impl.org.controlsfx.skin.NotificationPaneSkin (in unnamed module @0x5a94eeef) cannot access class com.sun.javafx.scene.traversal.ParentTraversalEngine (in module javafx.graphics) because module javafx.graphics does not export com.sun.javafx.scene.traversal to unnamed module @0x5a94eeef
at impl.org.controlsfx.skin.NotificationPaneSkin.(NotificationPaneSkin.java:117)
at org.controlsfx.control.NotificationPane.createDefaultSkin(NotificationPane.java:227)
at javafx.controls/javafx.scene.control.Control.doProcessCSS(Unknown Source)
at javafx.controls/javafx.scene.control.Control$1.doProcessCSS(Unknown Source)
at javafx.controls/com.sun.javafx.scene.control.ControlHelper.processCSSImpl(Unknown Source)
at javafx.graphics/com.sun.javafx.scene.NodeHelper.processCSS(Unknown Source)
at javafx.graphics/javafx.scene.Node.processCSS(Unknown Source)
at javafx.graphics/javafx.scene.Node.processCSS(Unknown Source)
at javafx.graphics/javafx.scene.Node.processCSS(Unknown Source)
at javafx.graphics/javafx.scene.Node.processCSS(Unknown Source)
at javafx.graphics/javafx.scene.Scene.doCSSPass(Unknown Source)
at javafx.graphics/javafx.scene.Scene$ScenePulseListener.pulse(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.Toolkit.lambda$runPulse$2(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.Toolkit.runPulse(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.Toolkit.firePulse(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.pulse(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.pulse(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.pulseFromQueue(Unknown Source)
at javafx.graphics/com.sun.javafx.tk.quantum.QuantumToolkit.lambda$runToolkit$11(Unknown Source)
at javafx.graphics/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(Unknown Source)
at javafx.graphics/com.sun.glass.ui.win.WinApplication._runLoop(Native Method)
at javafx.graphics/com.sun.glass.ui.win.WinApplication.lambda$runLoop$3(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
Java 9 introduced modules and module encapsulation, stronger restrictions on accessing classes. Encapsulation violations were warnings until Java 16, and since Java 16 they are errors. Those programs which did not define module exports (that was the case for GP prior to 3.2) would fail on Java 16+ even if they run fine on Java 11.
Java 18 is just a launcher issue. Launchers for Linux and macOS check if Java Runtime is ok, and they are not yet aware of Java 18.