[Fontconfig] FcConfigEnableHome results in a lot of error messages

[Jerry Casiano]

It does help.

Not in terms of getting rid of the messages but in terms of being confident
in telling users they can ignore it and why if they happen to ask about it.

Thank you.


On Mon, Jan 31, 2022, 12:34 AM Akira TAGOH <akira at tagoh.org> wrote:

> On Sun, Jan 30, 2022 at 3:21 AM Jerry Casiano <jerrycasiano at gmail.com>
> wrote:
> >
> > Calling FcConfigEnableHome outputs a lot of error messages.
> >
> > Fontconfig error: No writable cache directories
> >
> > Is printed repeatedly.
> >
> > This wasn't the case previously, I'm wondering if this is a regression
> and I should file a report or if this might be caused by misuse on my part?
>
> I don't think we have changed anything around it. But I'm not even
> surprised you saw that error message. That is expected and likely to
> happen when you disable home. If caches are outdated, fontconfig will
> be going to update caches at the runtime. but you don't have any
> permissions to write caches, in this case.
>
> > Is there something I can do to prevent this?
>
> To avoid this situation, you may want to update caches with
> appropriate permissions if you don't want to store caches into the
> userspace directory.
>
> > It does not appear to cause any actual problems for the application, as
> far as I can tell anyway, and the application is typically not launched
> from a terminal so most users are unlikely to even notice but I would still
> like to prevent this if at all possible.
> >
>
> Not exactly. applications may see the outdated information of the
> fonts and/or missing some fonts newly added onto the system.
>
> Hope that helps,
> --
> Akira TAGOH
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig/attachments/20220131/7d3d95ea/attachment.htm>