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

Charles Wilson
Wed Nov 25 14:57:00 GMT 2009

Jon TURNEY wrote:
> 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...

There's another option. In startxwin.bat, you could use run2.exe instead
of run.  Instead of:

%RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error"


%RUNTWO% /usr/bin/XWin.xml

where XWin.xml is something like the following (untested):

<?xml version="1.0" encoding="us-ascii"?>
  <SelfOptions />
      <!-- either of these, or both, and modified as desired -->
      <Set var="LANG"  value="C.ASCII"/>
      <Append var="CYGWIN"  value=" tty"/>
    <Target filename="/usr/bin/bash.exe" startin="~">
      <Arg>"XWin -multiwindow -clipboard -silent-dup-error"</Arg>


Unsubscribe info:
Problem reports:

More information about the Cygwin-xfree mailing list