Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.


#135 xterm - can't type w/cursor not in xterm

Matt Martini

xterm no longer accepts keyboard input if the cursor is
not in the current xterm window.

The window retains focus, but typing is ignored in an
xterm window unless the cursor is over the xterm, as
if focus-follows-cursor is on. However when the cursor
moves off the xterm window, the window retains focus,
however keypresses are ignored. This was not
the previous behavior and it is quite annoying.

I have tested a few window managers (Wmaker, orobor,
twm) and the simptoms are the same which leads me to
beleive that the problem is with xterm (or the 4.1.0

I am running Xfree86 4.1.0 on Mac OSX 10.1.1 I
recently upgraded to XFree86 4.1.0 (compiled from cvs
source). And that is when the problems started.


1 2 > >> (Page 1 of 2)
  • Logged In: YES

    This does seem to be something particular to xterm as other X clients don't have this behavior. Awhile back there was an xterm bug (now fixed) that caused typed characters not to show up if the cursor was in the scroll bar. Perhaps this is related.

    • assigned_to: nobody --> torrey
  • Logged In: YES

    When you say you are running XFree86 4.1.0 compiled from source, are you sure it is really 4.1.0? What does "X -version" give you? I ask because XFree86 4.1.0 does not build correctly without a little tweaking on Mac OS X 10.1.1 last I checked. If you use "xterm -version" you will get something like "XFree86 4.1.0(163)" with the current development version.

  • Logged In: YES

    What version of xterm/XFree86 were you using before that didn't have this problem? This will help in isolating the problem.

  • Matt Martini
    Matt Martini

    Logged In: YES


    Here is the version info. The top version info is current,
    and the second set is my old set. I think the old stuff was
    compiled binaries that I installed, and the new stuff was
    cvs'd from and compiled w/o any tweeks or
    patches. The last time I updated my source and recompiled
    was 2001-11-28, and the problem persists.

    What tweeking should I do to the sources for my OS X 10.1.1

    sarantium.martini 1 $ xterm -version
    XFree86 4.1.0(163)
    sarantium.martini 2 $ X -version

    This is a pre-release version of XFree86, and is not
    supported in any
    way. Bugs may be reported to XFree86@XFree86.Org and
    patches submitted
    to fixes@XFree86.Org. Before reporting bugs in pre-release
    please check the latest version in the XFree86 CVS

    XFree86 Version / X Window System
    (protocol Version 11, revision 0, vendor release 6510)
    Release Date: xx November 2001
    If the server is older than 6-12 months, or if your
    hardware is
    newer than the above date, look for a newer version
    reporting problems. (See
    Operating System: Darwin
    sarantium.martini 3 $

    sarantium.martini 12 $ ./xterm -version
    XFree86 4.1.0(160)
    sarantium.martini 13 $ ./X -version

    This reports the same version as above (prob. because I am
    running the current libs) but the version was XFree86 4.0

  • Matt Martini
    Matt Martini

    • priority: 5 --> 3
  • Logged In: YES

    I have the same problem with Matt. I've been using XDarwin
    1.0.6/XFree86 4.1/OS X 10.1.2 without this problem, and have
    encountered the trouble after I have upgraded to XFree86
    4.2. To reproduce it,

    1) Launch XDarwin with twm & xterm.
    2) Click on title bar of xterm to open twm menu, and select
    3) Moving off the mouse cursor. The focus still remains on
    the window, but keyboard is not connected to xterm.

    I have noticed the same symptom on kterm, the Japanized
    version of xterm. I have compiled it with XDarwin
    1.0.6/XFree86 4.1, which works fine on them. However, the
    same binary starts losing focus on XFree86 4.2. I have
    recompiled kterm on XFree86 4.2 in vain.

    The same trouble seems to occur on some applications (as
    xclipboard), while doesn't on others (as xedit). I still
    cannot figure out any rules.

  • Logged In: YES

    I did a basic check in this afternoon, and found that the problem is
    solved if libXt.6.0.dylib is replaced with the old one. The problem is
    not on the XDarwin side...

  • Logged In: YES

    Thanks for pointing out the libXt connection. As it turns
    out, this is another problem with libXt using a two-level
    namespace. I am looking into the best solution for the
    future, but for now you can do one of the following:

    1. Set the environment variable DYLD_FORCE_FLAT_NAMESPACE
    before you launch xterm.

    2. Relink xterm and specify the option -force_flat_namespace.

    3. Replace libXt.6.0.dylib with the XFree86 4.1 version or
    rebuild it with -flat_namespace.

    • status: open --> open-fixed
1 2 > >> (Page 1 of 2)