Re: Problem with new xinit - console window doesn't open (but bash starts)
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 you try? Now my log file (attached) shows: It also claims another window manage is running (and therefore shuts down), which is untrue (there is no other Xwin process running). Since I have touched 'check for another window manager' code recently, I was kind of expecting to see that I'd managed to break it in some way, but.. I'm not quite sure what to make of that log file. This is very strange. If you look for (II) xorg.conf is not supported, you'll see that it looks like that server starts again about half-way through. I did wonder if you were managing to somehow start two copies of XWin near-simultaneously, but I don't think that would produce a logfile like that (since it's not opened in append mode, you probably get the logfile from the last process to close it or something like that) An alternative explanation is that there is a really inconveniently timed server regeneration happening: just after the internal client threads have been created, but before they can connect, so they are still hanging around to be accepted by the next server generation. If we did have twice as many threads as we are supposed to, that would explain the final failure due to another WM running (as there's another WM thread, note that there are two 'winMultiWindowXMsgProc - Hello' lines) No idea why the server is regenerating though, needs more meditation :-) After some meditation, I think that the server regeneration may be being caused by a race condition introduced by the use of checkX in the startxwin.bat script: If checkX connects to and then disconnects from the Xserver before the internal client threads get a chance to connect, the Xserver will restart when checkX disconnects, causing these duplicate threads. Fortunately, this should have a simple workaround of removing the checkX line from startxwin.bat (or replacing it with a delay if you care about getting an xterm started by it) The correct fix for this behaviour is not immediately obvious, and I don't really have time to work on it at the moment, so I don't have a patch for this. -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 Use %RUNTWO% /usr/bin/XWin.xml where XWin.xml is something like the following (untested): ?xml version=1.0 encoding=us-ascii? Run2Config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=run2.xsd SelfOptions / Global Environment !-- either of these, or both, and modified as desired -- Set var=LANG value=C.ASCII/ Append var=CYGWIN value= tty/ /Environment Target filename=/usr/bin/bash.exe startin=~ Arg-l/Arg Arg-c/Arg ArgXWin -multiwindow -clipboard -silent-dup-error/Arg /Target /Global /Run2Config -- Chuck -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 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 Use %RUNTWO% /usr/bin/XWin.xml where XWin.xml is something like the following (untested): ?xml version=1.0 encoding=us-ascii? Run2Config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=run2.xsd SelfOptions / Global Environment !-- either of these, or both, and modified as desired -- Set var=LANG value=C.ASCII/ Append var=CYGWIN value= tty/ /Environment Target filename=/usr/bin/bash.exe startin=~ Arg-l/Arg Arg-c/Arg ArgXWin -multiwindow -clipboard -silent-dup-error/Arg /Target /Global /Run2Config You can also just use the DOS set command right in startxwin.bat. In the case of CYGWIN, the syntax would be SET CYGWIN=%CYGWIN% tty Ken -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 '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 ...or perhaps setting xterm's menuLocale resource to C 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) iirc, that's from the Xaw initialization, which asks X11 (library), and _that_ falls into a hole where someone decided to load a fontset. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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) shows: It also claims another window manage is running (and therefore shuts down), which is untrue (there is no other Xwin process running). Since I have touched 'check for another window manager' code recently, I was kind of expecting to see that I'd managed to break it in some way, but.. I'm not quite sure what to make of that log file. This is very strange. If you look for (II) xorg.conf is not supported, you'll see that it looks like that server starts again about half-way through. I did wonder if you were managing to somehow start two copies of XWin near-simultaneously, but I don't think that would produce a logfile like that (since it's not opened in append mode, you probably get the logfile from the last process to close it or something like that) An alternative explanation is that there is a really inconveniently timed server regeneration happening: just after the internal client threads have been created, but before they can connect, so they are still hanging around to be accepted by the next server generation. If we did have twice as many threads as we are supposed to, that would explain the final failure due to another WM running (as there's another WM thread, note that there are two 'winMultiWindowXMsgProc - Hello' lines) No idea why the server is regenerating though, needs more meditation :-) -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 charsets in String to FontSet conversion Try installing the font-isas-misc, font-jis-misc, and font-daewoo-misc packages. See http://cygwin.com/ml/cygwin-xfree/2009-11/msg00111.html http://cygwin.com/ml/cygwin-xfree/2009-11/msg00117.html Ken -- 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/
Re: Problem with new xinit - console window doesn't open (but bash starts)
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, however: [...] Warning: Missing charsets in String to FontSet conversion Try installing the font-isas-misc, font-jis-misc, and font-daewoo-misc packages. See http://cygwin.com/ml/cygwin-xfree/2009-11/msg00111.html http://cygwin.com/ml/cygwin-xfree/2009-11/msg00117.html I tried adding the missing fonts. I tried SET LANG=C Starting the X server is still unpredictable. Now my log file (attached) shows: 2009-11-20 08:01:58 winClipboardProc - Could not open display, try: 1, sleeping: 4 2009-11-20 08:01:58 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-11-20 08:01:58 winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5 It also claims another window manage is running (and therefore shuts down), which is untrue (there is no other Xwin process running). - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1680 h 1050 winInitializeDefaultScreens - Returning 2009-11-20 08:01:57 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-11-20 08:01:57 (II) xorg.conf is not supported 2009-11-20 08:01:57 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-11-20 08:01:57 winPrefsLoadPreferences: /cygdrive/d/Home/.XWinrc 2009-11-20 08:01:57 LoadPreferences: Done parsing the configuration file... 2009-11-20 08:01:57 winGetDisplay: DISPLAY=:0.0 2009-11-20 08:01:57 winDetectSupportedEngines - Windows NT/2000/XP 2009-11-20 08:01:57 winDetectSupportedEngines - DirectDraw installed 2009-11-20 08:01:57 winDetectSupportedEngines - DirectDraw4 installed 2009-11-20 08:01:57 winDetectSupportedEngines - Returning, supported engines 0007 2009-11-20 08:01:57 winSetEngine - Multi Window or Rootless = ShadowGDI 2009-11-20 08:01:57 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-11-20 08:01:57 winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 2009-11-20 08:01:57 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2009-11-20 08:01:57 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2009-11-20 08:01:57 null screen fn ReparentWindow 2009-11-20 08:01:57 null screen fn RestackWindow 2009-11-20 08:01:57 InitQueue - Calling pthread_mutex_init 2009-11-20 08:01:57 InitQueue - pthread_mutex_init returned 2009-11-20 08:01:57 InitQueue - Calling pthread_cond_init 2009-11-20 08:01:57 InitQueue - pthread_cond_init returned 2009-11-20 08:01:57 winInitMultiWindowWM - Hello 2009-11-20 08:01:57 winMultiWindowXMsgProc - Hello 2009-11-20 08:01:57 Screen 0 added at XINERAMA coordinate (0,0). 2009-11-20 08:01:57 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-11-20 08:01:57 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-11-20 08:01:57 MIT-SHM extension disabled due to lack of kernel support 2009-11-20 08:01:57 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-11-20 08:01:57 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-11-20 08:01:57 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-11-20 08:01:57 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! 2009-11-20 08:01:57 [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! 2009-11-20 08:01:57 [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! 2009-11-20 08:01:57 winPointerWarpCursor - Discarding first warp: 840 525 2009-11-20 08:01:57 (--) 16 mouse buttons found 2009-11-20 08:01:57 (--) Setting autorepeat to delay=500, rate=31 2009-11-20 08:01:57 (--) winConfigKeyboard - Layout: 0409 (0409) 2009-11-20 08:01:57 (--) Using preset keyboard for English (USA) (409), type 4 2009-11-20 08:01:57 Rules = base Model = pc105 Layout = us Variant = none Options = none 2009-11-20 08:01:58 winInitMultiWindowWM - pthread_mutex_lock () returned. 2009-11-20 08:01:58 winProcEstablishConnection - Hello 2009-11-20 08:01:58 winInitClipboard () 2009-11-20 08:01:58 winProcEstablishConnection - winInitClipboard returned. 2009-11-20 08:01:58 winClipboardProc - Hello 2009-11-20 08:01:58 DetectUnicodeSupport - Windows NT/2000/XP 2009-11-20 08:01:58 winInitMultiWindowWM - pthread_mutex_unlock () returned. 2009-11-20 08:01:58
Re: Problem with new xinit - console window doesn't open (but bash starts)
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. I do see some interesting things in the log file, however: [...] Warning: Missing charsets in String to FontSet conversion Try installing the font-isas-misc, font-jis-misc, and font-daewoo-misc packages. See http://cygwin.com/ml/cygwin-xfree/2009-11/msg00111.html http://cygwin.com/ml/cygwin-xfree/2009-11/msg00117.html Ken -- 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/ -- View this message in context: http://old.nabble.com/Problem-with-new-xinit---console-window-doesn%27t-open-%28but-bash-starts%29-tp26438078p26443605.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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/
RE: Problem with new xinit - console window doesn't open (but bash starts)
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 other locales due to its ability to represent so many scripts. Also, the server won't fail for lack of those fonts, rather it will exhibit occasional unnecessary lags. That said, I favor setting the packages as dependencies, as they're ever more likely to see a bit of use. $.02 (and not a red cent more), Mike
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 extension local-client optimization disabled due to lack of shared memory support in the kernel II) GLX: Initialized DRISWRAST GL provider for screen 0 [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! Warning: Missing charsets in String to FontSet conversion None of the compatibility settings are checked in the Windows shortcut. I've attached the Xwin.0.log file - Jim On 11/19/2009 8:57 PM, Jim Reisert AD1C wrote: 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 proceeding %RUN% checkX -wait -d %DISPLAY% -t 12 REM Startup an xterm, using bash as the shell. %RUN% xterm -e /usr/bin/bash -l Anyone else notice this? The problem is the same on my laptop at work running WinXP, as well as my home system running Windows 7 - Jim # cygcheck -c | egrep cyg|x cygrunsrv 1.34-1 OK cygutils 1.4.0-1 OK cygwin 1.7.0-65 OK cygwin-doc 1.5-1 OK expat 2.0.1-1 OK gettext 0.17-11 OK libexpat1 2.0.1-1 OK libexpat1-devel 2.0.1-1 OK libpixman1_0 0.16.2-1 OK libxcb1 1.4-2 OK libXext6 1.1.1-1 OK libxkbfile1 1.0.6-1 OK libxml2 2.7.4-1 OK lynx 2.8.5-4 OK texinfo 4.13-3 OK util-linux 2.14.1-1 OK xauth 1.0.4-1 OK xcursor-themes 1.0.2-1 OK xemacs-emacs-common 21.4.22-1 OK xinit 1.2.0-1 OK xkbcomp 1.1.1-1 OK xkeyboard-config 1.7-1 OK xmodmap 1.0.4-1 OK xorg-server 1.7.1-3 OK xrdb 1.0.6-1 OK xterm 250-1 OK -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1680 h 1050 winInitializeDefaultScreens - Returning 2009-11-19 21:06:08 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-11-19 21:06:08 (II) xorg.conf is not supported 2009-11-19 21:06:08 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-11-19 21:06:08 winPrefsLoadPreferences: /cygdrive/d/Home/.XWinrc 2009-11-19 21:06:08 LoadPreferences: Done parsing the configuration file... 2009-11-19 21:06:08 winGetDisplay: DISPLAY=:0.0 2009-11-19 21:06:08 winDetectSupportedEngines - Windows NT/2000/XP 2009-11-19 21:06:08 winDetectSupportedEngines - DirectDraw installed 2009-11-19 21:06:08 winDetectSupportedEngines - DirectDraw4 installed 2009-11-19 21:06:08 winDetectSupportedEngines - Returning, supported engines 0007 2009-11-19 21:06:08 winSetEngine - Multi Window or Rootless = ShadowGDI 2009-11-19 21:06:08 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-11-19 21:06:08 winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 2009-11-19 21:06:08 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2009-11-19 21:06:08 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2009-11-19 21:06:08 null screen fn ReparentWindow 2009-11-19 21:06:08 null screen fn RestackWindow 2009-11-19 21:06:08 InitQueue - Calling pthread_mutex_init 2009-11-19 21:06:08 InitQueue - pthread_mutex_init returned 2009-11-19 21:06:08 InitQueue - Calling pthread_cond_init 2009-11-19 21:06:08 InitQueue - pthread_cond_init returned 2009-11-19 21:06:08 winInitMultiWindowWM - Hello 2009-11-19 21:06:08 Screen 0 added at XINERAMA coordinate (0,0). 2009-11-19 21:06:08 winMultiWindowXMsgProc - Hello 2009-11-19 21:06:08 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-11-19 21:06:08 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-11-19 21:06:08 MIT-SHM extension disabled due to lack of kernel support 2009-11-19 21:06:08 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-11-19 21:06:08 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-11-19 21:06:08 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-11-19 21:06:08 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! 2009-11-19 21:06:08 [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! 2009-11-19 21:06:08 [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! 2009-11-19
Re: Problem with new xinit - console window doesn't open (but bash starts)
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 workaround.) -- Eliot Moss -- 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/
