5

When trying to launch the JavaFX "Hello world" sample, the native libraries are not found -- or, they are rejected. The symptom is a "No toolkit found" exception. There seems to be some specificity to macOS, as signing is mentioned at some point.

What I did (on macOS 10.14.6):

  1. Installed Java 12 from https://adoptopenjdk.net
  2. Downloaded the JavaFX 12 SDK for macOS from http://gluonhq.com/download/javafx-12-0-2-sdk-mac. Unzipped it as $WRK_DIR/javafx-sdk-12.0.2
  3. Downloaded the JavaFX "hello world" sample from https://github.com/openjfx/samples. Unzipped it as $WRK_DIR/samples-master

Then I followed the instructions of the Getting Started (here or here). I chose the simplest path: no IDE, no build system like Maven, non-modular app, nothing but plain CLI.

$ WRK_DIR=$(pwd)
$ ls -lF
total 0
drwxr-xr-x@ 4 bruno  staff  128 19 jul 16:25 javafx-sdk-12.0.2/
drwxr-xr-x@ 8 bruno  staff  256 31 jul 10:18 samples-master/
$ PATH_TO_FX=$WRK_DIR/javafx-sdk-12.0.2/lib
$ ls $PATH_TO_FX 
javafx-swt.jar      javafx.properties   libglib-lite.dylib  libjfxwebkit.dylib
javafx.base.jar     javafx.swing.jar    libgstreamer-lite.dylib libprism_common.dylib
javafx.controls.jar javafx.web.jar      libjavafx_font.dylib    libprism_es2.dylib
javafx.fxml.jar     libdecora_sse.dylib libjavafx_iio.dylib libprism_sw.dylib
javafx.graphics.jar libfxplugins.dylib  libjfxmedia.dylib   src.zip
javafx.media.jar    libglass.dylib      libjfxmedia_avf.dylib
$ javac -version
javac 12.0.2
$ cd samples-master/CommandLine/Non-modular/CLI/hellofx
$ javac --module-path $PATH_TO_FX --add-modules=javafx.controls -d out $(find src -name "*.java")
$ find . -type f
./out/hellofx/HelloFX.class
./out/hellofx/Launcher.class
./src/hellofx/HelloFX.java
./src/hellofx/Launcher.java

Up until trying to launch:

$ java -version
openjdk version "12.0.2" 2019-07-16
OpenJDK Runtime Environment AdoptOpenJDK (build 12.0.2+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 12.0.2+10, mixed mode)
$ java --module-path $PATH_TO_FX --add-modules=javafx.controls -cp out hellofx.HelloFX
Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
   <stack trimmed>
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found
   <stack trimmed>
Exception in thread "main" java.lang.reflect.InvocationTargetException
   <stack trimmed>
Caused by: java.lang.RuntimeException: No toolkit found
   <stack trimmed>

The research I did led me to think that the native libraries are not found. So I tried to add $PATH_TO_FX to LD_LIBRARY_PATH and DY LD_LIBRARY_PATH with no better result. Following this comment I added -Dprism.verbose=true to the command line:

$ java -Dprism.verbose=true --module-path $PATH_TO_FX --add-modules=javafx.controls -cp out hellofx.HelloFX
Prism pipeline init order: es2 sw 
Using Double Precision Marlin Rasterizer
Using dirty region optimizations
Not using texture mask for primitives
Not forcing power of 2 sizes for textures
Using hardware CLAMP_TO_ZERO mode
Opting in for HiDPI pixel scaling
Prism pipeline name = com.sun.prism.es2.ES2Pipeline
Loading ES2 native library ... prism_es2
GraphicsPipeline.createPipeline failed for com.sun.prism.es2.ES2Pipeline
java.lang.UnsatisfiedLinkError: no prism_es2 in java.library.path: [/Users/bruno/Library/Java/Extensions, /Library/Java/Extensions, /Network/Library/Java/Extensions, /System/Library/Java/Extensions, /usr/lib/java, .]
   <trimmed the rest of errors that are essentially the above>

So indeed there is a problem of (at least) libprism_es2.dylib not being found. I then tried to add $PATH_TO_FX to java.library.path:

