stefanofornari commented on issue #9453: URL: https://github.com/apache/netbeans/issues/9453#issuecomment-4796695800
> SEVERE [global] > java.lang.RuntimeException: No toolkit found > at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:275) > at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:290) > at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:162) > at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:651) > at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:671) > at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:196) > [catch] at java.base/java.lang.Thread.run(Thread.java:1516) > Graphics Device initialization failed for : d3d, sw > Error initializing QuantumRenderer: no suitable pipeline found > java.lang.RuntimeException: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found > at com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:283) > at com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:253) > at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:263) > at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:290) > at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:162) > at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:651) > at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:671) > at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:196) > at java.base/java.lang.Thread.run(Thread.java:1516) > Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: no suitable pipeline found > at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:95) > at com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:125) > ... 1 more Looking into it, this is quite key. There is no sign in the stack trace that the plugin kicked this off, but I suspect it was. However the issue here seems that JavaFX could not initialize at all: `Graphics Device initialization failed for : d3d, sw` A couple of questions for @pinkybitesu 1. where you running netbeans on a virtual environment or remotely on screen sharing? could you try again adding -Dprism.verbose=true to the netbeans starting command line? (i.e. `netbeans64.exe -J-Dprism.order=sw`) 2. in an environment where the issue happens, can you please try running netbeans with `-Dglass.platform=Monocle -Dmonocle.platform=Headless -Dprism.order=sw` and see if it solves the issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
