Re: 1.5.23 on vista: difficulties launching X
On Wed, 10 Jan 2007, Larry Hall (Cygwin X) wrote: Dick Repasky wrote: 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. snip 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. Did you try rebasing? When I rebaseall to 0x6500, the child_copy error disappears. Both startxwin.sh and startx run fine. (I have yet to try -engine 2 to get the toolbar-X-icon-exit to work.) WHen I rebaseall back to 0x7000, the child_copy error does not return. I did not believe in the healing powers of vista until I saw that. What does return after rebasing back to 0x7000 is that startx sometimes hangs with CPU at 100% and cat.exe burning cycles. What will the longterm fix for the rebase issue be in the cygwin distro? Thanks, Dick -- 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/
Re: 1.5.23 on vista: difficulties launching X
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 Cygwin Configuration Diagnostics Current System Time: Wed Jan 10 16:18:17 2007 Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Windows\system32 c:\Windows c:\Windows\System32\Wbem SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'rrepasky' PWD = '/home/rrepasky' HOME = '/home/rrepasky' MAKE_MODE = 'unix' HOMEPATH = '\Users\rrepasky' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Users\rrepasky\AppData\Roaming' HOSTNAME = 'rrepasky-PC' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 2 Stepping 8, GenuineIntel' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' PROGRAMDATA = 'C:\ProgramData' USERDOMAIN = 'rrepasky-PC' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/cygdrive/c/Users/rrepasky/AppData/Local/Temp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'rrepasky' PROCESSOR_LEVEL = '15' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' USERPROFILE = 'C:\Users\rrepasky' PS1 = '\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\RREPASKY-PC' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\rrepasky\AppData\Local' !C: = 'C:\cygwin\bin' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/cygdrive/c/Users/rrepasky/AppData/Local/Temp' SYSTEMROOT = 'C:\Windows' PRINTER = 'hrothgar' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '0208' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '1' SESSIONNAME = 'Console' COMPUTERNAME = 'RREPASKY-PC' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus
Re: 1.5.23 on vista: difficulties launching X
Dick Repasky wrote: 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. snip 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. Did you try rebasing? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
1.5.23 on vista: difficulties launching X
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. startx sometimes succeeds and sometimes fails. It succeeds in 35 % of runs and fails in 65 % of runs. A contingency table indicates that success of successive runs are independent of one another: observed cell frequencies are very close to expected values. Again if startx is run immediately after a system reboot, it fails in a manner that is similar to that in which startxwin.sh fails. Subsequent runs sometimes work or not. If they work the X server exits normally when xterm that has been run in the foreground exits. When it fails, it too fails with the xterm child copy error, but that error is followed by a number of other messages as processes shut down. A combined output and error are attached as startx-outerr. Hope that helps, Dick Dick Repasky Center for Computational Cytomics UITS Cubicle 101.08 Indiana University USA [EMAIL PROTECTED] Cygwin Configuration Diagnostics Current System Time: Mon Jan 08 16:54:23 2007 Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Windows\system32 c:\Windows c:\Windows\System32\Wbem SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'rrepasky' PWD = '/home/rrepasky' HOME = '/home/rrepasky' MAKE_MODE = 'unix' HOMEPATH = '\Users\rrepasky' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Users\rrepasky\AppData\Roaming' HOSTNAME = 'rrepasky-PC' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 2 Stepping 8, GenuineIntel' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' PROGRAMDATA = 'C:\ProgramData' USERDOMAIN = 'rrepasky-PC' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/cygdrive/c/Users/rrepasky/AppData/Local/Temp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'rrepasky' PROCESSOR_LEVEL = '15' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' USERPROFILE = 'C:\Users\rrepasky' PS1 = '\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\RREPASKY-PC' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\rrepasky\AppData\Local' !C: = 'C:\cygwin\bin' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/cygdrive/c/Users/rrepasky/AppData/Local/Temp' SYSTEMROOT = 'C:\Windows' PRINTER = 'hrothgar' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '0208' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '1' SESSIONNAME = 'Console' COMPUTERNAME = 'RREPASKY-PC' _ = '/usr/bin/cygcheck' POSIXLY_CORRECT = '1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
Re: 1.5.23 on vista: difficulties launching X
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 -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