$ java -Dprism.verbose=true -Djava.library.path=$PATH_TO_FX --module-path $PATH_TO_FX --add-modules=javafx.controls -cp out hellofx.HelloFX
Prism pipeline init order: es2 sw 
Using Double Precision Marlin Rasterizer
Using dirty region optimizations
Not using texture mask for primitives
Not forcing power of 2 sizes for textures
Using hardware CLAMP_TO_ZERO mode
Opting in for HiDPI pixel scaling
Prism pipeline name = com.sun.prism.es2.ES2Pipeline
Loading ES2 native library ... prism_es2
GraphicsPipeline.createPipeline failed for com.sun.prism.es2.ES2Pipeline
java.lang.UnsatisfiedLinkError: /Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib: dlopen(/Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib, 1): no suitable image found.  Did find:
    /Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib: code signature in (/Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.
   <...>

Now the library is found, but is not considered valid.

Oscarmatox
  • 73
  • 1
  • 9
  • Does it work if you create new simple project containing main class with `System.out.println("Hello World")` ? – bakero98 Aug 18 '19 at 12:53
  • For me this version of the JDK and JFX works without problems on the same version of macOS as yours and I don't have to mess around with the libary path. Possible differences: I use the Oracle provided OpenJDK and JavaFX via Maven. Have you checked your environment? Maybe you have defined some variables which interfere with your command line options. – mipa Aug 18 '19 at 14:09
  • 1
    There is an [issue](https://github.com/AdoptOpenJDK/openjdk-build/issues/1211) with AdoptOpenJDK 11.0.4 (probably the same was happening with 12.0.2), and native libraries failed to be extracted with the message `no suitable image found...mapped file has no cdhash, completely unsigned`. Can you try [OpenJDK 12](https://jdk.java.net/12/)? – José Pereda Aug 18 '19 at 17:59
  • @bakero98 Yes, a simple non-JavaFX program works. – Oscarmatox Aug 18 '19 at 20:37
  • @JoséPereda This is indeed the exact same error. I downloaded the test program mentioned in the issue and I get the same (erroneous) behaviour. Thanks for pointing that. I'll try with OpenJDK 12 asap. – Oscarmatox Aug 18 '19 at 20:51
  • @JoséPereda And I confirm that everything is working as expected with OpenJDK 12 (as opposed to AdoptOpenJDK 12). Thanks for you help. You may want to turn your comment as an answer, so that I accept it. – Oscarmatox Aug 19 '19 at 15:40

2 Answers2

3

In your command line:

$ java -Dprism.verbose=true --module-path $PATH_TO_FX \
    --add-modules=javafx.controls -cp out hellofx.HelloFX

everything looks okay, so it should work fine. In fact, you get it running, until it fails with:

GraphicsPipeline.createPipeline failed for com.sun.prism.es2.ES2Pipeline
java.lang.UnsatisfiedLinkError: /Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib: \
    dlopen(/Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib, 1): no suitable image found.  \
    Did find: /Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib: \
code signature in (/Users/bruno/try/javafx-sdk-12.0.2/lib/libprism_es2.dylib) \
not valid for use in process using Library Validation: \
mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.

There is a bug reported to AdoptOpenJDK 11.0.4 about native libraries that cannot be loaded with 11.0.4+11.2 on Mac, and produces the exact same error message.

However, you are running AdoptOpenJDK 12.0.2, and your project works for you with OpenJDK 12, so it seems this bugs also extends to AdoptOpenJDK 12.0.2+10.

So while this is fixed, you can use OpenJDK 12. Note that there has been already reported that 12 fails.

EDIT

I can confirm that the latest 11 prerelease for Mac works (it actually says Java version 11.0.5).

The same goes with the latest 12 prerelease for Mac, it works fine.

José Pereda
  • 44,311
  • 7
  • 104
  • 132
1

Unfortunately the released version of AdoptOpenJDK 12.0.2 does not work correctly

openjdk version "12.0.2" 2019-07-16
OpenJDK Runtime Environment AdoptOpenJDK (build 12.0.2+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 12.0.2+10, mixed mode)
Manfred Riem
  • 31
  • 1