Thanks goes out to Peter Stern and John James who both had the answer.
This bug has been fixed in Patch Kit 3 and up. It only happens when coming
in from XDMCP.
Specific patch was Patch 334: OSF440X11-010B
Info from patch kit release notes:
Patch: Problem in dtterm with system using XDMCP
State: New
This patch fixes a problem in which ^C fails to work in dtterm when
logged in to a 4.0E or 4.0F system using XDMCP.
--Original message---
After upgrading to V4.0f, Ctrl-C, as well as other commands don't always
work properly. This seems to only happen when someone is logged in via
another Xserver. In this situation, people are using Xwin32 or Xceed on
PCs, however I've tested it with a variety of other tools and it does it
with them too, so I figure this must be a v4.0f thing, since it doesn't do
it on any of our V4.0d machines(or any other Unix we use)
Here is what happens.
I bring up a dtterm, and press Ctrl-C, it does what I would expect,
basically acts as a carriage return if I am not running anything.
Now, if I start an GUI app up(without &) and try a Ctrl-C in the term
window, it doesn't work. It echo's a ^V, and just sits there.
What is really interesting, if I hit Caps lock, and then the Ctrl-C again
it sends a ^C and the application shutsdown.
Anyone have any clue about this? It happens on ALL v4.0f machines we have,
upgraded ones, and freshly installed V4.0f machines. They are all at Patch
Kit 2.
-grant
---------------------------------------------------------------------------
Grant Schoep, grant_at_storm.com
System/Network Administrator
L3 Communications Telemetry & Instrumentation
San Jose,CA
Received on Thu Jul 27 2000 - 16:57:45 NZST