Re: error in running startx

2005-09-10 Thread Johan Grönqvist
I get exactly the same error message when I try to start X while already 
having X running. My guess is therefore that you have already started x 
successfully, but you do not know it. Try starting xterm instead and see 
if it works.


You may have to set a DISPLAY variable for that to work. I think the 
script startxwin is closer to what you want, but I am not the expert.


/ johan


--
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: error in running startx

2005-09-10 Thread Reid Thompson

Johan Grönqvist wrote:


I get exactly the same error message when I try to start X while already
having X running. My guess is therefore that you have already started x
successfully, but you do not know it. Try starting xterm instead and see
if it works.

You may have to set a DISPLAY variable for that to work. I think the
script startxwin is closer to what you want, but I am not the expert.

/ johan


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

you are correct -- use either startxwin.bat, or (startxwin.sh if running 
cygwin).



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



Failed xorg/XWin launch

2005-09-10 Thread [EMAIL PROTECTED]
To whom it may concern,
 
All 4 methods outlined in the User's Guide of launching xorg/XWin produced 
similar errors.  Further, attempts to cut-and-paste the contents of the 
XWin.log or sending it as an attachement have generated MAILER-DAEMON errors 
from your email server.
 
All requisite xorg packages (in addition to optional ones) are installed.
 
Here's another try of sending the contents (stripped of HTML content) to the 
XWin.log as a result of issuing $ sh /usr/X11R6/bin/startxwin.sh:
 
 
*
 
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-2
Contact: cygwin-xfree.
XWin was started with the following command line:
XWin -multiwindow -clipboard -silent-dup-error
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
_XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership
(II) XF86Config is not supported
(II) See ...cygwin-x-faq for more information
(==) FontPath set to 
/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/
winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 depth: 16
winInitVisualsShadowGDI - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16
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
winInitMultiWindowWM - 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 
shared memory support in the kernel
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: 0409 (0409) 
(--) Using preset keyboard for English (USA) (409), type 4
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from 
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from 
list!
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 
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from 
list!
Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing 
from list!
Fatal server error:
could not open default font 'fixed'
winDeinitMultiWindowWM - Noting shutdown in progress
 
**
 
The method for defining the PATH on the commandline yielded similar content in 
its XWin.log, but for brevity sake that has been omitted.  Another undesired 
behavior arose when defining the PATH, $PATH=%PATH:/usr/X11R6/bin, locally in 
BASH and returning to the commandline after startx failed-the PATH environment 
variable inherited from Windows, which provides access to cygwin/usr, 
cygwin/usr/bin and hence all the shell programs (commands).  The Windows 
inherited PATH variable restores when opening a new Cygwin session. 
 
Please advise as to how xorg can be successfully launched on my computer?
 
 
 
Thanks and best regards,
 
 
Keith Kuchenbecker
PS - Why does the XWin.log file contain text/HTML or MIME components that 
bounce in your email server?
 
 


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



bye

2005-09-10 Thread Bruce

bye

--
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: Failed xorg/XWin launch

2005-09-10 Thread Ken Dibble
On Sat, Sep 10, 2005 at 10:27:41PM +, [EMAIL PROTECTED] wrote:
 To whom it may concern,
  
 All 4 methods outlined in the User's Guide of launching xorg/XWin produced 
 similar errors.  Further, attempts to cut-and-paste the contents of the 
 XWin.log or sending it as an attachement have generated MAILER-DAEMON errors 
 from your email server.
  
 All requisite xorg packages (in addition to optional ones) are installed.
  
 Here's another try of sending the contents (stripped of HTML content) to the 
 XWin.log as a result of issuing $ sh /usr/X11R6/bin/startxwin.sh:
  
  
 *
  
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 6.8.2.0-2
 Contact: cygwin-xfree.
 XWin was started with the following command line:
 XWin -multiwindow -clipboard -silent-dup-error
 ddxProcessArgument - Initializing default screens
 winInitializeDefaultScreens - w 1024 h 768
 winInitializeDefaultScreens - Returning
 _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership
 (II) XF86Config is not supported
 (II) See ...cygwin-x-faq for more information
 (==) FontPath set to 
 /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/
 winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel
 winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 depth: 16
 winInitVisualsShadowGDI - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16
 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
 winInitMultiWindowWM - 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 
 shared memory support in the kernel
 winMultiWindowXMsgProc - Hello
 winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
 (--) Setting autorepeat to delay=500, rate=31
 (--) winConfigKeyboard - Layout: 0409 (0409) 
 (--) Using preset keyboard for English (USA) (409), type 4
 (--) 3 mouse buttons found
 Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing 
 from list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from 
 list!
 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 
 list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing 
 from list!
 Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing 
 from list!
 Fatal server error:
 could not open default font 'fixed'
 winDeinitMultiWindowWM - Noting shutdown in progress
  
 **
  
 The method for defining the PATH on the commandline yielded similar content 
 in its XWin.log, but for brevity sake that has been omitted.  Another 
 undesired behavior arose when defining the PATH, $PATH=%PATH:/usr/X11R6/bin, 
 locally in BASH and returning to the commandline after startx failed-the PATH 
 environment variable inherited from Windows, which provides access to 
 cygwin/usr, cygwin/usr/bin and hence all the shell programs (commands).  The 
 Windows inherited PATH variable restores when opening a new Cygwin session. 
  
 Please advise as to how xorg can be successfully launched on my computer?
  
  
  
 Thanks and best regards,
  
  
 Keith Kuchenbecker
 PS - Why does the XWin.log file contain text/HTML or MIME components that 
 bounce in your email server?
  
  

Lacking the output of cygcheck -s -v -r as stated at
http://cygwin.com/problems.html

See:
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof

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