Alan Hourihane <alanh <at> fairlite.demon.co.uk> writes: > > On Wed, 2007-05-09 at 15:25 +0000, Scott Hussong wrote: > > After running rebaseall, I got startx to work on my new HP vista laptop. > > However, when I wake up from hibernate, any open xterms show "Not Responding". > > > > In my main cygwin window, where startx was executed, shows this: > > > > xterm: fatal IO error 104 (Connection reset by peer) or KillClient on X server > > ":0.0" > > xinit: connection to X server lost. > > > > > > I don't have this problem on my XPsp2 laptop. > > > > Anyone experience this and know a fix? > > Looks like the Xserver died for some reason. > > You should check your Xwin.log files. > > Alan. >
Alan, You raise an interesting point. This seems to happen when I go back and forth between my external display and laptop display: winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp:32 winWindowProc - WM_DISPLAYCHANGE - new width: 1280 new height: 1024 This is the message in my Xwin.log that appears after a successful startx and later hibernate if I switch displays. But still, this is a new problem - I didn't see this before with my older XP laptop. I'm wondering if this is a startx on Vista issue, or if it's hardware (display or hibernate) config related. Thanks, Scott -- 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/
