Re: Problems with Startx even after rebaseall

2007-05-05 Thread Robert Neville
On Thu, 3 May 2007 00:22:50 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:

* Robert Neville (Wed, 02 May 2007 12:19:45 -0700)
 On Wed, 2 May 2007 09:57:08 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:
 * Robert Neville (Tue, 01 May 2007 14:09:59 -0700)
  On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe [EMAIL PROTECTED] 
  wrote:
  * Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
   On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 
   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
 
 
 Sorry about not posting the error log. I was helping several other people 
 with their basic computer
 issues and made this oversight. Both startxwin.bat and startxwin.sh fail. 
 Here are the error logs.
 
 $ startx
 
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 6.8.99.901-4
 
 Contact: cygwin-xfree@cygwin.com
 
 XWin was started with the following command line:
 
 X :0
 
 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
 (II) XF86Config is not supported
 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
 winDetectSupportedEngines - Windows NT/2000/XP
 winDetectSupportedEngines - DirectDraw installed
 winDetectSupportedEngines - DirectDraw4 installed
 winDetectSupportedEngines - Returning, supported engines 0007
 winSetEngine - Using Shadow DirectDraw NonLocking
 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per 
 pixel
 winFinishScreenInitFB - Masks: 00ff ff00 00ff
 MIT-SHM extension disabled due to lack of kernel support
 XFree86-Bigfont extension local-client optimization disabled due to lack of 
 shar
 ed memory support in the kernel
 (--) Setting autorepeat to delay=500, rate=31
 (--) winConfigKeyboard - Layout: 0409 (0409)
 (--) Using preset keyboard for English (USA) (409), type 4
 Rules = xorg Model = pc105 Layout = us Variant = (null) Options = 
 (null
 )
 (--) 5 mouse buttons found
 Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing 
 from li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing 
 from
 list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
 from li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing 
 from
  list!
 winPointerWarpCursor - Discarding first warp: 509 353
 winProcEstablishConnection - Hello
 winProcEstablishConnection - Clipboard is not enabled, returning.
 cat: /home/Ferdie/.Xauthority: No such file or directory
 
 waiting for X server to shut down FreeFontPath: 

Re: Problems with Startx even after rebaseall

2007-05-05 Thread Thorsten Kampe
* Robert Neville (Sat, 05 May 2007 00:10:50 -0700)
 On Thu, 3 May 2007 00:22:50 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:
  _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
  _XSERVTransMakeAllCOTSServerListeners: server already running
  
  Fatal server error:
  Cannot establish any listening sockets - Make sure an X server isn't 
  already run
  ning
  winDeinitMultiWindowWM - Noting shutdown in progress
 
 It seems like there is something already listening or blocking the X 
 server...
 
 
 Do you have any suggestions on a solution?

Actually almost none (I just recently started using Xwinw and I'm 
still amazed who easy the setup is and that seemingly everything 
simply works).

 I have no idea why this would occur or how to troubleshoot these scenarios.
 
 The console keeps returning the font error. 
 
 Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from 
 li
 st!
 winPointerWarpCursor - Discarding first warp: 509 353
 winProcEstablishConnection - Hello
 winProcEstablishConnection - Clipboard is not enabled, returning.
 cat: /home/neville/.Xauthority: No such file or directory
 
 waiting for X server to shut down FreeFontPath: FPE 
 /usr/X11R6/lib/X11/fonts/mi
 sc/ refcount is 2, should be 1; fixing.
 winDeinitMultiWindowWM - Noting shutdown in progress

You seem to get different errors when starting startx or startxwin.sh 
and startxwin.bat. This log shows no reason for shutting down the X 
server - the other said there was already one running.
 
 This link gave me some insight, yet it did not resolve my main problem.
 
  http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof
 
 Apparently, mount does not list any mount points for /usr/X11R6/lib/X11/fonts 
 on my installation. 

Well, neither on mine and there are no mount statements in the 
postinstall scripts. I think some years ago there was a mounted font 
path but I might be mistaken.

Anyway, check if all the postinstall sripts have been run, and 
consider reinstalling X or Cygwin or Windows...

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/



Re: Problems with Startx even after rebaseall

2007-05-02 Thread Thorsten Kampe
* Robert Neville (Tue, 01 May 2007 14:09:59 -0700)
 On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:
 * Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
  On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 
  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/



