public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: D Jackson <drmc@microdash.com>
To: cygwin-xfree@cygwin.com
Subject: Re: Problem starting XWin Server
Date: Mon, 22 Aug 2011 17:30:00 -0000	[thread overview]
Message-ID: <loom.20110822T191023-333@post.gmane.org> (raw)
In-Reply-To: <4E401225.9090808@dronecode.org.uk>

Jon TURNEY <jon.turney <at> dronecode.org.uk> writes:

> 
> On 30/07/2011 07:10, Jan Chludzinski wrote:
> >  From within a mintty shell, I get:
> >
> > $ startxwin
> >
> > giving up.
> > startxwin:  No such file or directory (errno 2):  unable to connect to X 
server
> > startxwin:  No such process (errno 3):  Server error.
> 
> That's odd.  I can't really understand how that can happen.  I'd suspect 
that 
> startxwin is failing to fork/exec Xwin successfully, possibly due to an 
> application causing cygwin difficulties [1] (Unfortunately, 64-bit Windows 
> itself seems to sometimes cause similar problems)
> 
> Are you able to start the server directly by running 'XWin'?
> 
> [1] http://cygwin.com/faq-nochunks.html#faq.using.bloda
> 


I have same issue. I have reinstalled Cygwin 5 times. Each time I can start 
XWin fine UNTIL I rebaseall or perlrebase or until I uninstall+reinstall 
perl/Tk. The .log file is from the first couple times it sucessfully came up 
(prior to the rebase and the errors) and nothing is written to any logfiles or 
even STDERR/STDOUT except for the:
$ xinit
giving up.
xinit:  No such file or directory (errno 2):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

or
$ startxwin
giving up.
startxwin:  No such file or directory (errno 2):  unable to connect to X server
startxwin:  No such process (errno 3):  Server error.

I have added the env variable CYGWIN=tty but still nothing more informative is 
written to any files or terminal. 

My hardware is  a HP EliteBook sitting on MS XP Pro version 2002 SP3. I have 
altered the rebaseall script to actually complete, as it is failing on the 
64bit dlls. ( added filter to sed to not include the specific dlls from list 
creation ) I have tried this both ways in 'stock' form from repository and 
altered to complete. 

This is 100% reproducible. I can reproduce this every time even with fully 
fresh installs of cygwin.

My goal is to get a version of Cyg X running that I can run cssh and have a 
full menubar ( this is why the initial rebase and then the subsequent 
reinstalls and the mucking about with the Perl/Tk stuff )

Thanks for any information in advance, 

DJ  


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


      reply	other threads:[~2011-08-22 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADqjQ-LnaUZWLPf9gtVkTkLZs0gM+xh7xAPO57kDm0W5xFjdVA@mail.gmail.com>
2011-07-12 21:16 ` Jan Chludzinski
2011-07-13 12:30   ` Jon TURNEY
2011-07-14 14:11     ` Jan Chludzinski
2011-07-19 16:15       ` Jon TURNEY
2011-07-31 18:54         ` Jan Chludzinski
2011-08-08 16:43           ` Jon TURNEY
2011-08-22 17:30             ` D Jackson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20110822T191023-333@post.gmane.org \
    --to=drmc@microdash.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).