On Wed, 2004-01-14 at 09:10, David Johnston wrote:

> Guys,
> could you run "set | grep -i utf" and tell me if you're running with
> LANG, LOCALE, et cetera, set to en_US.UTF-8?  If so, can you try running
> OOo with LANG=en_US and let us know if it fixes it?
> 
> -David

David-

I changed my LANG, LOCALE, etc to various settings using export, but
that didn't fix it.  However, the combination of your idea and a post on
ooforums started me looking toward fonts, and it turns out that
something is amiss with the /usr/X11R6/lib/X11/xkb directory in
XFree86.  The ooforums post talked about the "compiled" directory in
this folder causing problems because it is not writeable, but it appears
that the xkb folder is almost completely empty in a stock XFree install.

So basically, I copied the xkb folder from my LTSP3 tree into the LTSP4
tree, restarted my X session (ctrl-alt-backspace) and StarOffice7 and
OOo 1.1 menus work flawlessly.  

Thanks for the hint!  Here are the steps to replicate (as root on the
server), assuming you have v3 installed in /opt/ltsp3:

cd /opt/ltsp4/i386/usr/X11R6/lib/X11
mv xkb xkb.old
cp -R /opt/ltsp3/i386/usr/X11R6/lib/X11/xkb xkb

Restart and give it a shot.  I haven't fully figured out what the
problem is with this dir.  My XFree86 is a custom 4.3.0 build straight
off of xfree86.org, and it was in the same condition as the 4.2.99
shipped with LTSP4: an empty xkb directory with only a symlink inside it
to /usr/X11R6/bin/xkbcomp.

-Todd



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to