installation problem with Limewire 4.12
 

I have java 1.5 installed, seems OK.
However, couldn't install Limewire using the rpm, got
error: Failed dependencies:
j2re >= 1.4.1 is needed by LimeWire-free-4.12.3-0.i386
So I installed using the 'nodeps' option.
Attempting to start limewire now just produces the hovering splash screen, and on
cancelling I get the following message in the shell:
Starting LimeWire...
Java exec found in PATH. Verifying...
Suitable java version found [java = 1.5.0_07]
Configuring environment...
Loading LimeWire:

************************************************** ****************
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.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)

I had limewire installed previously but have removed the .limewire directory.

Anything else to try??

Ta, Pete

re problem
 

Hi,
problem was no problem apart from impatience.
When I went away and made a cup of tea after starting Limewire, the install dialog was waiting on return.
We have to wait a minute or two after a new install.
Ta,
Pete

We have to wait a minute or two after a new install.

I timed it at 5 minutes this morning---that can't be right! Splash screen sits on ALL my desktops getting in the way the whole time.

Is there some option I should use to hurry things along?

ta
pete

Nobody out there? OK, in case anyone else has this problem, I realised that it was related to an upgrade from Mandriva 2005 to 2006. I found that with Java 1.4 the problem partially disappeared in that the splash screen didn't sit in the middle of all my desktops, just the desktop I started LimeWire on. Still unhappy with the 5 minute wait, I found the answer lies in changing the firewall options to "Do Nothing(not recommended)". I could download with this setting, but I'm not sure whether uploading was allowed, without adjusting the (shorewall) firewall to accept calls to the "listen on" port in that option.
Anyway, back to normal, now.

Curious fix for your scenario!

Actualy, I noticed the same problem with 4.12.6 on SuSE 10.0, running java 1.5.0

You can install with the --nodeps option, but in this case the system maintance via apt will fail - unfulfilled dependencies.

Can one of the package maintainers maybe fix the dependency problem? Thx!