Bug 101680 - fontconfig/ is created in different directories
Summary: fontconfig/ is created in different directories
Alias: None
Product: fontconfig
Classification: Unclassified
Component: fc-cache (show other bugs)
Version: 2.11
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: fontconfig-bugs
QA Contact: Behdad Esfahbod
Depends on:
Reported: 2017-07-03 17:39 UTC by Victor Porton
Modified: 2018-08-20 21:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Victor Porton 2017-07-03 17:39:19 UTC
fontconfig/ directory is created in some directories (not in $HOME directory).

Debian Linux 9 "stretch".
Comment 1 Akira TAGOH 2017-07-04 02:32:39 UTC
Can you provide more information? where is it? when was it created? what did the debian maintainer say about it?
Comment 2 Victor Porton 2017-07-04 09:38:22 UTC
It was created in /home/porton/math/mybooks/volume-1-latex (where I hold LaTeX files of my book).

Maybe it was created when I ran LaTeX editor Kile.

I haven't asked a Debian maintainer, because I don't know which package to blame.
Comment 3 Akira TAGOH 2017-07-04 10:08:59 UTC
in that directory only? does it contain any files? what happens when you run your apps once removing that directory?

I guess... it was created to store the fontconfig cache files because there was *no* cache directory found and $XDG_CACHE_HOME was somehow set there by someone (maybe your apps or you). I don't even know why but there are nothing wrong on the behavior itself if my guess is correct. when the next step to take an action for you should be to blame your app (or you) why they override $XDG_CACHE_HOME instead of the standard location where is $HOME/.cache.
Comment 4 Victor Porton 2017-07-04 10:15:25 UTC
Yes it contained some binary cache files.

Nothing special happens when I remove that directory. But it is recreated by some app.

I have also:


$XDG_CACHE_HOME is unset
Comment 5 Akira TAGOH 2017-07-04 10:31:12 UTC
(In reply to Victor Porton from comment #4)
> /home/porton/.cache/fontconfig

This one is correct. anyway, I can't say too much until you can reprocude it. there are no such bugs so far unless there are misconfiguration in $XDG_CACHE_HOME or fonts.conf.
Comment 6 GitLab Migration User 2018-08-20 21:43:59 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/11.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.