I can no longer reproduce the problem. Whatever it was, it seems to
have sorted itself out in that queasy "just try rebooting 50 times"
way that windows 'fixes' iteself.
Gah.
On 8/18/07, Jay Abel <[EMAIL PROTECTED]> wrote:
> Yikes. I turned off VirusScan on-access and buffer overflow checking,
Yikes. I turned off VirusScan on-access and buffer overflow checking,
then xterm ran. So happy it was running, I forgot what I was doing
and fixed some missing fields in my .xdefaults file (changed Xterm to
xterm) and opened another window. No problem. xclock now runs, no
problem. Re-enable bu
On 8/18/07, Larry Hall (Cygwin X) <[EMAIL PROTECTED]> wrote:
> Jay Abel wrote:
> > I'm having similar trouble, starting yesterday. xterm and xclock both
> > hang as described, but xeyes, xfig and rxvt all work.
>
> And have you installed any "dodgy app" recently?
>
> --
> Larry Hall
Jay Abel wrote:
I'm having similar trouble, starting yesterday. xterm and xclock both
hang as described, but xeyes, xfig and rxvt all work.
And have you installed any "dodgy app" recently?
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (5
Larry Hall (Cygwin X) wrote:
All of this is really strange. The only change/installation I made to
my system yesterday was to install a logitech webcam.
Remove it again. I think you'll find that solves the problems you were
seeing. Logitech drivers are known to cause problems. Cygwin is one
I'm having similar trouble, starting yesterday. xterm and xclock both
hang as described, but xeyes, xfig and rxvt all work.
On 8/17/07, Larry Hall (Cygwin X) <[EMAIL PROTECTED]> wrote:
> Olumide wrote:
> > Hi -
> >
> > Yesterday, I started my X server as usual and followed by an
> > X-application
Olumide wrote:
Hi -
Yesterday, I started my X server as usual and followed by an
X-application (gnuplot), which refused to start up. At the same time the
XWin process stopped working, in fact it had stopped page faulting. On
terminating the XWin process I got the following message
XIO: fat
Hi -
Yesterday, I started my X server as usual and followed by an
X-application (gnuplot), which refused to start up. At the same time the
XWin process stopped working, in fact it had stopped page faulting. On
terminating the XWin process I got the following message
XIO: fatal IO error 104
