The labels in the connections tab refer to the type of connection it was when established. If you see an "Ultrapeer" connection as a leaf, and then somehow become promoted to an Ultrapeer, you'll see still that "Ultrapeer" connection -- that means there's a big bug. Your servent should never change status and retain its old connections. If an Ultrapeer sees an "Ultrapeer" connection, or a Leaf sees a "Peer" or "Leaf" connection, there's a large problem.

We'll look into that GUI thing, though I suspect it'll be difficult to track down. You've updated all the video drivers and there's still a problem?

I noticed almost immediatley... and I miss it!

A number of versions ago, the spinning Lime was replaced by the 'blinking' plug... personally I preferred the spinning Lime!

LimeNut:

the problem is most likely in the version of X that you're using. The next version of Limewire will not freeze anymore, but will unfortunately not be able to download magnet links on such systems.

You should see if there are any updates available for your X environment, and potentially upgrade the entire distro (there is Suse 9.2 out afaik)

I just installed 4.3.3 on my SuSE 9.1 machine at work (which also has JRE 1.5.0_01 but a different video card and -- obviously -- different drivers) and it had the same GUI corruption.

It looked ok until I tried to download something. So I think the code to add the download sub-window must be the source of the problem.

One thing that's different, and may be a clue, is that the Linux version acted like my windowed copy of LW was actually running full-screen, even though it wasn't. In other words, if I did maximize LW, then I could see the bottom controls. Re-windowing it 'lost' them. I checked this on my Windows machine though and it's not the same; still a mystery there.

I did a net install of SuSE 9.2 onto another partition on my hard drive and the freezes also occur in SuSE 9.2 running X.org 6.8.1 (using java 1.4.2_06 that came with it).

Here is the kill -SIGQUIT output during the freeze in SuSE 9.2 with Java 1.4.2_06.

Attached Files

limewire-4.3.3-beta-gui-freeze-in-suse-9.2.txt (20.5 KB, 253 views)

Also, here is the kill -SIGQUIT output during the 15 to 30 second freeze in java 1.5.0 in SuSE 9.2.

Attached Files

limewire-4.3.3-beta-gui-freeze-in-suse-9.2-and-java-1.5.0.txt (17.7 KB, 242 views)

lime nut:

. There isn't much we can do about it, we haven't been able to reproduce it on our linux systems which use virtually the same setup as Suse 9.2.

The next version will not freeze anymore, unfortunately magnet links will be available only through the command line.

Nothing wrong in this dump. There's no deadlock and all threads are in normal wait state.

Probably a freeze caused in your X11 display server by another X11 application: possibly a screensaver not starting properly or wanting to grab your mouse/keyboard input focus?
Does it occur if you disable your X11 screensaver?

Also check the status of your window manager. There may be some uncaught conditions. (Look at its log). Does it occur if you switch to another window manager (Motif, twm, ...)?

Also check the status of your X11 font server. May be there are logs indicating that it fails to initialize some font properly. May be caused by a corrupted font, or a font feature not working properly. This may cause the X11 display server to wait for a reply from the X11 font server. (check the logs too). I've read that the support and integration of TrueType font servers for X11 display servers was still not finished, or that some features in OpenType fonts were particularly slow or consuming too much resource. (Try disabling the TrueType fonts: does it still occur?)

been running beta for 2 day know i go away from computer and limewire turn i self off all the time even when it is uploading and downloading got all the upto date on java any help with this