I started looking into the complete graphical lockup of all classpath
awt/swing apps, and I think this may be the problem:
This adds a bunch of 1.6 methods and constants to our AWT, and fixes
some issues in the peers. Together with these patches and a bunch of
modifications on OpenJDK, I was able to use the GTK peers in OpenJDK to
get Swing running:
* gnu/java/awt/peer/gtk/GtkComponentPeer.java
(postMouseEvent): Use MouseEvent constructor with absolute coordinates
to avoid deadlock (over getLocationOnScreen()).
as a dump at the lockup shows:
Thread 6 (Thread -1400042608 (LWP 10064)):
#0 0x00d63402 in __kernel_vsyscall ()
#1 0x007d1a0e in __lll_mutex_lock_wait () from /lib/libpthread.so.0
#2 0x007cd883 in _L_mutex_lock_79 () from /lib/libpthread.so.0
#3 0x007cd3ad in pthread_mutex_lock () from /lib/libpthread.so.0
#4 0x00121aac in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#5 0x00121a30 in gdk_threads_enter () from /usr/lib/libgdk-x11-2.0.so.0
#6 0x00785b55 in
Java_gnu_java_awt_peer_gtk_GtkComponentPeer_gtkWindowGetLocationOnScreen
(env=0x806a33c, obj=0xaffa1fc0, jpoint=0xaffddf18)
at gnu_java_awt_peer_gtk_GtkComponentPeer.c:523
Currently testing a fix...
Francis
