broken with newer java

Bug #2034752 reported by drewp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
freeplane (Debian)
New
Unknown
freeplane (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Out of the box, freeplane doesn't start up:

% freeplane
*org.knopflerfish.framework.readonly=true
*org.knopflerfish.gosg.jars=reference:file:/usr/share/freeplane/core/
*org.freeplane.user.dir=/home/drewp
*org.freeplane.basedirectory=/usr/share/freeplane
org.freeplane.globalresourcedir=/usr/share/freeplane/resources
*java.security.policy=/usr/share/freeplane/freeplane.policy
*org.osgi.framework.storage=/usr/share/freeplane/fwdir
Exception in thread "main" java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release
 at java.base/java.lang.System.setSecurityManager(System.java:425)
 at org.freeplane.launcher.Launcher.launchWithoutUICheck(Launcher.java:279)
 at org.freeplane.launcher.Launcher.main(Launcher.java:87)

% dpkg -l | grep jre
ii default-jre 2:1.17-74 amd64 Standard Java or Java compatible Runtime
ii default-jre-headless 2:1.17-74 amd64 Standard Java or Java compatible Runtime (headless)
ii openjdk-17-jre:amd64 17.0.8+7-1~23.04 amd64 OpenJDK Java runtime, using Hotspot JIT
ii openjdk-17-jre-headless:amd64 17.0.8+7-1~23.04 amd64 OpenJDK Java runtime, using Hotspot JIT (headless)
ii openjdk-19-jre:amd64 19.0.2+7-0ubuntu4 amd64 OpenJDK Java runtime, using Hotspot JIT
ii openjdk-19-jre-headless:amd64 19.0.2+7-0ubuntu4 amd64 OpenJDK Java runtime, using Hotspot JIT (headless)
ii openjdk-8-jre:amd64 8u382-ga-1~23.04.1 amd64 OpenJDK Java runtime, using Hotspot JIT
ii openjdk-8-jre-headless:amd64 8u382-ga-1~23.04.1 amd64 OpenJDK Java runtime, using Hotspot JIT (headless)

But this works:

% JAVA_CMD=/usr/lib/jvm/java-17-openjdk-amd64/bin/java freeplane

So I think freeplane needs to depend on, and then somehow use, an earlier version of java.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting.

I found a corresponding Debian bug report with the same issue, so I have attached a bug watch.

Changed in freeplane (Ubuntu):
status: New → Confirmed
Changed in freeplane (Debian):
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.