From: Unknown <ax487@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37895@debbugs.gnu.org
Subject: bug#37895: 26.3; X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139
Date: Thu, 24 Oct 2019 20:06:35 +0200 [thread overview]
Message-ID: <898cb0bbc5006ac293c21eb8dfe876faf3f6be27.camel@gmx.de> (raw)
In-Reply-To: <837e4uxgdr.fsf@gnu.org>
On Thu, 2019-10-24 at 19:22 +0300, Eli Zaretskii wrote:
> > From: Unknown <ax487@gmx.de>
> > Cc: 37895@debbugs.gnu.org
> > Date: Thu, 24 Oct 2019 17:34:00 +0200
> >
> > Regarding the tracing: As far as I can see the bottommost emacs
> > code
> > being called is
> >
> > static Lisp_Object
> > xftfont_open (struct frame *f, Lisp_Object entity, int pixel_size)
> >
> > I also got
> >
> > (gdb) call debug_print(entity)
> > #<font-entity xft GOOG JoyPixels nil iso10646-1 normal normal
> > normal 0
> > nil nil 0 ((:font-entity "/usr/share/fonts/TTF/JoyPixels.ttf" .
> > 0))>
>
> So your file included some emoji, is that correct?
Well, that stands to reason. I suspect the doom-modeline package
https://github.com/seagle0128/doom-modeline
which relies heavily on icons and unicode symbols. In particular, there
are icons for the file types and minor modes. I think that opening a
C/C++ file activates some major/minor mode associated with an
icon/symbol triggering the error.
next prev parent reply other threads:[~2019-10-24 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 22:14 bug#37895: 26.3; X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139 Unknown
2019-10-24 13:58 ` Eli Zaretskii
2019-10-24 15:34 ` Unknown
2019-10-24 16:22 ` Eli Zaretskii
2019-10-24 18:06 ` Unknown [this message]
2019-10-25 16:37 ` Robert Pluim
[not found] ` <e0f168af7a18e4cbeadacfe2fad997d2b72a6909.camel@gmx.de>
2019-10-27 8:09 ` Robert Pluim
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=898cb0bbc5006ac293c21eb8dfe876faf3f6be27.camel@gmx.de \
--to=ax487@gmx.de \
--cc=37895@debbugs.gnu.org \
--cc=eliz@gnu.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).