Your X Window system and TotalView are having trouble communicating key stroke information.

The X system attempts to handle the translation of keystroke information from a spectrum of input devices available from a myriad of vendors gracefully. Input keyboard events are converted into a numeric code which is sent to TotalView where they are subsequently decoded and interpreted within the present GUI context. For that to happen successfully, both X and TotalView have to agree on a common set of event / code mappings.

One of the methods that is used by X, and where TotalView acquires its keyboard mappings, is the translation table contained in the file XKeysymDB. TotalView looks for XKeysymDB in a traditional location within the file system, however some recent distro releases have XKeysymDB located in an entirely different location, which results in translation problems between X and TotalView. In this case, no keyboard events are captured by TotalView and the resulting symptom, no characters are displayed in the text widgets within the TotalView GUI.

The other noticeable symptom is a large number of console error messages, on the order of:

translation table syntax error: Unknown keysym name: osfActivate
... found while parsing ':<Key>osfActivate: PrimitiveParentActivate()'
String to TranslationTable conversion encountered errors
translation table syntax error: Unknown keysym name: osfHelp
... found while parsing ':<Key>osfHelp: Help()'

...but that's another FAQ.

The work around is to set the XKEYSYMDB environment variable to the location of the XKeysymDB file on your system. For example on my Suse 9 system, the path is /usr/X11R6/lib/X11/XKeysymDB, while on Debian Sarge, the path is /usr/share/X11/XKeysymDB.

Tom Archambault
Etnus Customer Services