git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Peter Oberndorfer <kumbayo84@arcor.de>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, git@vger.kernel.org
Subject: Re: bug report: gitk crashes on git commit with emoji (utf-8)
Date: Sun, 11 Oct 2020 13:47:17 +0200	[thread overview]
Message-ID: <3318fdd6-5709-1d3c-64d8-01d029803635@arcor.de> (raw)
In-Reply-To: <1e06bde8-ae70-2653-5112-c97c9ee021da@gmail.com>

On 05.10.20 13:33, Tomek Mrugalski wrote:
> Hi there,
> 
Hi Tomek,

> $ ~/devel-ssd/git/gitk-git/gitk
> X Error of failed request:  BadLength (poly request too large or
> internal Xlib length error)
>   Major opcode of failed request:  139 (RENDER)
>   Minor opcode of failed request:  20 (RenderAddGlyphs)
>   Serial number of failed request:  3065
>   Current serial number in output stream:  3148

> 
> Is there a workaround I could try?
> 
I managed to work around this problem
by installing the Ubuntu package 'fonts-symbola'.

Testing with your repository, the Emoji is still not displayed correctly
but gitk does not crash anymore.

This issue (and the workaround) seems to be tracked at
https://bugs.launchpad.net/ubuntu/+source/git/+bug/1852985

> I'm willing to help with debugging the problem or testing patches.
> I'm not sure how long I'll be able to remain subscribed to this list
> due to the traffic volume.
> 
> Other than that, gitk has been rock solid stable for me and I've been
> using it for years. Thanks a lot for providing this great tool.
> 
> Tomek Mrugalski
> 
Greetings Peter


  reply	other threads:[~2020-10-11 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 11:33 bug report: gitk crashes on git commit with emoji (utf-8) Tomek Mrugalski
2020-10-11 11:47 ` Peter Oberndorfer [this message]
2020-10-13  8:00   ` Tomek Mrugalski
2020-10-11 12:32 ` Đoàn Trần Công Danh

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=3318fdd6-5709-1d3c-64d8-01d029803635@arcor.de \
    --to=kumbayo84@arcor.de \
    --cc=git@vger.kernel.org \
    --cc=tomasz.mrugalski@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.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).