Java.io.FileNotFoundException: /home/roman/.config/icedtea-web/deployment.properties (No existe el archivo o el directorio) at java.base/java.io.FileInputStream.open0(Native Method) The application has not been initialized, for more information execute javaws/browser from the command line and send a bug report. : Fatal: Launch Error: Could not launch JNLP file. This is the output when I try to launch from firefox a jnlp application: Denying permission: ("" "") So, how can I achieve that icedtea-8 is installed with openjdk-8, and not 11? My guess is that I installed some PPA that now produces this situation where jdk-11 is a more up to date choice than any jdk-8 package. I suspect that jdk-11 does not include some libraries required for this.
While it is expected to depend on openjdk-8, not 11 (according to ubuntu packages website). Icedtea-netx librhino-java libtagsoup-java openjdk-11-jre So I removed everything, started installation again, and found that apt-get install icedtea-8-plugin depends on: ca-certificates-java default-jre default-jre-headless icedtea-8-plugin After inspection, some libraries seem to be missing in Java. All the jnlp applications I tried give execution error. Once you've cleared the cache, try to run the Jalview JNLP file again.I'm on Ubuntu MATE 18.04. Locate any jalview instances in your applications cache and remove them (usually, select the application and hit the delete or 'X' button).If you have access to a terminal, you can usually open the console with
Locate and open the java console on your system (in your control panel or systems settings, but may also be in the Utilities section of the Applications folder on OSX.If you are using the latest version of the JNLP then you need to open the Java Web Start console panel, and flush any application caches and remove any old versions of Jalview listed in the application viewer. To fix, first make sure that you are using the latest version of the Jalview JNLP file (right-click or apple-click to save this link to a file) to launch jalview.
This error (and others like it) is raised when an old version of the Jalview Webstart JNLP is being used to launch the latest version of the application (for instance, because you have created your own JNLP file in order to increase the memory available to Jalview).
0 kommentar(er)
