Description of problem: jnlp program stopped working after an upgrade. How reproducible: Start the jnlp file from the commandline Actual results: /usr/bin/javaws: line 89: /usr/lib/jvm/jre-openjdk/bin/java: No such file or directory Expected results: Programs starts Additional info: # alternatives --config java There is 1 program that provides 'java'. Selection Command ----------------------------------------------- *+ 1 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre/bin/java
Hi! Ugh, may you veryfi manually thatthis directory donot exists? [jvanek@jvanek ~]$ ll /usr/lib/jvm/jre-openjdk/bin/java -rwxr-xr-x. 1 root root 331 Jan 17 15:04 /usr/lib/jvm/jre-openjdk/bin/java or simialr? This is standart jpackage provided direcotry and its absence will be critical. Can you try to reinstall openjdk or update to recently release 2.4.4.1?
This directory doesn't exists. I already tried the following to no avail: mkdir /usr/lib/jvm/jre-openjdk/bin ln -s /usr/bin/java java yum reinstall icedtea-web yum install java-1.8.0-openjdk yum remove java-1.7.0-openjdk yum install java-1.7.0-openjdk And editing the path in/usr/bin/javaws. ls /usr/lib/jvm/jre-openjdk/bin/java ls: cannot access /usr/lib/jvm/jre-openjdk/bin/java: No such file or directory
I'm wondering about: yum install java-1.8.0-openjdk How is this workflow behave if you miss it? I have made many somehow corrupted installations and was not able to reproduce your issue.
I tried the commands below without result. I got the selinux error during the previous upgrade. Maybe these are related? yum remove java-1.7.0-openjdk icedtea-web java-1.8.0-openjdk yum install java-1.7.0-openjdk icedtea-web
Then it may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1056187
Thanks! The following commands did the trick: > yum reinstall java-1.7.0-openjdk-headless follow by > alternatives --config java (and choosing the new one as default) > alternatives --remove java > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre/bin/java > is solving the issue
*** This bug has been marked as a duplicate of bug 1056187 ***