unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Alexandros Theodotou <alex@zrythm.org>, 41344@debbugs.gnu.org
Subject: bug#41344: Font broken in GUI application with guix pack
Date: Tue, 19 May 2020 20:11:20 +0200	[thread overview]
Message-ID: <87sgfvre0n.fsf@devup.no> (raw)
In-Reply-To: <5ab2b1ecc173c0114115f653f6476430a387df9e.camel@zrythm.org>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Alexandros Theodotou <alex@zrythm.org> writes:

> Hi,
>
> This is the command I ran to generate a pack:
> guix pack -RR -S /opt/zrythm/bin=bin -L . zrythm
>
> I then tried moving this pack to a VM running another distro
> (archlinux) and all letters are shown as boxes. I have asked other
> people to test it on other distros, including debian, and they reported
> the same issue.
>
> I am not exactly sure what is missing. Attaching a screenshot of what
> it looks like.

Can you try the patch posted at
<https://lists.gnu.org/archive/html/guix-devel/2020-05/msg00281.html> ?

When no fonts are installed in the common Guix profiles, applications
only "see" the font hard-coded into fontconfig, which happens to be
broken[*] since the recent 'core-updates' merge for any application
using Pango (such as GTK+).

[*] because fontconfig currently uses "gs-fonts", which are bitmap only,
and Pango no longer supports bitmap fonts[**]
[**] https://gitlab.gnome.org/GNOME/pango/issues/386

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      parent reply	other threads:[~2020-05-19 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17  4:05 bug#41344: Font broken in GUI application with guix pack Alexandros Theodotou
2020-05-19 13:43 ` Ludovic Courtès
2020-05-19 17:49   ` Alexandros Theodotou
2020-05-19 18:11 ` Marius Bakke [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

  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=87sgfvre0n.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=41344@debbugs.gnu.org \
    --cc=alex@zrythm.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.
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).