From: "Bravery, Gavin S" <gavin.bravery@imperial.ac.uk>
To: Jon TURNEY <jon.turney@dronecode.org.uk>,
jaakov jaakov <jaakov@ro.ru>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: run.exe fails to start XWin in Windows 8.1
Date: Thu, 04 Jun 2015 11:57:00 -0000 [thread overview]
Message-ID: <C5101A1534B7D7418DE06BC355FD7D63C35EA411@icexch-m1.ic.ac.uk> (raw)
In-Reply-To: <55703436.7050002@dronecode.org.uk>
You review (and possible upload) the output from this directory:
/var/log/xwin
You could at least then confirm the xwin application is running, and starting (even if it then crashes)...
I had issues after recent upgrades (probably over a year ago) because of what I had in my local .startxwin...
I only discovered it by looking at these xwin logs.
Gavin
-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of Jon TURNEY
Sent: 04 June 2015 12:19
To: jaakov jaakov; cygwin@cygwin.com
Subject: Re: run.exe fails to start XWin in Windows 8.1
On 01/06/2015 22:38, jaakov jaakov wrote:
> Finally, I got to the machine that won't start XWin. It is different
> now: XWin won't start as before, but now no run.exe.stackdump file is
> produced. The start command is
>
> C:\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd;
> /usr/bin/startxwin"
Thanks for following up on this.
But I'm sorry, there's nothing to go on there.
Is it possible for you to upload the output of stracing that run command somewhere?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-06-04 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 20:43 jaakov jaakov
2015-05-18 17:09 ` Jon TURNEY
2015-05-18 17:16 ` Jaakov
[not found] ` <1433194723.669375.16882.18430@mail.rambler.ru>
2015-06-04 11:19 ` Jon TURNEY
2015-06-04 11:57 ` Bravery, Gavin S [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=C5101A1534B7D7418DE06BC355FD7D63C35EA411@icexch-m1.ic.ac.uk \
--to=gavin.bravery@imperial.ac.uk \
--cc=cygwin@cygwin.com \
--cc=jaakov@ro.ru \
--cc=jon.turney@dronecode.org.uk \
/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).