This is the mail archive of the
mailing list for the Cygwin project.
Re: snapshot 20091002 and xterm crash
2009/10/2 Corinna Vinschen:
> [Ping Yaakov]
> On Oct Â2 09:04, Marco Atzeri wrote:
>> xterm abort when run in snapshot 20091002
>> reverting to 20090924 solve the issue.
>> Run as:
>> DISPLAY=127.0.0.1:0.0 xterm Â-ls /usr/bin/bash.exe
> I can reproduce that. ÂI found the problem and it's really puzzeling.
> In the snapshot 2009-10-02, the default charset for the "C" locale is
> set to UTF-8 for the application. ÂIn 2009-09-24, it was only using
> UTF-8 for filenames and other system objects by default.
> When starting xterm with no locale environment variable set, it fails
> to start. ÂIf you're quick enough, you can read a message along the
> lines of "Cannot allocate pty: No such file ..."
That could be a luit problem:
> However, starting xterm works if you set, for instance, the environment
> variable $LANG to "C.UTF-8". ÂThis works:
> ÂDISPLAY=127.0.0.1:0.0 LANG=C.UTF-8 xterm
> However, even though newlib handles "UTF8" same as "UTF-8", it's
> apparently not the same for xterm.
Random guess: xterm recognises "UTF-8" in $LANG and concludes that no
translation is needed. It doesn't recognise "UTF8" (without the
hyphen), nor does it know that plain "C" now implies "UTF-8", hence it
invokes "luit" to do the translation, which fails for the reason
No idea why the luit problem didn't show up more prominently before though ...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple