From: Stephen Nadas <stephen.nadas@gmail.com>
To: cygwin-digest@cygwin.com
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: cygwin Digest 18 Oct 2015 22:48:10 -0000 Issue 9353
Date: Mon, 19 Oct 2015 15:52:00 -0000 [thread overview]
Message-ID: <CADMABNs1-F=YCRPs4nGyrkCB=7uDjrtE=0=FeWABvkpkmWMmnQ@mail.gmail.com> (raw)
In-Reply-To: <1445208490.13841.ezmlm@cygwin.com>
On Sun, Oct 18, 2015 at 6:48 PM, <cygwin-digest-help@cygwin.com> wrote:
> xfig-3.2.5c-2.x86_64 segfaults on save-as and export in current cygwin64 on Windows 10
Hi,
A follow up.
I down leveled the xorg-server* (5 packages from 1.17.2-4 to 1.17.2-3
-common, -devel, -dmx, -extra + servers) and this really bad behavior
goes away (Xfig saves as and/or exports files). There is a segfault
when it exits & some complaints re missing fonts (?) but I can
function.
Cheers,
Steve
--
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
parent reply other threads:[~2015-10-19 15:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1445208490.13841.ezmlm@cygwin.com>]
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='CADMABNs1-F=YCRPs4nGyrkCB=7uDjrtE=0=FeWABvkpkmWMmnQ@mail.gmail.com' \
--to=stephen.nadas@gmail.com \
--cc=cygwin-digest@cygwin.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).