Hi all,

I installed Fedora in early September and have been using Limewire under Linux without problem since then. However, I haven't been able to launch last two releases; LimeWire never gets beyond the splash screen and the "Loading messages..." text and I have to kill the process on the command line. I've tried both the installer and .tgz packages, and as a last resort, just renamed the .limewire directory, all to no avail. I have Java 1.5 installed under Fedora Core 3.

Anything else I can do to determine what is going wrong?

interesting. try issuing the following command:

kill -QUIT <process #> from a different console. That will print out some debugging info which can help us find out what's going on.

Mod, please move this thread to the linux forum.

[colin@ariel limewire4.2.2]$ 5~Full thread dump Java HotSpot(TM) Client VM (1.5.0-b64 mixed mode, sharing):

"AWT-EventQueue-0" prio=1 tid=0x0835c690 nid=0x6f1c in Object.wait() [0xf6e2e000..0xf6e2f040]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Unknown Source)
at java.awt.EventQueue.getNextEvent(Unknown Source)
- locked <0xcd97e1a0> (a java.awt.EventQueue)
at java.awt.EventDispatchThread.pumpOneEventForHierar chy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
at java.awt.Dialog$1.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierar chy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

"TimerQueue" daemon prio=1 tid=0x0806f670 nid=0x6f1b in Object.wait() [0x02888000..0x028881c0]
at java.lang.Object.wait(Native Method)
- waiting on <0xcdadde40> (a javax.swing.TimerQueue)
at javax.swing.TimerQueue.run(Unknown Source)
- locked <0xcdadde40> (a javax.swing.TimerQueue)
at java.lang.Thread.run(Unknown Source)

"AWT-Shutdown" prio=1 tid=0x0806efe0 nid=0x6f1a in Object.wait() [0x02908000..0x02909140]
at java.lang.Object.wait(Native Method)
- waiting on <0xcd971ab8> (a java.lang.Object)
at java.lang.Object.wait(Unknown Source)
at sun.awt.AWTAutoShutdown.run(Unknown Source)
- locked <0xcd971ab8> (a java.lang.Object)
at java.lang.Thread.run(Unknown Source)

"AWT-XAWT" daemon prio=1 tid=0x084799c0 nid=0x6f16 runnable [0x02806000..0x02806f40]
at sun.awt.X11.XToolkit.waitForEvents(Native Method)
at sun.awt.X11.XToolkit.run(Unknown Source)
at sun.awt.X11.XToolkit.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

"Java2D Disposer" daemon prio=1 tid=0x0846c800 nid=0x6f15 in Object.wait() [0x0261e000..0x0261f0c0]
at java.lang.Object.wait(Native Method)
- waiting on <0xcd9940e0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
- locked <0xcd9940e0> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
at sun.java2d.Disposer.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

"Low Memory Detector" daemon prio=1 tid=0x080a0300 nid=0x6f13 runnable [0x00000000..0x00000000]

"CompilerThread0" daemon prio=1 tid=0x0809edb0 nid=0x6f12 waiting on condition [0x00000000..0x0073db28]

"Signal Dispatcher" daemon prio=1 tid=0x0809de48 nid=0x6f11 runnable [0x00000000..0x00000000]

"Finalizer" daemon prio=1 tid=0x08099120 nid=0x6f10 in Object.wait() [0x00608000..0x00608e40]
at java.lang.Object.wait(Native Method)
- waiting on <0xcd8f44b8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
- locked <0xcd8f44b8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(Unknown Source)
at java.lang.ref.Finalizer$FinalizerThread.run(Unknow n Source)

"Reference Handler" daemon prio=1 tid=0x08098408 nid=0x6f0f in Object.wait() [0x003f3000..0x003f3fc0]
at java.lang.Object.wait(Native Method)
- waiting on <0xcd8f4538> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Unknown Source)
at java.lang.ref.Reference$ReferenceHandler.run(Unkno wn Source)
- locked <0xcd8f4538> (a java.lang.ref.Reference$Lock)

"main" prio=1 tid=0x0805b628 nid=0x6f0d in Object.wait() [0xfeffd000..0xfeffd678]
at java.lang.Object.wait(Native Method)
- waiting on <0xcd970220> (a java.awt.Component$AWTTreeLock)
at java.lang.Object.wait(Unknown Source)
at java.awt.Dialog.show(Unknown Source)
- locked <0xcd970220> (a java.awt.Component$AWTTreeLock)
at javax.swing.JOptionPane.showOptionDialog(Unknown Source)
at javax.swing.JOptionPane.showMessageDialog(Unknown Source)
at javax.swing.JOptionPane.showMessageDialog(Unknown Source)
at com.limegroup.gnutella.gui.MessageService.showErro r(MessageService.java:74)
at com.limegroup.gnutella.gui.GUIMediator.showError(G UIMediator.java:1440)
at com.limegroup.gnutella.gui.SaveDirectoryHandler.sh owSaveDirectoryWindow(SaveDirectoryHandler.java:28 )
at com.limegroup.gnutella.gui.SaveDirectoryHandler.ha ndleSaveDirectory(SaveDirectoryHandler.java:109)
at com.limegroup.gnutella.gui.Initializer.initialize( Initializer.java:172)
at com.limegroup.gnutella.gui.Main.main(Main.java:49)

"VM Thread" prio=1 tid=0x08095950 nid=0x6f0e runnable

"VM Periodic Task Thread" prio=1 tid=0x080bafa8 nid=0x6f14 waiting on condition

Looks like there's a problem with your save directory, and there's a deadlock in showing the error message about it. Oddly enough, it looks like the deadlock is occuring in a single trace. It locks the AWTTreeLock and then is waiting on locking it again.

The problem may be that I have my shared/ directory in the root, because I have it on a separate partition -- a separate drive actually. However, this directory obviously has write permission, so that shouldn't be an issue.

Isn't it strange that the same thread has both acquired the lock, and is now waiting for itself the same lock?

- waiting on <0xcd970220> (a java.awt.Component$AWTTreeLock)
at java.lang.Object.wait(Unknown Source)
at java.awt.Dialog.show(Unknown Source)
- locked <0xcd970220> (a java.awt.Component$AWTTreeLock)

It looks like an unexpected behavior in AWT, probably coming from a compatibility issue between AWT (a core component of Java2D for graphic display) and the version of X11 (XFree86 or X.org?) running on your Redhat installation, possibly because some normally mandatory display event was captured by some tools.

Do you use the regular (RedHat supported) version of the X-Window display server?

So, if you use X.org instead of XFree86, you should know that this is a split from the historic XFree86 branch, which is still in beta, and not widely tested. I suggest you reinstall XFree86 instead if you have changed for a beta version of X.org (Java2D has still not been tested on the X.org implementation, given that XFree86 was until very recently the top windowing system for Linux on PC desktops).

Do you use some custom desktop window manager, instead of the standard Redhat-supported desktop?

Do you use some mouse-enhancing tools, that capture the mouse and don't release it correctly, so that the windowing tree of your desktop gets garbled?

Yes, I am using the standard packages included in the official Fedora distribution.

Quote:

Do you use some custom desktop window manager, instead of the standard Redhat-supported desktop?

Nope, just Gnome.

Quote:

Do you use some mouse-enhancing tools, that capture the mouse and don't release it correctly, so that the windowing tree of your desktop gets garbled?

No, nothing of the kind. Perhaps it is a Gnome problem, but how would I be able to determine this?