Bug 480878

Summary: fc-cache says that it writes to /var/tmp/${localstatedir}/cache/${PACKAGE} and it does - literally
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: fontconfigAssignee: Behdad Esfahbod <behdad>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: behdad, fonts-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-29 22:00:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2009-01-21 02:08:18 UTC
Description of problem:

Look at this:

# fc-cache -v /usr/share/fonts/dejavu
/usr/share/fonts/dejavu: skipping, existing cache is valid: 42 fonts, 0 dirs
/var/tmp/${localstatedir}/cache/${PACKAGE}: cleaning cache directory
/root/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded

As a result I have a '/var/tmp/${localstatedir}/cache/${PACKAGE}/' directory, full of newly created cache files, but in /var/cache/fontconfig/ the newest
file is from 2009-01-09. That with three "liberation-fonts*" packages just
installed by yum.

Version-Release number of selected component (if applicable):
fontconfig-2.6.91-1.git.64.g9feaf34.fc11

How reproducible:
always