Re: Problems with Startx even after rebaseall

2007-05-02 Thread Robert Neville
On Wed, 2 May 2007 09:57:08 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:

* Robert Neville (Tue, 01 May 2007 14:09:59 -0700)
 On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:
 * Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
  On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 
  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


Sorry about not posting the error log. I was helping several other people with 
their basic computer
issues and made this oversight. Both startxwin.bat and startxwin.sh fail. Here 
are the error logs.

$ startx

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.99.901-4

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

X :0

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0007
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winFinishScreenInitFB - Masks: 00ff ff00 00ff
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: 0409 (0409)
(--) Using preset keyboard for English (USA) (409), type 4
Rules = xorg Model = pc105 Layout = us Variant = (null) Options = (null
)
(--) 5 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from
 list!
winPointerWarpCursor - Discarding first warp: 509 353
winProcEstablishConnection - Hello
winProcEstablishConnection - Clipboard is not enabled, returning.
cat: /home/Ferdie/.Xauthority: No such file or directory

waiting for X server to shut down FreeFontPath: FPE /usr/X11R6/lib/X11/fonts/mi
sc/ refcount is 2, should be 1; fixing.
winDeinitMultiWindowWM - Noting shutdown in progress

#--#

$ startxwin.bat
startxwin.bat - Starting on Windows 

Re: Problems with Startx even after rebaseall

2007-05-02 Thread Thorsten Kampe
* Robert Neville (Wed, 02 May 2007 12:19:45 -0700)
 On Wed, 2 May 2007 09:57:08 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:
 * Robert Neville (Tue, 01 May 2007 14:09:59 -0700)
  On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe [EMAIL PROTECTED] 
  wrote:
  * Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
   On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 
   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
 
 
 Sorry about not posting the error log. I was helping several other people 
 with their basic computer
 issues and made this oversight. Both startxwin.bat and startxwin.sh fail. 
 Here are the error logs.
 
 $ startx
 
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 6.8.99.901-4
 
 Contact: cygwin-xfree@cygwin.com
 
 XWin was started with the following command line:
 
 X :0
 
 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
 (II) XF86Config is not supported
 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
 winDetectSupportedEngines - Windows NT/2000/XP
 winDetectSupportedEngines - DirectDraw installed
 winDetectSupportedEngines - DirectDraw4 installed
 winDetectSupportedEngines - Returning, supported engines 0007
 winSetEngine - Using Shadow DirectDraw NonLocking
 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per 
 pixel
 winFinishScreenInitFB - Masks: 00ff ff00 00ff
 MIT-SHM extension disabled due to lack of kernel support
 XFree86-Bigfont extension local-client optimization disabled due to lack of 
 shar
 ed memory support in the kernel
 (--) Setting autorepeat to delay=500, rate=31
 (--) winConfigKeyboard - Layout: 0409 (0409)
 (--) Using preset keyboard for English (USA) (409), type 4
 Rules = xorg Model = pc105 Layout = us Variant = (null) Options = 
 (null
 )
 (--) 5 mouse buttons found
 Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from 
 li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing 
 from
 list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from 
 li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing 
 from
  list!
 winPointerWarpCursor - Discarding first warp: 509 353
 winProcEstablishConnection - Hello
 winProcEstablishConnection - Clipboard is not enabled, returning.
 cat: /home/Ferdie/.Xauthority: No such file or directory
 
 waiting for X server to shut down FreeFontPath: FPE 
 /usr/X11R6/lib/X11/fonts/mi
 sc/ refcount is 2, should be 1; fixing.
 

Re: Problems with Startx even after rebaseall

2007-05-01 Thread Thorsten Kampe
* Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
 On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 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.
  
  After rebooting the computer and typing startx, cygwin gave me the 
  following error message. 
  [...]
  winProcEstablishConnection - winInitClipboard returned.
  winClipboardProc - Hello
  winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened 
  the di
  splay.
  winInitMultiWindowWM - XOpenDisplay () returned and successfully opened 
  the disp
  lay.
  DetectUnicodeSupport - Windows NT/2000/XP
  winClipboardProc - DISPLAY=127.0.0.1:0.0
  winClipboardProc - XOpenDisplay () returned and successfully opened the 
  display.
  
  winProcSetSelectionOwner - Clipboard not yet started, aborting.
  winProcSetSelectionOwner - Clipboard not yet started, aborting.
  
  waiting for X server to shut down winClipboardProc - 
  winClipboardFlushWindowsMes
  sageQueue trapped WM_QUIT message, exiting main loop.
  winClipboardProc - XDestroyWindow succeeded.
  
  winClipboardIOErrorHandler!
 
 Well, if there is an winClipboardIOErrorHandler error (whatever that 
 is) you should try starting without -clipboard says my common 
 sense...
 
 I am not familiar with the startx options. The man page only has basic info 
 about startx. I tried
 startx -clipboard as suggested; and the console returned the following error.

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. 

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/



