JDK-4453472 : keyboard input blocked in SMC
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: solaris_9,1.4.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_8,solaris_9
  • CPU: generic,sparc
  • Submitted: 2001-05-02
  • Updated: 2001-09-20
  • Resolved: 2001-06-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.0 beta2Fixed
Related Reports
Duplicate :  
Relates :  
Description
Effective with Java 1.4.0-beta-b61, SMC is exhibitting the following problems
that did not occur with 1.4.0-beta-b59 or 1.3.1-beta-b15.

These can be seen by running one of the following environments:

  - You must be running build37.  SMC will be b55-built bytecodes
    running on a b61 JVM.

  - You can run an earlier OS build as long as you have b61 installed
    as the default JVM, and install the AI nightly build referenced
    at http://smpt.east/projects/SMC/install.html.  Follow the 
    "Cluster install" instructions.  You should run "nuke_admin"
    first to purge any previous versions.  Again, SMC will be b55-built
    bytecodes running on a b61 JVM.

  - b61-built bytecodes for SMC can be found at /net/divet.east/files/s81/b61-pkgs.
    Simply follow the same instructions as mentioned at the above URL, accept
    cd to this directory before running "install_admin".

After installation, set JAVA_HOME to point to the location of B61 and
run "/usr/sadm/bin/smc".  When the console comes up, note the following
problems:

1) The border around work-in-progress icon in the upper-right corner is now 
   too big.  Note the gap along the top and bottom of the image.  This
   did not happen before.

2) Invoke Console->Preferences.  Note the grey square in the top-left
   corner of the dialog.  This is supposed to be a question mark image
   and has always shown before.

3) Invoke Console->Preferences.  Click on the Fonts tab.  Click on any
   of the "Change..." buttons.  Click on the Color button.  Select a color.
   Click Ok, click Ok, click Ok.  Now go to any dialog that requires text
   input and note that keyboard input is blocked.  There doesn't appear
   to be any way to get it unblocked other than by restarting the console.
   
   The quickest way to a dialog might be to click on the "Devices and Hardware" 
   turner in the left-side navigation pane, then click on "Serial Ports".  
   Log in, and after the list of ports is displayed, select one and invoke
   Actions->Properties.

4) In step 3) above, when you click on "Serial Ports" (or any tool in the
   navigation pane), you will be prompted with a login dialog upon the
   1st tool selection.  When you type your password fast, the character
   mask does not seem to keep up.  That is, my password has 6 characters,
   yet when I type it fast, I only see the '#' mask character echoed
   twice.  Note that this does not interfere with authentication, which
   does succeed, but the character mask behavior is different than previously.

5) In step 3) above, when you click on "Serial Ports", the right-side pane
   says "Loading Serial Ports Tool", followed by "Loading Serial Ports".
   Both text messages are supposed to be displayed in the same purple color
   as the icon image to the immediate left.  However, in b61, they appear
   in the color black.

6) In step 3) above, note also how the main window completely fills in
   with grey and then repaints itself before the dialog comes up - this too,
   is new behavior which has not been seen previously.  This does NOT happen
   if you double-click on the object to invoke properties, as opposed to
   the Actions->Properties menu item.

7) Difficult to reproduce, but sometimes objects displayed in the right-side
   pane are invisible.  A subsequent refresh makes them visible.

8) For any tool which displays it's main object list as large icons (say,
   System Configuration->Users->Users from the navigation pane), try resizing
   the console window just enough so that you fill up an entire row.  Then
   right-click thr right-most object and select "Properties".  When the
   dialog comes up, note how keyboard input is blocked on any text field.
   Unlike in step 3) however, it doesn't appear to remain blocked, as 
   dismissing the dialog and invoking some other dialog with a textfield 
   seems to work fine.

