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