From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: ng0 <ng0@n0.is>
Cc: 24279@debbugs.gnu.org
Subject: bug#24279: XTerm menu doesn't work (no font found error)
Date: Wed, 29 Nov 2017 07:56:48 -0500 [thread overview]
Message-ID: <87fu8xp7jj.fsf@gmail.com> (raw)
In-Reply-To: <20171128124143.3vvpsxzuhchuztqz@abyayala> (ng0@n0.is's message of "Tue, 28 Nov 2017 12:41:43 +0000")
Hi ng0,
ng0 <ng0@n0.is> writes:
> Maxim Cournoyer transcribed 0.5K bytes:
>> I can reproduce this on GuixSD (foreign distros are OK).
>>
>> By going to tty0 (Ctrl-Alt-F1) we can see the following text which gets
>> output at every crash:
>>
>> --8<---------------cut here---------------start------------->8---
>> Warning: Unable to load any usable ISO8059 font
>> ERROR: Aborting: no font found
>> --8<---------------cut here---------------end--------------->8---
>>
>> Apparently there is a patch which might fix that problem, available
>> here: https://lists.gnu.org/archive/html/guix-devel/2016-12/msg00165.html
>>
>> Maxim
>
> Good catch, it was just forgotten. Would you like to work on the suggestions
> Ludovic gave John? It's unlikely that John will work on them after John
> more-or-less left Guix.
Yes, it's on my TODO! Thanks for the reminder :)
Maxim
next prev parent reply other threads:[~2017-11-29 12:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 13:18 bug#24279: Bug in xterm and/or fontconfig John Darrington
2016-08-22 8:36 ` Alex Kost
2016-08-22 13:41 ` John Darrington
2016-08-22 18:39 ` Alex Kost
2016-08-28 14:45 ` Ludovic Courtès
2016-08-29 9:20 ` Alex Kost
2016-09-01 21:03 ` Mark H Weaver
2016-09-02 9:02 ` Alex Kost
2017-05-04 6:54 ` bug#24279: XTerm menu doesn't work (no font found error) Maxim Cournoyer
2017-11-28 12:41 ` ng0
2017-11-29 12:56 ` Maxim Cournoyer [this message]
2017-11-28 7:14 ` bug#24279: Bug in xterm and/or fontconfig Oleg Pykhalov
2017-11-29 10:01 ` Alex Kost
2017-11-30 9:42 ` Ludovic Courtès
2017-12-01 2:10 ` Maxim Cournoyer
2017-12-01 15:01 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu8xp7jj.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=24279@debbugs.gnu.org \
--cc=ng0@n0.is \
/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/guix.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).