From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
To: Peter Oberndorfer <kumbayo84@arcor.de>, git@vger.kernel.org
Subject: Re: bug report: gitk crashes on git commit with emoji (utf-8)
Date: Tue, 13 Oct 2020 10:00:43 +0200 [thread overview]
Message-ID: <13bc5c41-8989-5551-51ba-eec30b59900c@gmail.com> (raw)
In-Reply-To: <3318fdd6-5709-1d3c-64d8-01d029803635@arcor.de>
On 11.10.2020 13:47, Peter Oberndorfer wrote:
>> $ ~/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'.
Hi Peter,
Yes, the workaround works on 2.28 on ubuntu 20.04.
> 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
Uh, missed that. Thanks for the pointer.
Hmm. It seems this is very dependent on what kind of fonts are in the
system and the lib could crash. You may possibly consider implementing
some sort of --dont-display-utf8 option. Or perhaps waiting for the
xlib bug to be fixed is less involving option.
Anyway, I can again use gitk.
Thanks again for this great software.
Tomek
next prev parent reply other threads:[~2020-10-13 8:01 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
2020-10-13 8:00 ` Tomek Mrugalski [this message]
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=13bc5c41-8989-5551-51ba-eec30b59900c@gmail.com \
--to=tomasz.mrugalski@gmail.com \
--cc=git@vger.kernel.org \
--cc=kumbayo84@arcor.de \
/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).