Re: Problems with Startx even after rebaseall

2007-05-01 Thread Robert Neville
On Tue, 1 May 2007 08:55:47 +0100, Thorsten Kampe [EMAIL PROTECTED] wrote:

* Robert Neville (Mon, 30 Apr 2007 15:45:46 -0700)
 On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 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. 

Thorsten

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. 

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.99.901-4

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

X :0

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0007
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel
winFinishScreenInitFB - Masks: 00ff ff00 00ff
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: 0409 (0409)
(--) Using preset keyboard for English (USA) (409), type 4
Rules = xorg Model = pc105 Layout = us Variant = (null) Options = (null
)
(--) 5 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li
st!
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from
 list!
winPointerWarpCursor - Discarding first warp: 509 353
winProcEstablishConnection - Hello
winProcEstablishConnection - Clipboard is not enabled, returning.
cat: /home/Ferdie/.Xauthority: No such file or directory

waiting for X server to shut down FreeFontPath: FPE 
/usr/X11R6/lib/X11/fonts/misc/ refcount is 2,
should be 1; fixing.
winDeinitMultiWindowWM - Noting shutdown in progress


--
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: Problems with Startx even after rebaseall

2007-04-30 Thread Thorsten Kampe
* 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.
 
 After rebooting the computer and typing startx, cygwin gave me the following 
 error message. 
 
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 6.8.99.901-4
 
 Contact: cygwin-xfree@cygwin.com
 
 XWin was started with the following command line:
 
 X :0 -multiwindow -clipboard
 
 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
 (II) XF86Config is not supported
 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
 winDetectSupportedEngines - Windows NT/2000/XP
 winDetectSupportedEngines - DirectDraw installed
 winDetectSupportedEngines - DirectDraw4 installed
 winDetectSupportedEngines - Returning, supported engines 0007
 winSetEngine - Multi Window or Rootless = ShadowGDI
 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
 winAllocateFBShadowGDI - Creating DIB with width: 2048 height: 768 depth: 32
 winFinishScreenInitFB - Masks: 00ff ff00 00ff
 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32
 null screen fn ReparentWindow
 null screen fn RestackWindow
 InitQueue - Calling pthread_mutex_init
 InitQueue - pthread_mutex_init returned
 InitQueue - Calling pthread_cond_init
 InitQueue - pthread_cond_init returned
 winInitMultiWindowWM - Hello
 winMultiWindowXMsgProc - Hello
 winInitMultiWindowWM - Calling pthread_mutex_lock ()
 winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
 MIT-SHM extension disabled due to lack of kernel support
 XFree86-Bigfont extension local-client optimization disabled due to lack of 
 shar
 ed memory support in the kernel
 (--) Setting autorepeat to delay=500, rate=31
 (--) winConfigKeyboard - Layout: 0409 (0409)
 (--) Using preset keyboard for English (USA) (409), type 4
 Rules = xorg Model = pc105 Layout = us Variant = (null) Options = 
 (null
 )
 (--) 5 mouse buttons found
 Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from 
 li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing 
 from
 list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from 
 li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing 
 from
  list!
 winPointerWarpCursor - Discarding first warp: 1024 384
 winInitMultiWindowWM - pthread_mutex_lock () returned.
 winProcEstablishConnection - Hello
 winInitMultiWindowWM - pthread_mutex_unlock () returned.
 cat: winMultiWindowXMsgProc - pthread_mutex_lock () returned.
 /home/Ferdie/.Xauthority: No such file or directorywinInitMultiWindowWM - 
 DISPLA
 Y=127.0.0.1:0.0
 
 winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
 winInitClipboard ()
 winProcEstablishConnection - winInitClipboard returned.
 winClipboardProc - Hello
 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the 
 di
 splay.
 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the 
 disp
 lay.
 DetectUnicodeSupport - Windows NT/2000/XP
 winClipboardProc - DISPLAY=127.0.0.1:0.0
 winClipboardProc - XOpenDisplay () returned and successfully opened the 
 display.
 
 winProcSetSelectionOwner - Clipboard not yet started, aborting.
 winProcSetSelectionOwner - Clipboard not yet started, aborting.
 
 waiting for X server to shut down winClipboardProc - 
 winClipboardFlushWindowsMes
 sageQueue trapped WM_QUIT message, exiting main loop.
 winClipboardProc - XDestroyWindow succeeded.
 
 winClipboardIOErrorHandler!

