public inbox for
help / color / mirror / Atom feed
From: Reinier Post <>
Subject: Re: can not startx
Date: Thu, 13 Jan 2011 15:40:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Yaakov (Cygwin/X <yselkowitz <at>> writes:

> On 05/01/2010 16:56, eric lin wrote:
> > this is my /var/log/XWin.0.log
> > where I think problm cause, fail startx, please help, eric
> Sigh.  Lets try this again:
> > Problem reports:
> Yaakov
> Cygwin/X

I can't follow the rules, there because I'm posting this from

which doesn't support attachments.

My XWin.0.log exhibits the same problem eric lin reported:

  XKB: Could not invoke xkbcomp

To check this I replaced xkbcomp with a shell script and indeed,
it does not get called.  Running as X -logverbose 100 does not
shed any light on the problem.  Running X or XWin with strace doesn't
work (strace refuses to run X and on XWin crashes out with access violation,
I'm on Windows 7).

The problem appeared after running a rebaseall and rebooting for a regular
Windows 7 update.  I haven't made any hardware changes and Cygwin/X was
running fine yesterday.  After the problem appeared,
running another erebaseall or updating my Cygwin 1.7 installation
didn't help.

I'm not replying here to report the problem in full detail
(because I can't add attachments) but to report a workaround:
install XMing from

and run that.  Then after setting $DISPLAY to
I can run X clients such as xterm from the Cygwin bash prompt.

Reinier Post
TU Eindhoven

Unsubscribe info:
Problem reports:

  reply	other threads:[~2011-01-13 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 22:56 eric lin
2010-01-06  0:08 ` Yaakov (Cygwin/X)
2011-01-13 15:40   ` Reinier Post [this message]
2011-01-13 19:23     ` Larry Hall (Cygwin X)
2011-01-17 16:11     ` Jon TURNEY
2011-01-17 20:47       ` Reinier Post

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:

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

  git send-email \ \ \ \

* 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).