public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cygwin-xfree@cygwin.com
Subject: Cygwin 1.7.22 calls dumper when starting X
Date: Tue, 30 Jul 2013 17:33:00 -0000	[thread overview]
Message-ID: <CAK-n8j6yg-he-qtugdiirYUMNySms6mNHU0yo3pRz_5xsP1wFA@mail.gmail.com> (raw)

I have the latest version of Cygwin (using setup-x86). I see the same
problem on both 32-bit and 64-bit Windows 7 systems.

CYGWIN_NT-6.1 LTDEN-REISERT 1.7.22(0.268/5/3) 2013-07-22 17:06 i686 Cygwin

Here is how I am starting X:

C:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe

When I run this command, a dumper console window pops up with this error:

"failed to open file: No such file or directory"

I had not seen this before updating setup to setup-x86 and installing
the latest code.  The console window goes away by itself, and XWin
seems to have started normally, I.e. I get the 'X' in my system tray
and can launch programs from it.

- Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
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:[~2013-07-30 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 17:33 Jim Reisert AD1C [this message]
2013-07-30 18:37 ` Jim Reisert AD1C
2013-07-31 11:58 ` Jon TURNEY
2013-07-31 13:41   ` Jim Reisert AD1C
2013-07-31 16:10     ` Jim Reisert AD1C
2013-07-31 19:22     ` Charles Wilson
2013-08-01 11:20 Angelo Graziosi
2013-08-01 13:09 ` Charles Wilson
2013-08-01 21:34 Angelo Graziosi
2013-08-01 22:06 ` Mark Hansen

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=CAK-n8j6yg-he-qtugdiirYUMNySms6mNHU0yo3pRz_5xsP1wFA@mail.gmail.com \
    --to=jjreisert@alum.mit.edu \
    --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).