LimeWire on Linux: This is how it worked for me....
 

Installing LineWire

I had the problem that LimeWire worked only with root authorisations. Setting SUID rood didnt help, downloads still were not working. I fixed it the following:

login as root
install limewire to /opt/LimeWire

create a script, lets say lw, and put it to /usr/local/bin (or somewhere else, e.g. $HOME). Assuming you are joe_user, the script is:
-------- snip
#!/bin/sh
XAUTHORITY=/home/joe_user/.Xauthority; export XAUTHORITY
DISPLAY=:0.0; export DISPLAY
/opt/LimeWire/LimeWire

-------- snap

next you need sudo installed on your machine. Pls. Note that there was a security announcement last (look at portal.suse.de/en).
With visudo, configure sudo and add the following line:

joe_user ALL=NOPASSWD:/usr/local/bin/lw

now you can start limewire with

sudo lw

.....and enjoy sucking songz!

Gents,
just wanted to reanimate this old thread to ask: How did other Linux users got it running without being logged in as root?

Axe

Hi Axe.
I´m using SuSE 7.1 and did it on the following way (sorry for my engish):

First I´ve installed the newest JRE from Sun for RH-Linux by using the instructions in the SuSE-Support-Database (How to install an RPM-Package made for other Distributions. You can find it by the keyword "java").

After that was done I changed the link "java" in "/usr/lib/" which pointed on the original JDK1.1.8-directory in the same directory to the new Runtime-E. (for all who wants to know: ln -s /usr/java/jre1.3.1 /usr/lib/java).

First I tried to install the "Linux-Version" of LimeWire, but I had too much trouble with it.
So I used the "LimeWireOther.zip"-Version for other OS and installed it with: "java -classpath LimeWireOther.zip install"

No stupid messages, everything went ok and I installed it into /usr/local/lw.

These steps were done as root but all other user on the system can use LimeWire too without any problems.

Bye

He, would be too easy ....
I´ve found out that after installing a new RPM-Package with Yast on SuSE-Linux, SuSE-Config (runnig automatically after the RPM-installation) changes the link from the new JRE to the old JDK 1.1.8. LimeWire also runs with the old one on my system.

So, if you would like (or need) to run the new runtime, it seems so that you have to change the link each time Suse-Config was runnig. If anyone has an idea, how it is possible to fix this problem ... you are welcome :)

If you first deinstall the old (1.1.8) Java?

Regarding the authorisation stuff, I still work with Suse 6.3 (no time for updates :-((
Have you checked - as a stadndard user w/o root authorisations - that a download works? Everything else worked also before (lw running with SUID root), but not the download.

Cheers
Axe

You can avoid running LimeWire as root or using sudo simply by changing the permissions on the LimeWire root directory.