Re: fatal IO error 104 on start

[Harold L Hunt II <huntharo at msu dot edu>]

Follow these steps:

1) Open Cygwin bash shell.

2) In bash shell, run the following two commands:

umount /usr/X11R6/lib/X11/fonts
umount -u /usr/X11R6/lib/X11/fonts

3) Rerun Cygwin's setup.exe, select 'Reinstall' for any of the following 
packages that were already installed:

XFree86-f100
XFree86-fcyr
XFree86-fenc
XFree86-fnts
XFree86-fscl

4) Launch Cygwin/X again and test that the font problems have gone away.

5) Report your results here along with any deviations you had to make 
from these instructions.

Harold

Greg Jewell wrote:

> Thanks for the tip.  Looking at the log file, it appears that this is the pertinent error message:
>
> Fatal server error:
> could not open default font 'fixed'
> winDeinitClipboard - Noting shutdown in progress
> winDeinitMultiWindowWM - Noting shutdown in progress
>
> Any ideas?  I installed the default XFree86 packages.
>
>
> Greg
>
>
>
>
> > -----Original Message-----
> > From: Harold L Hunt II [mailto:huntharo@msu.edu]
> > Sent: Monday, January 05, 2004 13:58
> > To: cygwin-xfree@cygwin.com
> > Subject: Re: fatal IO error 104 on start
> >
> >
> > Greg,
> >
> > Look at /tmp/XWin.log.
> >
> > Harold
> >
> > Greg Jewell wrote:
> >
> >
> > > Hi All,
> > >
> > > I just installed cygwin on my work machine, but am unable to 
> >
> > start the X server.  Each time I try (using startx), I receive 
> > the following error:
> >
> > > XIO:  fatal IO error 104 (Connection reset by perr) on X 
> >
> > server ":0.0"
> >
> > >        after 0 requests (0 known processed) with 0 events remaining.
> > >
> > > I searched the archives and saw that others were having the 
> >
> > same problem at the end of November/beginning of December, but 
> > no solution was offered.
> >
> > > I downloaded the packages from a couple of different sources 
> >
> > this morning, but none of them produced different results.  
> > Other than the few times that I've installed the software this 
> > morning, cygwin had not been on this machine previously.  
> > (It's a new box.)
> >
> > > Does anybody know how to resolve this?
> > >
> > >
> > > Thanks,
> > > Greg Jewell