public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash
Date: Mon, 14 May 2018 21:47:00 -0000	[thread overview]
Message-ID: <3a375be2-499f-1f40-8c90-7c91b8822e3e@dronecode.org.uk> (raw)
In-Reply-To: <7a60e967-6861-5e5c-f0ee-5ebb6bf14e23@SystematicSw.ab.ca>

On 14/05/2018 20:30, Brian Inglis wrote:
> On 2018-04-26 08:03, Jon Turney wrote:
>> On 19/04/2018 22:15, Gilles Detillieux wrote:
>>> Has anybody else run into this problem? I've done two installations of
>>> Cygwin/X on Windows 10 systems this week, and they both had problems with the
>>> XWin Server dying just a few seconds after starting up. I traced the problem
>>> back to xwin-xdg-menu.exe getting a Segmentation fault, which then causes XWin
>>> Server to exit. I hacked an alternate .startxwinrc file to prevent XWin Server
>>> from dying (it ends with a "sleep infinity"), so I could debug it further.
>>>
>>> With the XWin Server running reliably, I then ran "strace xwin-xdg-menu.exe"
>>> and saw that it got a segmentation fault just after reading a TTF font from
>>> the Windows Font directory (bahnschrift.ttf if it matters). I noticed there
>>> were two recent library updates related to font handling, so I tried back out
>>> to the previous version for each. It turns out that when I reverted to version
>>> 1.7.4-1 of libharfbuzz0, xwin-xdg-menu.exe stopped crashing.
>>>
>>> If it matters, both these systems are the Fall Creator's Update (1709) of
>>> Windows 10 64-bit, and I'm running the 32-bit version of Cygwin.
>>>
>>> Hopefully someone can track down and fix this recent bug!
>>
>> Thanks for reporting this.
>>
>> I can reproduce this problem, but it only seems to occur with 32-bit cygwin.
>>
>> (Obviously you also need a recent enough Windows 10 to have the Bahnschrift font)
>>
>> The actual crash seems to be in fontconfig, e.g. 'fc-query
>> /usr/share/fonts/microsoft/bahnschrift.ttf' fails in the same way.
>>
>> I didn't get very far investigating the problem, as rebuilding the fontconfig
>> package with the current toolchain seems to be enough to make the problem go away.
> 
> I haven't noticed any problems with Bahnschrift, but as it is a DE DIN 1451

Note that this problem only effects 32-bit Cygwin.

> Schrift (typeface), based on the original URW Fette Mittelschrift (bold
> regular), Engschrift (condensed), Breitschrift (expanded), it could be
> substituted by similar free fonts such as the Google Fonts Roboto family or SIL
> OFL licensed equivalents.

--
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-14 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 21:15 Gilles Detillieux
2018-04-24 21:30 ` Gilles Detillieux
2018-04-26 14:03 ` Jon Turney
2018-04-26 15:40   ` Gilles Detillieux
2018-05-12 14:27     ` Jon Turney
2018-05-14 19:29       ` Gilles Detillieux
2018-05-14 21:44         ` Jon Turney
2018-05-15 15:01           ` Gilles Detillieux
2018-05-14 21:38   ` Brian Inglis
2018-05-14 21:47     ` 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=3a375be2-499f-1f40-8c90-7c91b8822e3e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).