Well, if there is an winClipboardIOErrorHandler error (whatever that 
is) you should try starting without -clipboard says my common 

Re: Problems with Startx even after rebaseall

2007-04-30 Thread Robert Neville
On Mon, 30 Apr 2007 21:47:39 +0100, Thorsten Kampe [EMAIL PROTECTED] 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.
 
 After rebooting the computer and typing startx, cygwin gave me the following 
 error message. 
 
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 6.8.99.901-4
 
 Contact: cygwin-xfree@cygwin.com
 
 XWin was started with the following command line:
 
 X :0 -multiwindow -clipboard
 
 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
 (II) XF86Config is not supported
 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
 winDetectSupportedEngines - Windows NT/2000/XP
 winDetectSupportedEngines - DirectDraw installed
 winDetectSupportedEngines - DirectDraw4 installed
 winDetectSupportedEngines - Returning, supported engines 0007
 winSetEngine - Multi Window or Rootless = ShadowGDI
 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per 
 pixel
 winAllocateFBShadowGDI - Creating DIB with width: 2048 height: 768 depth: 32
 winFinishScreenInitFB - Masks: 00ff ff00 00ff
 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 
 32
 null screen fn ReparentWindow
 null screen fn RestackWindow
 InitQueue - Calling pthread_mutex_init
 InitQueue - pthread_mutex_init returned
 InitQueue - Calling pthread_cond_init
 InitQueue - pthread_cond_init returned
 winInitMultiWindowWM - Hello
 winMultiWindowXMsgProc - Hello
 winInitMultiWindowWM - Calling pthread_mutex_lock ()
 winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
 MIT-SHM extension disabled due to lack of kernel support
 XFree86-Bigfont extension local-client optimization disabled due to lack of 
 shar
 ed memory support in the kernel
 (--) Setting autorepeat to delay=500, rate=31
 (--) winConfigKeyboard - Layout: 0409 (0409)
 (--) Using preset keyboard for English (USA) (409), type 4
 Rules = xorg Model = pc105 Layout = us Variant = (null) Options = 
 (null
 )
 (--) 5 mouse buttons found
 Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing 
 from li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing 
 from
 list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
 from li
 st!
 Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing 
 from
  list!
 winPointerWarpCursor - Discarding first warp: 1024 384
 winInitMultiWindowWM - pthread_mutex_lock () returned.
 winProcEstablishConnection - Hello
 winInitMultiWindowWM - pthread_mutex_unlock () returned.
 cat: winMultiWindowXMsgProc - pthread_mutex_lock () returned.
 /home/Ferdie/.Xauthority: No such file or directorywinInitMultiWindowWM - 
 DISPLA
 Y=127.0.0.1:0.0
 
 winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
 winInitClipboard ()
 winProcEstablishConnection - winInitClipboard returned.
 winClipboardProc - Hello
 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened 
 the di
 splay.
 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the 
 disp
 lay.
 DetectUnicodeSupport - Windows NT/2000/XP
 winClipboardProc - DISPLAY=127.0.0.1:0.0
 winClipboardProc - XOpenDisplay () returned and successfully opened the 
 display.
 
 winProcSetSelectionOwner - Clipboard not yet started, aborting.
 winProcSetSelectionOwner - Clipboard not yet started, aborting.
 
 waiting for X server to shut down winClipboardProc - 
 winClipboardFlushWindowsMes
 sageQueue trapped WM_QUIT message, exiting main loop.
 winClipboardProc - XDestroyWindow succeeded.
 
 winClipboardIOErrorHandler!

Well, if there is an winClipboardIOErrorHandler