XWin starts but hangs as soon as I start an X-application

[Jay Abel]

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 <jabel@flex.com> wrote:
> 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 buffer overflow and access scan, and guess what?
> they both still work.  Put back configuration file.  Still works.
> wtf?
>
> I'll try rebooting and see if the problem reappears.
>
> On 8/18/07, Jay Abel <jabel@flex.com> wrote:
> > On 8/18/07, Larry Hall (Cygwin X) <reply-to-list-only-lh-x@cygwin.com> 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                              http://www.rfk.com
> > > RFK Partners, Inc.                      (508) 893-9779 - RFK Office
> > > 216 Dalton Rd.                          (508) 429-6305 - FAX
> > > Holliston, MA 01746
> >
> > Not recently, but I'm checking now.  I do have an evil logitech mouse,
> > but I thought I forced it to use the stock ms drivers.  It's possible
> > that I already have the unwanted/conflicting software, but that it
> > wasn't a problem until I upgraded to the most recent cygwin1.dll.
> > I'll see if I can find the list of evil applications then check if I
> > have any of them installed, and also try using an older cygwin.dll to
> > see if the problem disappears.
> >
> > I noticed that in the case of xterm, its associated shell also starts
> > and the xterm process cannot be killed until the corresponding shell
> > has also been killed, not from taskmanager, cygwin, etc.  On the other
> > hand, even typing 'xterm -version' hangs before any output is
> > produced.  It's almost as if the output pipe isn't being created
> > properly, but ps doesn't show xterm in the I state.  What I'm trying
> > to say is that the problem seems to happen when output is produced.
> > Note that even if the $DISPLAY variable isn't set, xterm still hangs
> > (you'd expect it to spit out an error message and die).  So I'd wager
> > the problem is related to writing to stdout, not to X.
> >
> > I'll take another look to see if I have any of the non-recommended
> > applications, such as logitech stuff, that might be interfering.
> >
>

--
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/