On 22/11/2009 20:24, Jon TURNEY wrote:
On 20/11/2009 15:05, Jim Reisert AD1C wrote:
I tried adding the missing fonts. I tried SET LANG=C
Starting the X server is still unpredictable.
Does this mean it sometimes works and sometimes doesn't?
Or does it mean it fails in different ways each time
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
On 11/25/2009 9:57 AM, Charles Wilson wrote:
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
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
On Sun, 22 Nov 2009, Jon TURNEY wrote:
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
On 20/11/2009 15:05, Jim Reisert AD1C wrote:
I tried adding the missing fonts. I tried SET LANG=C
Starting the X server is still unpredictable.
Does this mean it sometimes works and sometimes doesn't?
Or does it mean it fails in different ways each time you try?
Now my log file (attached)
On 11/19/2009 11:07 PM, 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.
I do see some interesting things in the log file, however:
[...]
Warning: Missing
On 11/20/2009 5:48 AM, Ken Brown wrote:
On 11/19/2009 11:07 PM, 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.
I do see some interesting things in the log file,
Shouldn't these packages be set as dependents for xorg-server?
Ken Brown-6 wrote:
On 11/19/2009 11:07 PM, 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.
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-
ow...@cygwin.com] On Behalf Of laxamar
Sent: Friday, November 20, 2009 9:38 AM
Shouldn't these packages be set as dependents for xorg-server?
They're not strict dependencies - a UTF-8 based locale has more
requirements than
I'm running the latest of everything Cygwin 1.7 (see below).
When I start the Xwin server from the Windows shortcut:
D:\Cygwin\bin\run.exe /usr/bin/startxwin.bat
I see a bash.exe process running, but no X window comes up, as per:
REM Make sure XWin is ready to accept connections before
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.
I do see some interesting things in the log file, however:
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont
The missing charsets message is symptomatic of not
having the patches needed to a couple of X config
files concerning UTF-8. If you apply the path, which
I think is in the latest Xorg files, then that
problem should be fixed. (Assuming you set LANG.
You can also try LANG=C as a temporary
13 matches
Mail list logo
