Re: Problems with Startx even after rebaseall

[Thorsten Kampe <thorsten at thorstenkampe dot de>]

* Robert Neville (Tue, 01 May 2007 14:09:59 -0700)
> On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe <thorsten@thorstenkampe.de> wrote:
> >* Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
> >> On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe <thorsten@thorstenkampe.de> wrote:
> >> >* Robert Neville (Mon, 30 Apr 2007 10:18:15 -0700)
> >> >> I am not sure if this is the appropriate group. In addition, searching through
> >> >> these gmane newsgroups is not straightforward since Google groups does not return them.
> >> >> 
> >> >> Startx fails to initialize when it worked yesterday. I ran setup and the process may have not
> >> >> completed (it was late and I needed to sleep). After running setup.exe again, I navigated to the
> >> >> System category and reinstalled rebase. Then I reviewed the README file; kill all processes
> >> >> associated with cygwin; ran ash; and typed /bin/rebaseall -v; the utility performed some actions and
> >> >> returned without errors.
> >> >> 
> >> >> I fired up a cygwin window and startx would still not initialize. The console gave me the following
> >> >> font error.
> >> >> 
> >> >> sageQueue trapped WM_QUIT message, exiting main loop.
> >> >> winClipboardProc - XDestroyWindow succeeded.
> >> >> FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing.
> >> >> 
> >> >> The cygwin console appears fully functional. The console has returned some errors when running make,
> >> >> but these issues may be completely separate. Please give me whatever insight you may have on these
> >> >> scenarios. I have already spent considerable time troubleshooting these issues and need better
> >> >> guidance.
> >
> >"XWin was started with the following command line:
> >X :0 -multiwindow -clipboard""
> >
> >Read again my posting. I said "without" and not "with" (which wouldn't 
> >make sense at all if there is a "winClipboardIOError"). "startx" is a 
> >shell script. Copy it, find the line where XWin is started and remove 
> >the arguments (parameters). Then start this script. 
> >
> 
> I did not realize that startx was just a script. Honestly, the clipboard is the main reason for me
> launching Xwin. After editing the script and removing the clipboard argument, the console returns a
> "winInitMultiWindowXMsgProc - Caught IO Error." Then I removed the multiwindow argument and the
> console returned the following error. I don't have much time to evaluate this scenario or the
> patience; hopefully someone has seen this scenario before. 
> [XWin log]

I can't see any error in the new log you posted. The only thing I can 
advise you is to try to run the startxwin.sh and startxwin.bat file to 
see if they make a difference...

Thorsten


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