From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Pierre Neidhardt" <mail@ambrevar.xyz>,
30435@debbugs.gnu.org, guix-devel@gnu.org, hmk <hmk42@posteo.de>
Subject: Re: bug#30435: libreoffice: Fonts don't show up after install
Date: Mon, 20 Feb 2023 13:22:34 -0500 [thread overview]
Message-ID: <874jrgkxhx.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt56MJn=rXZTqvnjNb4dQGBXx55GoZM6i+zd+SswiSUP+pQ@mail.gmail.com> (Felix Lechner's message of "Mon, 20 Feb 2023 09:32:21 -0800")
Hi Felix,
Felix Lechner <felix.lechner@lease-up.com> writes:
> Hi,
>
> On Mon, Feb 20, 2023 at 8:06 AM Maxim Cournoyer
> <maxim.cournoyer@gmail.com> wrote:
>>
>> I haven't seen this problem in a long while, so I'm inclined to think
>> it's been resolved.
>
> I think I had that issue with a fresh install within the last year and
> based on advice in IRC (thanks nckx!) ran 'fc-cache -fv'.
OK, thanks for the information; let's leave this bug open then.
> For what it's worth, I believe Debian's packaging tools (in this case,
> Debhelper) detect changes to the font directories and add a font
> update hook to the package installation scripts. Since we do not have
> such scripts—and I am with Ludo' that it's probably a feature worth
> preserving—maybe our package manager could run the hook?
Another idea: modify fontconfig so that it never creates or uses cache.
Revisit later if it causes performance problems (I doubt it would).
--
Thanks,
Maxim
prev parent reply other threads:[~2023-02-20 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bad1fc034ed4a0a4dbf14f74d431b7ae@posteo.de>
2020-04-02 9:09 ` bug#30435: libreoffice: Fonts don't show up after install Pierre Neidhardt
2020-04-02 9:19 ` Nicolò Balzarotti
2020-04-02 9:37 ` John Soo
2020-04-02 15:47 ` Ludovic Courtès
2020-04-02 15:46 ` Ludovic Courtès
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 [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=874jrgkxhx.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=30435@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=guix-devel@gnu.org \
--cc=hmk42@posteo.de \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
/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).