Xmanager Forum

Solaris Workshop doesn't work with Xmanager

Last post: Tuesday, November 11, 2003 5:57 PM by Smith, 1 reply

 
Tuesday, November 11, 2003 8:36 AM - Maoli

Solaris Workshop doesn't work with Xmanager

 
On solaris, when starting workshop on Solaris and display on windows, got the following warning:

Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':osfActivate:ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfBeginLine
Warning: ... found while parsing ':osfBeginLine:ManagerGadgetTraverseHome()'
.
.
.

After workshop starts succesfully, you won't be able to key in any thing. The workshop just does
not response to any key stroke.

This hapeens to 'ddd' and 'dtterm' as well. It seems to happen when motif library is used.

Has anyone encounter this problem before ?

Maoli
Tuesday, November 11, 2003 5:57 PM - Smith

Re: Solaris Workshop doesn't work with Xmanager

 
The following is an article written by Ken Lee. I've fixed the same problem by following his article.

~~~~~~~~~~~~~~
There is an OSF supplied addition to the /usr/lib/X11/XKeysymDB file.
It is found on the release tape and should have been automatically installed
if the installation procedure was followed in the Release Notes.

You have to copy (or append) lib/Xm/XKeysymDB into /usr/lib/X11. This may
require root permission. It is not clear how to fix the problem if you can't
do this. The error comes from Xt translation table parsing and can't be fixed
in Motif, so if you can't get root permission you may be stuck. The file is
not copyrighted so you can install it on other systems.

If X has been built so that XKeysymDB is not in this directory, and you don't
know where it is looking, run 'strings libX11.a | grep XKeysymDB' to find the
path.

On a Sun running openwin with shared libraries, you may need to put the path
for the library containing XKeysymDB *first* in the path list in
LD_LIBRARY_PATH, or it may find the wrong XKeysymDB in the wrong directory.

XKeysymDB simply contains the registered keysym values for the OSF keysyms.
The OSF values are server-independent. And, all registered keysyms will be
included in an XKeysymDB file to be shipped with X11R5.

In the meantime (till all systems are X11R5+), a list of the registered
keysyms can be found in the X11R4 release in mit/doc/Registry/Xregistry.

Also note the XKEYSYMDB environment variable. Setting this to point to the
XKeysymDB file often helps, but not always...

Some people have also reported getting this error if their Motif libraries
were built with libc headers that are not compatible with those installed on
their system. For example, Linux has two incompatible libraries libc5 and
glibc. You may get keysym (and other) errors if your Motif was built with
libc5 but you run your Motif application with glibc. Contact your Motif
vendor for information on the required libc.