Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 5392 - String actions in ibm_hosts cause the keyboard to lock
String actions in ibm_hosts cause the keyboard to lock
Product: Red Hat Linux
Classification: Retired
Component: x3270 (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Karsten Hopp
Depends On:
  Show dependency treegraph
Reported: 1999-09-27 08:07 EDT by Pekka Savola
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-11 10:50:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pekka Savola 1999-09-27 08:07:01 EDT

Having string actions in /usr/X11R6/lib/X11/x3270/ibm_hosts
cause the keyboard to lock up - you must use x3270 special
action 'Reset' to wake it up again.  This effectively
renders all ibm_hosts scripting useless.

Example ibm_hosts (doesn't work):
test primary test.xxx.fi test\n
Example 2 (doesn't work either):
test primary test.xxx.fi String(test) Enter()
Example 3 (does work):
test primary test.xxx.fi Reset()

This is probably related to the other x3270 problem I have

There were no problems using x3270 3.0 source code.
Comment 1 Jeff Johnson 2000-10-23 10:14:38 EDT
Does this problem still exist in x3270-3.2.13?
Comment 2 Pekka Savola 2000-10-23 16:43:39 EDT
Unfortunately, x3270 is no longer used here so I can't test it. :-(
Comment 3 Stephen John Smoogen 2003-01-23 16:17:20 EST
This problem still exists in the Red Hat Linux 7.3 version of x3270-3.2.18-2 and
will test against the 8.0.x betas but I do not see changes large enough to fix this.
Comment 4 Karsten Hopp 2003-02-11 10:50:15 EST
I'm using minor variations of examples 1 and 2 to log on to our  MP3000 with x3270-3.2.19-4 

Note You need to log in before you can comment on or make changes to this bug.