I don't know if these are all manifestations of the same bug.  But I'm
including them in one bug report because they all seem to be related to
something gone awry relative to processing the AWT event queue, and perhaps
a pattern can be easily seen if they're all listed together.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta2 FIXED IN: merlin-beta2 INTEGRATED IN: merlin-beta2 VERIFIED IN: merlin-beta3
14-06-2004

EVALUATION AWT did not integrate into either build 60 or build 61. The main integrations were Tools and plugin. If the information that the VM is build 61 is accurate, I imagine this would rule out the known rendering issues with hotspot in build 55. eric.hawkes@eng 2001-05-02 Talked to james.melvin@east about the plugin integration. He couldn't think of any issue offhand that might cause this. However, he did mention that there was a problem with pulling images from a jar file. Note: it appears that this application is launched using Java Webstart. eric.hawkes@eng 2001-05-03 Apparently build 59 of merlin used build 10 of JWS, while builds 60 and 61 of merlin use build 15 of JWS. Since no GUI groups integrated into builds 60 or 61, it seems likely that this problem is caused by the new JWS binary. eric.hawkes@eng 2001-05-03 The description says that this happens when the admin tool is started with the /usr/sadm/bin/smc command. I installed the packages and verified that this command-line does not involve Java Web Start nor Plug-In. It launches the admin tool directly using the java command. Thus, this is not a Java Web Start nor Plug-In related problem. rene.schmidt@eng 2001-05-03 The plugin integration changed slightly more than the plugin code, but I'm not sure whether it could have affected this particular bug. Commit to fix in merlin-beta2 (Solaris 9 problem). I've already contacted the submitter about the procedure for getting a fix in an earlier release, if necessary. eric.hawkes@eng 2001-05-03 Got the following information from the submitter: I changed the java launch command in /usr/sadm/lib/smc/bin/smc from: ${JAVA} "${JAVAARGS[@]}" -Djava.security.policy=${VIPER_HOME}/policy/smcconsole.policy -Dviper.argv0=$0 -Dviper.home=${VIPER_HOME} -Dviper.rthome=${SMC_RTHOME} -Dviper.display=${X_DISPLAY} -Dviper.legacydisplay=${DISPLAY} -mx64M com.sun.management.viperimpl.console.BaseConsoleOptionsManager "$@" to: ${JAVA} "${JAVAARGS[@]}" -Xint -Djava.security.policy=${VIPER_HOME}/policy/smcconsole.policy -Dviper.argv0=$0 -Dviper.home=${VIPER_HOME} -Dviper.rthome=${SMC_RTHOME} -Dviper.display=${X_DISPLAY} -Dviper.legacydisplay=${DISPLAY} -mx64M com.sun.management.viperimpl.console.BaseConsoleOptionsManager "$@" but it didn't make any difference. After I changed the color, keyboard input was still frozen. FWIW: SMC implements the applet model, in that code is downloaded from the server. I didn't do anything to the server, but only added the -Xint option on client startup - in case any of this matters. So, I suppose this rules out hotspot as a culprit. eric.hawkes@eng 2001-05-04 Possibly related to the new T2 threading library? We need a thread dump (ctrl backslash) of the application. We also need the call stack for each thread obtained from dbx. eric.hawkes@eng 2001-05-07 Can reproduce problems 3 and 8 in focus-follows-mouse, but not in the default CDE configuration (click to focus). We believe these are likely to be the same focus bug. eric.hawkes@eng 2001-05-16 The Description of this bug report lists a number of problems, many of which are unrelated. Because these problems are likely to have different causes, different levels of importance, and probably belong to different groups, the submitter has agreed to decompose the problems that are not related to blocked keyboard input into other bug reports. From this point forward, we will consider this particular bug report to pertain only to the blocked keyboard. In order to avoid confusion about the scope of this bug report, I have changed the Synopsis from "keyboard input blocked and images not rendering" to "keyboard input blocked in SMC" eric.hawkes@eng 2001-05-16 This bug was fixed as part of the fix for 4453933. See that BugID for details. david.mendenhall@east 2001-06-03
16-05-2001