I installed LimeWireLinux.rpm on my machine (the latest version)... but when I try to run it I get the following feedback:
Starting LimeWire...
Java exec found in PATH. Verifying...
OOPS, you don't seem to have a valid JRE. LimeWire works best with Sun JRE available at
http://www.java.com
OOPS, unable to locate java exec in /usr/lib/ hierarchy
You need to upgrade to JRE 1.4.x or newer from
http://www.java.com
Java exec found in /usr/java/j2sdk1.4.2_13/bin/
Suitable java version found [/usr/java/j2sdk1.4.2_13/bin/java = 1.4.2_13]
Configuring environment...
Loading LimeWire:
java.lang.UnsatisfiedLinkError: /usr/java/j2sdk1.4.2_13/jre/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1503)
at java.lang.Runtime.loadLibrary0(Runtime.java:788)
at java.lang.System.loadLibrary(System.java:834)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:50)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.loadLibraries(Toolkit.java:1437)
at java.awt.Toolkit.<clinit>(Toolkit.java:1458)
at com.limegroup.gnutella.gui.Main.showInitialSplash(Main.java:67)
at com.limegroup.gnutella.gui.Main.main(Main.java:39)
******************************************************************
Something went wrong with LimeWire.
Maybe you're using the wrong version of Java?
(LimeWire is tested against and works best with with Sun's JRE, Java 1.4+)
The version of Java in your PATH is:
java version "1.4.2"
gij (GNU libgcj) version 4.1.1 20061011 (Red Hat 4.1.1-30)
This is the value of my PATH environment variable:
/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/java/j2re1.4.2_13
Now, from the feedback message, it seems to me like the Sun Java conflicts with GNU java... but, Limewire seems to know where the Sun Java is installed. This has never happened to me before... it always worked flawlessly - until now.
Has anyone experienced something like this? Can anyone please tell me what this is all about?