EVALUATION

This bug's Notes suggest that the original Fix Delivered/Available status was incorrect.  The problem was never fixed in Java 5.0, and it was never intended to be fixed.  Instead, it was fixed in a later version, Java 6.0 (covered under sub-CR 2121519).  There were code changes put back in Java 5.0, but they did not fix the problem.  Instead, they enabled a workaround.

This bug probably should be closed as "Will Not Fix" in Java 5.0, with a note that workarounds exist.
                                     

WORK AROUND

There are two different workarounds:

1. Set the _AWT_USE_TYPE4_PATCH environment variable to false before starting the Java application.  For example: 
export _AWT_USE_TYPE4_PATCH=false

2. Toggle the "Num Lock" key on the keyboard to disable Num Lock mode.
                                     

EVALUATION

/****************************************************
 ****************************************************
 ****************************************************/

<B>To enable fix in 1.5.0, please set _AWT_USE_TYPE4_PATCH=false environment variable.</B>

/************************************************
 ************************************************
 ************************************************/ (now it is visible, isn't it:-)
                                     

SUGGESTED FIX

A quick fix is of workaround variety: allow processing _AWT_IGNORE_XKB environment variable not only on Linux but on every Unix platform.

------- src/solaris/native/sun/awt/awt_GraphicsEnv.c -------
*** /tmp/sccs.54jMhE    Wed Nov  3 15:07:10 2004
--- awt_GraphicsEnv.c   Wed Nov  3 15:07:00 2004
***************
*** 694,707 ****
  #endif
      awt_lock = (*env)->NewGlobalRef(env, this);

- #ifdef __linux__
    if (getenv("_AWT_IGNORE_XKB") != NULL &&
        strlen(getenv("_AWT_IGNORE_XKB")) > 0) {
        if (XkbIgnoreExtension(True)) {
          printf("Ignoring XKB.\n");
        }
    }
- #endif

      dpy = awt_display = XOpenDisplay(NULL);
  #ifdef NETSCAPE
--- 694,705 ----
###@###.### 11/3/04 12:08 GMT
                                     

EVALUATION

I think the problem is with the window system or java's ability to set the correct keybindings for the window system.  I logged into the user's system and did a remote display of bugster to both gnome and CDE on my sparc/solaris8 system.. both worked fine.
###@###.### 10/5/04 17:35 GMT
In existing native key-handling code for both Motif and XAWT, we should carefully process keysyms if NumLock is on, distinguishing subcases "XKB on/off" && "keysym selection convention  Xsun/Xorg".
###@###.### 2005-2-18 09:31:39 GMT