Re: 1.5.23 on vista: difficulties launching X

[Dick Repasky <rrepasky at lack dot ucs dot indiana dot edu>]

On Tue, 9 Jan 2007, Larry Hall (Cygwin X) wrote:

> Dick Repasky wrote:
> >  I'm experiencing difficulty starting X on a fresh install of cygwin on a
> >  fresh install of Windows Vista.  I've tried both startxwin.sh and startx.
> >  startxwin.sh always fails, and startx sometimes succeeds. A copy of
> >  cygcheck
> >  output is attached.
> >
> >  startxwin.sh fails in three ways.
> >
> >    1) Immediately after the system has been booted, a popup appears to
> >  notify
> >       me that sh.exe has exited, and X seems to be stalled.  An X appears
> >       in the toolbar, and both xterm and XWin are in the cygwin process
> >  table
> >       (ps -aux).  No xterm appears. A copy of the combined standard output
> >       and standard input are provided in startxwin.sh-outerr-postreboot.
> >
> >       The xterm in the process table can be killed with kill -TERM.
> >
> >       Attempts to launch an xterm fail. (I open a new cygwin window, set
> >       and export DISPLAY, and run xterm).
> >
> >       XWin cannot be killed with kill -TERM.  It can be killed with kill
> >       -9.
> >
> >       All of the above is repeatable if the system is rebooted.
> >
> >       I have seen the previous post of sh.exe exit that turned out not to
> >       be repeatable. Maybe the above will provide some insight on getting
> >       it
> >       to repeat.
> >
> >       Without rebooting, what happens on subsequent runs of startxwin.sh
> >       depends on how I clean up from the first failed run.
> >
> >   2)  If I clean up from a first failed run by killing the xterm and
> >       Xwin, subsequent runs of startxwin fail with a popup stating that
> >       Cygwin X has failed.
> >
> >       The cause seems to be a lingering sh.exe process in the table.
> >
> >   3) If I clean up from a first failed run by dismissing the cygwin
> >   terminal
> >      window by clicking on the window-close button, the sh.exe process goes
> >      away, and startxwin.sh fails with a message like "xterm 3228
> >  child_copy:
> >      linked dll data write copy failed, ...".  Full output is attached as
> >      startxwin.sh-outerr.
> >
> >      Unlike the previous poster who reported a similar error, there is no
> >      logitech camera or virus program running on the system. It is indeed a
> >      fresh install.
>
> Have you tried the suggestions mentioned in this thread?
>
> <http://sourceware.org/ml/cygwin/2006-11/msg00059.html>


Yes. Using the latest snapshot changes things, but doesn't clearly improve 
them.

For both startxwin.sh and startx, the snapshot eliminates the popup that 
states that sh.exe has exited.

Startxwin.sh still fails every time with the "child_copy: linked dll data
write copy failed" error that I originally reported.

startx fails more than it works. It worked in only 2 of ten runs.  For 7 
of the 8 failures, it ended with the usual child copy error. The odd 
failure was one in which it hung with processor use at 100%, and windows 
reported cat.exe as the process that was burning up the cycles.

OUtput of cygcheck is attached.

Hope that helps,

Dick

Attachment: cygcheck.info-snapshot
Description: Text document

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