top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Java symbolic links broken on Fedora 19

0 votes
396 views

I have a system that I upgraded from Fedora 18 to 19 recently and I just installed eclipse, but it says that there's no JVM when I try and run it. I noticed that /usr/bin/java is a symbolic link to
/etc/alternatives/java which is then a symbolic link to
/usr/lib/jvm/jre-1.7.0-openjdk/bin/java but it's actually installed at
/usr/lib/jvm/jre-1.7.0-openjdk.i386/bin/java.

Is this an issue from the update from Fedora 18 to 19? Or is it an issue with the packages in Fedora 19?

posted Jul 27, 2013 by Mandeep Sehgal

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote
 
Best answer

Seems this started with java-1.7.0-openjdk-1.7.0.25-*
run alternatives --config java
then choose your openjdk version path

answer Jul 28, 2013 by Abhay Kulkarni
Similar Questions
+1 vote
After migrating to Fedora-20 /var/log/messages file is missing?

I am migrating from a Fedora 19 to a Fedora 20 host. I used the Fedora 20 live disk to install on the new machine. I have most things transferred over and working, but curiously I don't have any messages or mail log files in /var/log as I do in the F19 host:

+3 votes
Fedup issue with thunderbird after to fedora upgrade?

I upgraded to fedora 20 from fedora 19 using fedup. Everything went well except for some weird issues with Thunderbird. The latter is now giving me a pile of weird permission errors and disk space errors. There is 250GB free space, so I know that is not the problem. Obviously this has something to do with the permissions on the thunderbird folder, but I do not have the knowledge to rectify the problem.

Please suggest how to proceed?

0 votes
Where is the iptables firewall configuration file on Fedora 19?

It's no longer in /etc/sysconfig/iptables.

0 votes
Transmission daemon does not start on Fedora 19

I'm having trouble starting transmission-daemon. When I try to start it with systemctl, it hangs:

 # systemctl start transmission-daemon.service

If I let it be for a few minutes (~5), it finishes with a failure. The log is extremely unhelpful. This is very strange because it was working just fine until a few days ago.

...