public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Stefan Katletz <stefan.katletz@gmail.com> To: cygwin-xfree@cygwin.com Subject: Re: xfig: Warning: Missing charsets in String to FontSet conversion Date: Sun, 22 May 2016 13:27:00 -0000 [thread overview] Message-ID: <CA+xtEwUkVwrQgs+TYUVvtNppb74xsrz9vzYg8dshM9M9gWjgPw@mail.gmail.com> (raw) Hello, I am now facing this (old) problem on a new installation under Windows 10. I tried 32 and 64 bit installations of cygwin, no difference: xfig gives this warning, and crashes when I want to save/export the drawing. $ Warning: Missing charsets in String to FontSet conversion xfig3.2.5c: SIGSEGV signal trapped xfig: attempting to save figure xfig: 1 object(s) saved in "/home/kat/SAVE.fig" At least the work is not all lost, I used xfig under linux to do export... Does anybody know what's going on? I am happy to supply logs if somebody cares. I was reading the old mails, but couldn't find a solution. I tried to install all font packages in cygwin I was offered, but the warning appears even when starting with an empty drawing. thanks, Stefan -- 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/
next reply other threads:[~2016-05-22 13:27 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-05-22 13:27 Stefan Katletz [this message] 2016-05-22 13:55 ` Stefan Katletz 2016-05-22 14:21 ` Marco Atzeri 2016-05-22 20:47 ` Stefan Katletz -- strict thread matches above, loose matches on Subject: below -- 2013-02-04 0:14 Andy 2013-02-04 15:26 ` Jon TURNEY 2013-02-05 0:27 ` Jack 2013-02-05 7:05 ` Andy 2013-02-12 14:12 ` Jon TURNEY 2013-02-12 14:42 ` marco atzeri 2013-02-12 15:42 ` Jon TURNEY 2013-02-12 15:53 ` marco atzeri 2013-02-13 17:17 ` Jack 2013-02-13 21:47 ` Thomas Dickey 2013-02-13 22:48 ` Jack 2013-02-13 23:26 ` Thomas Dickey 2013-02-14 16:15 ` Jon TURNEY
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=CA+xtEwUkVwrQgs+TYUVvtNppb74xsrz9vzYg8dshM9M9gWjgPw@mail.gmail.com \ --to=stefan.katletz@gmail.com \ --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: linkBe 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).