|
Seems to be related to X settings or the network (I
vote for X). Is annoying but not problematic. Some Google searching revealed the
following 3 different solutions:
Solution 1:
I found a possible explanation and fix for this
problem. I was
also having problems running JBuilder 3.5's debugger, and my fix for that problem seems to have fixed this one as well. My primary machine is a laptop that is only
connected to a LAN
part-time. My /etc/hosts file looked like the standard, with 127.0.0.1 aliased to "localhost" and "localhost.localdomain," and my Fully Qualified Domain Name (FQDN) aliased to my real IP address. In the case of JBuilder, the debug process was attempting to bind to the running applet using the FQDN, not "localhost." Since I was at home with the laptop not connected to the LAN, this debug process could not find my machine based on the FQDN or Real IP address. My workaround (and this should only be necessary
for
non-networked machines) is to edit /etc/hosts and alias my FQDN to 127.0.0.1, like so: 127.0.0.1 (FQDN here) localhost.localdomain
localhost
Again, this workaround seems to have not only fixed
my JBuilder debugging problem, but also the Keybinding problem mentioned above. It remains to be seen whether this will break anything when I actually *do* connect this laptop to the LAN. Solution 2:
Run:
xprop -root -remove
_MOTIF_DEFAULT_BINDINGS
at the prompt and it should take care of the
warnings.
Solution 3:
edit /usr/X11R6/lib/X11/bindings/xmbind.alias file
and add a line like so:
"The XFree86 Project, Inc"
pc
and edit the 'pc' file and comment out the "Meta
Ctrl <Key> Insert" line since that generates an error.
Finally, you could try other JVMs for Linux. Sun,
IBM, and Blackdown all make Linux JVMs. For different applications/window
managers different JVMs work better. There seems to be no magic formula that
works in all cases. My experience is that Java Swing works better under Gnome
than KDE. However, I haven't tried Gnome 2 or KDE 3.
Sean Durity
|