From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] unknown: X11 apps break, have to manually run mkfontdir & mkfontscale
Date: Wed, 28 Sep 2022 04:14:24 +0200 [thread overview]
Message-ID: <20220928021424.50nPsPeukQ_Z3jMRGGuYDj6y0AeDFF1Qlt1fguYpju0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37565@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Closed issue by Veyrdite on void-packages repository
https://github.com/void-linux/void-packages/issues/37565
Description:
### System
* xuname: Void 5.15.45_1 x86_64 GenuineIntel uptodate rFFFFFFFFFFF
* package: unknown
### Problem
Today I ran xbps-install -Su and everything seemed fine until I restarted Xorg. Then several issues started occurring:
* i3bar displayed the wrong font
* urxvt wouldn't launch (it couldn't find my font)
* xfontsel wouldn't launch ("Warning: Unable to load any usable ISO8859 font")
Reinstalling encodings, font-misc-misc, fontconfig and xorg-fonts had no impact on the problem, even after restarting Xorg.
### Fix
As per https://old.reddit.com/r/voidlinux/comments/ubv7nc/getting_badname_named_color_or_font_does_not/ (I am NOT the op, but I had the same issue today and their fix worked)
```
# cd /usr/share/fonts/X11/misc
# mkfontdir
# mkfontscale
(now restart xorg, however you do that on your system)
```
prev parent reply other threads:[~2022-09-28 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 0:39 [ISSUE] " Veyrdite
2022-06-15 4:39 ` classabbyamp
2022-06-15 11:33 ` Veyrdite
2022-06-15 11:34 ` Veyrdite
2022-06-15 11:35 ` Veyrdite
2022-06-15 11:35 ` Veyrdite
2022-06-15 19:49 ` icp1994
2022-09-14 2:14 ` github-actions
2022-09-28 2:14 ` github-actions [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220928021424.50nPsPeukQ_Z3jMRGGuYDj6y0AeDFF1Qlt1fguYpju0@z \
--to=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).