From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: John Darrington <john@darrington.wattle.id.au>, 24279@debbugs.gnu.org
Subject: bug#24279: Bug in xterm and/or fontconfig
Date: Thu, 30 Nov 2017 10:42:36 +0100 [thread overview]
Message-ID: <87inds6r1v.fsf@gnu.org> (raw)
In-Reply-To: <87shcyj2n9.fsf@gmail.com> (Oleg Pykhalov's message of "Tue, 28 Nov 2017 10:14:34 +0300")
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
Hi Oleg,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> John Darrington <john@darrington.wattle.id.au> writes:
>
>> In GuixSD:
>>
>> guix package -i xterm strace
>> strace xterm
>>
>> xterm starts as it should, however observe many failed calls similar to:
>> open("/gnu/store/b484nvn9nnr3ddclpz2fma9yxmimg2jj-fontconfig-2.11.94/lib/libXdmcp.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
>>
>>
>> Now in the xterm, hold down Ctrl and press any mouse button.
>> The xterm aborts with the following messages:
>> Warning: Unable to load any usable ISO8859 font
>> Error: Aborting: no font found
>
> I solved this issue by:
>
> - Install a font-misc-misc as Mike Hunt from Gentoo forum suggests¹:
>
> $ guix package -i font-misc-misc
>
> - From "(guix) Application Setup"²:
>
> $ xset +fp ~/.guix-profile/share/fonts/X11/misc
Oh, good to know!
We can also fix this once and for all with this patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 581 bytes --]
diff --git a/gnu/services/xorg.scm b/gnu/services/xorg.scm
index 0da3397da..8f285b29a 100644
--- a/gnu/services/xorg.scm
+++ b/gnu/services/xorg.scm
@@ -113,6 +113,8 @@
(file-append font-alias "/share/fonts/X11/100dpi")
(file-append font-alias "/share/fonts/X11/misc")
(file-append font-alias "/share/fonts/X11/cyrillic")
+ (file-append font-misc-misc ;default fonts for xterm
+ "/share/fonts/X11/misc")
(file-append font-adobe75dpi "/share/fonts/X11/75dpi")))
(define* (xorg-configuration-file #:key
[-- Attachment #3: Type: text/plain, Size: 162 bytes --]
That adds 4.1 MiB, but it saves user headaches, so I think it’s worth it.
I’ll go ahead and push that if there are no objections.
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-11-30 9:43 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
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 [this message]
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=87inds6r1v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24279@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
--cc=john@darrington.wattle.id.au \
/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).