public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: jan.chludzinski@gmail.com
Subject: Re: Problem starting XWin Server
Date: Tue, 19 Jul 2011 16:15:00 -0000	[thread overview]
Message-ID: <4E25A34D.8070003@dronecode.org.uk> (raw)
In-Reply-To: <CADqjQ-LddjG963K1bAvnwNipbD2_3sxht_28ZwkHY5dnj+o0Ng@mail.gmail.com>

On 14/07/2011 10:29, Jan Chludzinski wrote:
> First, THANKS!
> 
>     $ 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.

Sorry, I hadn't quite grasped that is the whole of the output.

For obscure technical reasons, the output of XWin doesn't appear in a cmd.exe
terminal if cygwin wasn't started with CYGWIN=tty.

Can I suggest you install mintty, and try running startxwin from that, which
should produce some more informative output.

It looks like Cygwin/X FAQ 2.4 could do with some improvement :-)

> The server is never started - no process in the Windows "Resource
> Monitor".  When I try to start xedit (or whatever X based app) nothing
> happens, nothing appears.
> 
> As for FAQ, I'm afraid I don't see anything that might help.  I looked
> before I posted the original e-mail.
> 
> ---John
> 
> On Wed, Jul 13, 2011 at 8:21 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote:
>> On 12/07/2011 09:10, Jan Chludzinski wrote:
>>> I just did a complete installation of X11 from Cygwin 1.7 setup.exe.
>>> But when I try to start the "XWin Server" using the "Start" menu
>>> nothing happens.  If I try either "startxwin" or "startx" or "xinit"
>>> from the BASH shell I get:
>>>
>>> giving up.
>>> startxwin:  No such file or directory (errno 2):  unable to connect to X server
>>> startxwin:  No such process (errno 3):  Server error.
>>>
>>> Any suggestions?
>>
>> Looking at the XWin.0.log you attached, it looks like the X server is starting
>> up successfully.
>>
>> If clients are unable to connect, this might be due to firewall configuration
>> or other software which interferes with cygwin sockets (see [1] in the
>> Cygwin/X FAQ for some suggestions)
>>
>> [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cannot-open-display

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
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-07-19 15:31 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 [this message]
2011-07-31 18:54         ` Jan Chludzinski
2011-08-08 16:43           ` Jon TURNEY
2011-08-22 17:30             ` D Jackson

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=4E25A34D.8070003@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=jan.chludzinski@gmail.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).