public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Joshua Hoke <jhoke@automate.com>
To: cygwin@cygwin.com
Subject: Re: Windows 7 update broke Cygwin X?
Date: Mon, 12 Sep 2016 13:01:00 -0000	[thread overview]
Message-ID: <CABHjk8CN02nkNEJsdHv65q8cbyLccAXGMxtPmqmRme=ZQyq=cA@mail.gmail.com> (raw)
In-Reply-To: <CABHjk8DcX9SzOE++mK9fh9xb604ZUBejgrA1hw=o_GQC=SiRfw@mail.gmail.com>

On Fri, Sep 9, 2016 at 1:17 PM, Joshua Hoke <jhoke@automate.com> wrote:
> On Fri, Sep 9, 2016 at 12:42 PM, Marco Atzeri <marco.atzeri@gmail.com> wrote:
>> On 09/09/2016 18:03, Joshua Hoke wrote:
>>> After a recent Windows update, I am unable to start Cygwin's X server
>>> anymore. I tried updating to the latest Cygwin by running setup again,
>>> /usr/bin/rebaseall and rebooting. There are no obvious errors from the
>>> X server if I run /usr/bin/startxwin from a Cygwin console, but it
>>> seems to exit after 20 seconds or so:

I tried following directions from
https://cygwin.com/ml/cygwin/2015-07/msg00448.html for debugging with
strace and it seems there is an exception occurring inside a Trend
Micro DLL, causing XWin.exe to exit silently. At this point I don't
consider it a problem with Cygwin/X anymore, except that possibly it
should exit with a non-zero exit status. I am using a different X
server at the moment as a workaround.

--
Joshua Hoke

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

  reply	other threads:[~2016-09-12 13:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 16:04 Joshua Hoke
2016-09-09 16:43 ` Marco Atzeri
2016-09-09 17:17   ` Joshua Hoke
2016-09-12 13:01     ` Joshua Hoke [this message]
2016-09-12 19:13       ` Achim Gratz

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='CABHjk8CN02nkNEJsdHv65q8cbyLccAXGMxtPmqmRme=ZQyq=cA@mail.gmail.com' \
    --to=jhoke@automate.com \
    --cc=cygwin@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).