***Special Note***

Only Blackdown uses .java_wrapper that I am aware of at this time. Any other java vm will not require symlinking this to /usr/bin as java.

****************


1.) How familiar are you with linux console commands? You are saying that when you type this command:

rpm -qa | grep j2

You get no output?

Otherwise, it sounds like a typo somewhere.

If you do get an output, please post it here.

2.) I would like to know if you are using, Sun's, Blackdown's, or IBM's java VM. (This would be answered by your output from Question #1 if you are not certain yourself.

Eagerly awaiting your answers,
Altoine

3.) You are using bash?

If there isn't any typo you might simply have to logout and then back in again to update your path. Otherwise, it will not work before unless you manually type the export commands directly on the command line and not in .bashrc or .bash_profile.

altoine

Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre (ie /usr/java/j2sdk1.4.0, /usr/java/j2re1.3.1, /usr/lib/j2re1.3.1, etc):

I put where I downloaded my j2sdk1.3.1-02b-FCS:

/usr/lib/j2sdk1.3.1

into my PATH in my .bash_profile (.bashrc will work, also):

export JAVA_HOME=/usr/lib/j2sdk1.3.1
export PATH=$JAVA_HOME/bin:$PATH

After doing that, I remove kaffe from my system but I have a dependency problem with my wizard packages. I do this command to keep that program around:

(If the above path is added to .bash_profile or .bashrc, you really won't have to remove kaffe if you reboot or logout and then login again before running the LimeWire Installer) This is necessary in order for the path changes can take effect. Depending on your setup, just opening another terminal will not use your new changes. Once the system is using your changes, you will not have to mess with them until you do a java vm upgrade.

Instructions for removing kaffe without breaking anything:

rpm -e kaffe --nodeps

This removes all instances of kaffe binaries from /usr/bin.

**Special Note**
rpm -e jdkgcj --nodeps

for those whom have this package installed on their system.
**End Special Note**


After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root. I don't know a way to install it system wide as root yet without making a script.):

./LimeWireLinux.bin

Installation works. Program installed, running, and functional. I discovered that I had to install the program as user instead of trying to set it systemwide as root.

Hi,

I did the suggestions, and it fixed my problems in the first run.

I got up a screen asking for shared folder a.s.o.

That worked okey, but when it tried to start the LimeWire application I got up a screen with the limewire logo and a message stating it was loading the gui.

Then the app exited with this error mesage:
./LimeWire: line 1: 1199 Segmentation fault "/home/helene/programs/jre1.3.1_03/bin/java" com.zerog.lax.LAX "/home/helene/programs/LimeWire/./LimeWire.lax" "/tmp/env.properties.1146"

Any ideas?

(I'm running suse professional 7.2)

Hi again,



I found in another thread this solution that worked for me




http://www.gnutellaforums.com/showth...&threadid=7148

nDiScReEt just a quick thanks.

Worked like a charm.

.bash_profile?

Im a newbie.....

where is this and how do i find it?

Thank you. Your problem and solution are both well appreciated. I had came across that solution a long time ago but I had never came across a situation where I needed it implemented. I will add that to the installation guide that I haven't regrettably finished yet. I have a new problem that as far as I have seen on this list, no one has come across it yet. Once, I solve that installation issue, I will indeed have THE ultimate installation and troubleshooting guide.

altoine

it is in your home directory of your user.

(example:

suppose your user login name is yesm

/home/yesm/.bash_profile)

If you don't have .bash_profile .bashrc is a good substitute.

any file with a "." (period) before the name of the file or directory means that it is "hidden". Doing a "ls" or "ls -l" will not find the file. While "ls -a" or "ls -a .bash*" will!

altoine

Add me to the list of Linux LimeWire "L-users"

I have read all the threads in this session and have followed the instructions, but to date I still haven't seen any improvement in the install. In short, LimeWire still cannnot find the PATH to my Java virtual machine.

Here are my specs:
I have this installation path for my java:
/usr/java/j2re1.4.0_01

I have created a symbolic link to:
/usr/bin/java
with this server path:
/usr/lib/j2re1.4.0_01/bin/.java_wrapper

The symbolic link was created, so the directory path seems to be valid.

I have edited my .bash_profile to read:
export Java_HOME=/usr/java/j2re1.4.0._01
export PATH=$JAVA_HOME/bin:$PATH

After making these updates, I log out as root and then type:
sh ./LimeWireLinux.bin and receive the missing virtual path error.

So, I'm not sure how to proceed from here. Any clues?

That depends... the link can be broken as it should be in your case. You only need to create a link to /usr/bin/java with .java_wrapper ONLY if it is a jvm from www.blackdown.org.
Your version seems to be a different sort. under your java bin directory should be a java, javac, etc that you can link to the /usr/bin directory :

ln -s /usr/lib/j2re1.4.0/bin/java /usr/bin/java

and

ln -s /usr/lib/j2re1.4.0/bin/javac /usr/bin/javac


I have edited my .bash_profile to read:
export Java_HOME=/usr/java/j2re1.4.0._01
export PATH=$JAVA_HOME/bin:$PATH
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
All wrong above. Close but not for *nix useage. It should read:

export JAVA_HOME=/usr/lib/j2re1.4.0
export PATH=$JAVA_HOME/bin:$PATH

or

export JAVA_HOME=/usr/lib/j2re1.4.0_01
export PATH=$JAVA_HOME/bin:$PATH

depending on the actual path to your jvm directory. You have it listed as /usr/lib/j2re1.4.0 in one instance and then have the path listed as j2re1.4.0_01 in another. Everything is predominately case sensitive in *nix (linux, unix, freebsd, etc).
This should fix your problem and I will update/upload the Installation Instructions on how to install using any environment and any jvm from virtually any source. My apologies for not doing this sooner but I was away for a few weeks. Deep in rebuilding my own projects from the ground up.

altoine