Re: Cannot start X server
Thanks Andrew works fine now !!!
Re: Cannot start X server
Sorry for the cross-post, but I feel it's relevant to both lists... We should move any resulting discussion to one of them (probably [EMAIL PROTECTED]). On Mon, 21 Oct 2002, Christopher Faylor wrote: On Mon, Oct 21, 2002 at 11:11:19AM -0600, Andrew Grimm wrote: This is not really an XFree problem, rather it is a global Cygwin issue caused by a policy change that took most people by surprise. Sounds like most people need to read the cygwin release announcements a little more closely rather than just blindly upgrading. cgf In retrospective, would it help to mark any other new release with such a major policy change 'Experimental' for a while? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Water molecules expand as they grow warmer (C) Popular Science, Oct'02, p.51
Re: Cannot start X server
On Tue, Oct 22, 2002 at 11:06:01AM -0400, Igor Pechtchanski wrote: Sorry for the cross-post, but I feel it's relevant to both lists... We should move any resulting discussion to one of them (probably [EMAIL PROTECTED]). On Mon, 21 Oct 2002, Christopher Faylor wrote: On Mon, Oct 21, 2002 at 11:11:19AM -0600, Andrew Grimm wrote: This is not really an XFree problem, rather it is a global Cygwin issue caused by a policy change that took most people by surprise. Sounds like most people need to read the cygwin release announcements a little more closely rather than just blindly upgrading. In retrospective, would it help to mark any other new release with such a major policy change 'Experimental' for a while? That's what snapshots are for. cgf
Cannot start X server
Hi there, i have seen the enclosed mail from Nicolas at the archive. I have the same problems. First the xserver works fine, after a reboot of the systems it dont work again. Is the a solution ... regards Walter * From: Nicolas F Rouquette * Subject: Cannot start X server * Date: Tue, 15 Oct 2002 11:48:29 -0700 I have been running cygwin X for quite a while. Recently, my setup got corrupted after a setup session gone bad (not sure why). Today, I reinstalled everything (cygwin xfree) from the internet but I can't start a basic X server. Here's what I get: $ startx waiting for X server to begin accepting connections . .. .. [repeated many times] .. giving up. xinit: Permission denied (errno 13): unable to connect to X server waiting for X server to shut down xinit: Server error The /tmp/XWin.log doesn't seem to have particularly alarming messages, except for the ownership message that I've read in the mailing list archive to ignore (perhaps it no longer should???) - ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1200 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 1166 1600 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1166 1600 winCreateBoundingWindowWindowed - WindowClient w 1594 h 1135 r 1594 l 0 b 1135 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowDDNL - lPitch: 6376 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winScreenInit - returning Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, 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/100dpi/, removing from list! --- Suggestions? -- Nicolas.
Re: Cannot start X server
I was having the exact same problem starting X under the newest Cygwin release. I also found this very frustrating as I have been running X for quite some time with no problems, then *boom* it suddenly broke. One option that worked for me was to downgrade to the previous version of the DLL (backout 1.3.13-2 to 1.3.12-4). This is simple to do using the setup program but is not a long-term solution. I am not an expert on this, but some research revealed that 1.3.13-2 has turned on the ntsec option by default. If your computer is in an NT domain, this affects you. To check, compare the UID/GID reported by your id -a command with the ownership of your existing files ls -ln $HOME. If they don't match, you need to update your /etc/passwd and/or /etc/group files. You can do this by replacing the yourusername entry in /etc/passwd with the output of mkpasswd -d -u yourusername and updating /etc/group with the output of mkgroup -d | grep :yourGID: (note that the angled brackets are meant to indicate variables and are not literally part of the commands). This is not really an XFree problem, rather it is a global Cygwin issue caused by a policy change that took most people by surprise. Hope that fixes your particular problem, Andy
Re: Cannot start X server
On Mon, Oct 21, 2002 at 11:11:19AM -0600, Andrew Grimm wrote: This is not really an XFree problem, rather it is a global Cygwin issue caused by a policy change that took most people by surprise. Sounds like most people need to read the cygwin release announcements a little more closely rather than just blindly upgrading. cgf
Re: Cannot start X server
This is not really an XFree problem, rather it is a global Cygwin issue caused by a policy change that took most people by surprise. Sounds like most people need to read the cygwin release announcements a little more closely rather than just blindly upgrading. cgf It was not my intention to sound cynical. I was merely pointing out that the problem in question was not an XFree-specific problem. However To a Cygwin developer or expert CYGWIN=ntsec is now on by default probably serves fine as a description (albeit buried amongst 37 other change notes). However, most of the Cygwin-using community would not mentally equate that with I need to update my authentication files or Cygwin will break or know offhand how to do that. The User's Guide is great. However, your average user will not have waded through the ntsec section for the fun of it, because a standard Cygwin install works out of the box. Ironically, uneducated users may be the one price of quality (note that I must group myself as uneducated in the true ways of Cygwin, although I've been using it and XFree for some time). The setup program, which I run every morning like a kid at Christmas, encourages people to install updates by making it mind-numbingly simple. This is usually good and quite cool. However, given that model, perhaps a package mechanism which would inform users of required (non-automatable) configuration changes would be nice. This is not a flame. I have a deep appreciation for the hard work that goes into Cygwin and the quality of the evolving product--as well as for the time spent by those individuals whose efforts make Cygwin possible. I merely suggest that the upgrade process could do more to identify potential impacts and suggest corrective action, be that in the release notes or integrated into the process itself. -Andy
Cannot start X server
I have been running cygwin X for quite a while. Recently, my setup got corrupted after a setup session gone bad (not sure why). Today, I reinstalled everything (cygwin xfree) from the internet but I can't start a basic X server. Here's what I get: $ startx waiting for X server to begin accepting connections . .. .. [repeated many times] .. giving up. xinit: Permission denied (errno 13): unable to connect to X server waiting for X server to shut down xinit: Server error The /tmp/XWin.log doesn't seem to have particularly alarming messages, except for the ownership message that I've read in the mailing list archive to ignore (perhaps it no longer should???) - ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1200 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winAdjustForAutoHide - Original WorkArea: 0 0 1166 1600 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1166 1600 winCreateBoundingWindowWindowed - WindowClient w 1594 h 1135 r 1594 l 0 b 1135 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowDDNL - lPitch: 6376 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winScreenInit - returning Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, 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/100dpi/, removing from list! --- Suggestions? -- Nicolas.
