unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 30788@debbugs.gnu.org, mats.lidell@cag.se
Subject: bug#30788: 27.0.50; Getting 'char-displayable-p: Invalid hash table rehash size: 1.0' when starting emacs -Q
Date: Wed, 14 Mar 2018 20:15:43 +0200	[thread overview]
Message-ID: <83po46r0a8.fsf@gnu.org> (raw)
In-Reply-To: <23209.25224.689775.102503@a1i15.kph.uni-mainz.de> (message from Ulrich Mueller on Wed, 14 Mar 2018 18:57:28 +0100)

> Date: Wed, 14 Mar 2018 18:57:28 +0100
> Cc: 30788@debbugs.gnu.org,
>     mats.lidell@cag.se
> From: Ulrich Mueller <ulm@gentoo.org>
> 
> > +	/* Do this after the call to xg_initialize, because when
> > +	   Fontconfig is used, xg_initialize calls its initialization
> > +	   function which in some versions of Fontconfig calls setlocale.  */
> > +	fixup_locale ();
> > +
> >          dpy = DEFAULT_GDK_DISPLAY ();
> > 
> >  #if ! GTK_CHECK_VERSION (2, 90, 0)
> 
> This fixes the problem (tested with fontconfig-2.13.0).

Thanks, pushed to the release branch.

> Note that it has also been fixed in the fontconfig git repository:
> https://cgit.freedesktop.org/fontconfig/commit/?id=923b5be626a6e03fbaeee0b5cd6d0246c2f8f36f

I've seen that.  Does it really fix the problem?  What happens if you
run Emacs like so:

  $ LC_ALL=C emacs -Q

(If this works with the fixed version of fontconfig, then I guess I
completely misunderstand the issue.)

In any case, I think it's good for Emacs to be immune to buggy
versions of fontconfig, especially since we already needed to clean up
after similar problems in gtk_init.

Thanks.





  reply	other threads:[~2018-03-14 18:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 22:12 bug#30788: 27.0.50; Getting 'char-displayable-p: Invalid hash table rehash size: 1.0' when starting emacs -Q Mats Lidell
2018-03-13  3:44 ` Eli Zaretskii
2018-03-13 10:14 ` Ulrich Mueller
2018-03-13 16:14   ` Eli Zaretskii
2018-03-13 17:42     ` Mats Lidell
2018-03-13 18:08       ` Eli Zaretskii
2018-03-13 18:58         ` Ulrich Mueller
2018-03-13 19:07           ` Ulrich Mueller
2018-03-13 19:32             ` Eli Zaretskii
2018-03-13 20:06               ` Ulrich Mueller
2018-03-14  3:32                 ` Eli Zaretskii
2018-03-14  6:48                   ` Ulrich Mueller
2018-03-14 16:15                     ` Eli Zaretskii
2018-03-14 17:57                       ` Ulrich Mueller
2018-03-14 18:15                         ` Eli Zaretskii [this message]
2018-03-14 21:19                           ` Ulrich Mueller
2018-03-16  2:45                           ` Noam Postavsky
2018-03-16  3:38                             ` Eli Zaretskii
2018-03-13 21:26 ` Ulrich Mueller
2018-05-04 21:58 ` Peter Dyballa
2018-05-04 22:13   ` Glenn Morris
2018-05-05  8:06     ` Peter Dyballa
2018-05-15 14:02     ` Peter Dyballa
2018-05-15 17:06       ` Eli Zaretskii
2018-05-15 21:38         ` Peter Dyballa
2018-05-16  2:30           ` Eli Zaretskii
2018-05-16 23:22             ` Peter Dyballa
2018-05-17 14:56               ` Eli Zaretskii
2018-05-19 11:21                 ` Peter Dyballa
2018-05-19 11:45               ` Philipp Stephani

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83po46r0a8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=30788@debbugs.gnu.org \
    --cc=mats.lidell@cag.se \
    --cc=ulm@gentoo.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).