How to debug “Fontconfig error: No writable cache directories” as the console output of font-manager?

Ask Question

Asked 5 months ago

Modified 5 months ago

Viewed 1k times

Starting

font-manager

as a regular user from a console (regardless of the presence or the contents of /usr/local/share/fonts) prints four messages

Fontconfig error: No writable cache directories

on the console. /var/log/syslog and dmesg show nothing interesting, and running

fc-cache -r && fc-cache -fv && dpkg-reconfigure fontconfig fontconfig-cache font-manager

as root didn't help.

How to debug this error?

asked Feb 16 at 15:59

AlMa1r

1499 bronze badges

Have you tried sudo font-manager?
– DrMoishe Pippik
Commented Feb 16 at 16:54
@DrMoishePippik Upon sudo font-manager, these error messages don't appear. Are you implying that viewing fonts should be done as root?
– AlMa1r
Commented Feb 16 at 18:05
Font manager can do more than view fonts. Any app that can make system changes certainly should require higher privilege.
– DrMoishe Pippik
Commented Feb 18 at 0:34
@DrMoishePippik Then the error message is unactionable or has a wrong level of abstraction. Mildly put. (As for making system changes, elevated privileges should be asked only when necessary. Just viewing fonts, in my opinion, should not require them.)
– AlMa1r
Commented May 2 at 22:58

Add a comment |

0