Re: Problem with new xinit - console window doesn't open (but bash starts)

[Jon TURNEY <jon dot turney at dronecode dot org dot uk>]

On 20/11/2009 04:07, Jim Reisert AD1C wrote:
> More info:
>
> If I run startxwin.bat from a CMD.exe command line, the bash console
> xterm opens just fine. I only have problems starting it from the shortcut.

This is typical of the current issue we have where 'run xterm' blocks when 
xterm tries to output 'Warning: Missing charsets in String to FontSet conversion'

Any one of:
- installing the CJK fonts
- having 'tty' in the CYGWIN environment variable
- having the LANG environment set to a non-UTF-8 locale
should work around this problem

Note that the environment variable will have to be set via the system applet 
in the Windows control panel, as only that controls the environment for the 
startxwin.bat started from the start menu...

> I do see some interesting things in the log file, however:
>
> MIT-SHM extension disabled due to lack of kernel support
> XFree86-Bigfont extension local-client optimization disabled due to lack
> of shared memory support in the kernel

I hope these are explained by
http://x.cygwin.com/docs/ug/using-shared-memory.html

> [dix] Could not init font path element /usr/share/fonts/TTF/, removing
> from list!
> [dix] Could not init font path element /usr/share/fonts/OTF/, removing
> from list!
> [dix] Could not init font path element /usr/share/fonts/Type1/, removing
> from list!

These are expected when these font directories are empty, which is quite 
normal if you haven't installed all possible fonts

> Warning: Missing charsets in String to FontSet conversion

This is xterm warning that the fontset has no fonts for CJK locales (as no CJK 
fonts are installed)

--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/