Igor, This has been reported several times before. Although, you have probably contributed a more detailed analysis.
I don't know if xterm should depend on Xaw, but I do know that Xaw needs a hack similar to the lesstif one for VendorShell (from memory). Or maybe it was Xaw3d that needs that. Sorry to be so nebulous. I thought this info might tickle someones memory or fancy. On Tue, 11 Nov 2003, Igor Pechtchanski wrote: > Hi, all, > > I noticed that the xterm executable that comes with the 4.3.0-7 version of > XFree86-bin has problems with keyboard focus. After the mouse pointer > entered and left the window once, the keyboard input is ignored unless the > mouse pointer is in the window. The window apparently keeps the focus, > but no keyboard input is processed. Other executables don't suffer from > this problem, and extracting the xterm from XFree86-bin-4.3.0-4 fixes it. > I've tried running this with Exceed and also remotely on Linux through > ssh. FWIW, here are the relevant files: > > $ ls -l /usr/X11R6/bin/xterm-* > -r-xr-xr-x+ 1 igor Users 262656 Oct 30 11:14 > /usr/X11R6/bin/xterm-4.3.0-7.exe > -rwx--x--x 1 igor Administ 804352 Sep 20 14:52 > /usr/X11R6/bin/xterm-4.3.0-4.exe > > The second file is manually extracted from the XFree86-bin-4.3.0-4 > tarball. The reported version numbers are identical: > > $ xterm-4.3.0-7.exe -version > XFree86 4.2.99.903(174) > $ xterm-4.3.0-4 -version > XFree86 4.2.99.903(174) > > The latter version seems to depend on three extra DLLs: > > $ cygcheck /usr/X11R6/bin/xterm-4.3.0-7.exe | sort -b > /tmp/a7 > $ cygcheck /usr/X11R6/bin/xterm-4.3.0-4.exe | sort -b > /tmp/a4 > $ diff -I xterm -w /tmp/a4 /tmp/a7 > 4a5 > > C:/cygwin/usr/X11R6/bin\cygXaw-7.dll > 6a8 > > C:/cygwin/usr/X11R6/bin\cygXmu-6.dll > 7a10 > > C:/cygwin/usr/X11R6/bin\cygXt-6.dll > > I think libXt used to be linked in statically, but I don't recall xterm > being dependent on libXaw before. > > xterm is the only executable that seems to have changed behavior in my > case (xev, for example, works fine, i.e., respects the window manager's > focus policy). I suspect this new dependence on libXaw is the culprit, as > other Xaw-enabled apps (xfig, editres, etc) are notorious for having a > mind of their own when it comes to keyboard focus. > > Can anyone confirm/deny this? If an unwanted dependence on libXaw was > introduced in the xterm build, can it please be removed somehow? > Thanks, > Igor > -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444