all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: hmk <hmk42@posteo.de>
Cc: 30435@debbugs.gnu.org, guix-devel@gnu.org
Subject: bug#30435: libreoffice: Fonts don't show up after install
Date: Thu, 02 Apr 2020 11:09:34 +0200	[thread overview]
Message-ID: <87a73ui78x.fsf__28898.7157562346$1585818614$gmane$org@ambrevar.xyz> (raw)
In-Reply-To: <bad1fc034ed4a0a4dbf14f74d431b7ae@posteo.de> (hmk's message of "Mon, 12 Feb 2018 12:06:00 +0100")

I can reproduce this on guix ce226e9d8d52d2530f057f2000d36c0d55380ade.

But libreoffice is not the only victim: it seems that most applications
fail to see the fonts installed in the user profile (on Guix System).
Emacs is one example.

Running

--8<---------------cut here---------------start------------->8---
fc-cache -fv
--8<---------------cut here---------------end--------------->8---

fixes the issue.

Should we run this command in a profile hook?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

  reply	other threads:[~2020-04-02  9:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 11:06 bug#30435: libreoffice: Fonts don't show up after install hmk
2020-04-02  9:09 ` Pierre Neidhardt [this message]
2020-04-02  9:09 ` Pierre Neidhardt
2020-04-02  9:19   ` Nicolò Balzarotti
2020-04-02  9:37     ` John Soo
2020-04-02  9:37     ` John Soo
2020-04-02 15:47     ` Ludovic Courtès
2020-04-02 15:47     ` Ludovic Courtès
2020-04-02  9:19   ` Nicolò Balzarotti
2020-04-02 15:46   ` Ludovic Courtès
2020-04-02 15:59     ` Pierre Neidhardt
2020-04-02 15:59     ` Pierre Neidhardt
2023-02-20 16:05     ` Maxim Cournoyer
2023-02-20 17:32       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-02-20 18:22         ` Maxim Cournoyer
2023-08-29  3:28           ` Maxim Cournoyer
2020-04-02 15:46   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87a73ui78x.fsf__28898.7157562346$1585818614$gmane$org@ambrevar.xyz' \
    --to=mail@ambrevar.xyz \
    --cc=30435@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=hmk42@posteo.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.