From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: adam@dinwoodie.org
Subject: Re: git gui: assertion "font != NULL" failed
Date: Mon, 19 Oct 2015 14:54:00 -0000 [thread overview]
Message-ID: <5625041F.6020702@dronecode.org.uk> (raw)
In-Reply-To: <1445020196.12068.11.camel@cygwin.com>
On 16/10/2015 19:29, Yaakov Selkowitz wrote:
> On Fri, 2015-10-16 at 17:09 +0000, Matt Seitz (matseitz) wrote:
>> A few days ago, I ran Setup to update my currently installed package, including my git packages. Since then, whenever I run git gui, I get the following error:
>>
>> $ git gui
>> assertion "font != NULL" failed: file "/usr/src/ports/fontconfig/fontconfig-2.11.1-3.x86_64/src/fontconfig-2.11.1/src/fcmatch.c", line 453, function: FcFontRenderPrepare
>> error: git-gui died of signal 6
>>
>> cygcheck and xwin logs attached
>
> You don't have any Fontconfig-controlled fonts installed on your system.
> On mine, the default seems to be dejavu-fonts, so try installing that,
> although xorg-x11-fonts-Type1 might work as well.
The dependency chain is git-gui -> gitk -> font-adobe-dpi75
It doesn't look like the fonts in xorg-x11-fonts-Type1 are available to
fontconfig, so I've changed the dependency of gitk to dejavu-fonts on
sourceware.
Adam,
You might wish to update your local setup.hint and/or select a better
default.
--
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
next prev parent reply other threads:[~2015-10-19 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 17:09 Matt Seitz (matseitz)
2015-10-16 18:29 ` Yaakov Selkowitz
2015-10-19 14:54 ` Jon Turney [this message]
2015-10-23 15:02 ` Matt Seitz (matseitz)
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=5625041F.6020702@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=adam@dinwoodie.org \
--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).