public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: Jeff Rankin <jeffrey.rankin@me.com>
Subject: Re: X windows fatal errors following install of Feature update to Windows 10, version 1803
Date: Sat, 12 May 2018 15:07:00 -0000	[thread overview]
Message-ID: <54ba1929-42d9-280a-75fd-8964e55f05a4@dronecode.org.uk> (raw)
In-Reply-To: <1D6B1715-51FF-41DD-AD55-7DE4BFB38105@me.com>

On 03/05/2018 19:46, Jeff Rankin wrote:

> On two Windows 10/Cygwin installations, I have fatal errors with X windows following installation of “Feature update to Windows 10, version 1803” yesterday (May 1). The startxwin command output tail is:
[...]
> jrankin@Windows10: ~ cat xwin-xdg-menu.exe.stackdump
> 
> Exception: STATUS_ACCESS_VIOLATION at eip=6BB0F8F0
> eax=201DE7C8 ebx=00010007 ecx=00000002 edx=0000FFFF esi=00000000 edi=201DE7F0
> ebp=201D2950 esp=0067B550 program=C:\cygwin\bin\xwin-xdg-menu.exe, pid 3720, thread main
> cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
> Stack trace:
> Frame     Function  Args
> 201D2950  6BB0F8F0 (00000919, 000F0000, 00000344, 201DCA00)

Thanks for reporting this.

This is the same problem as [1], see the workarounds there.

[1] https://cygwin.com/ml/cygwin/2018-05/msg00153.html

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
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:[~2018-05-12 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 18:46 Jeff Rankin
2018-05-12 15:07 ` Jon Turney [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=54ba1929-42d9-280a-75fd-8964e55f05a4@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=jeffrey.rankin@me.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).