Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 100580

Summary: no pathname for local.conf fontconfig
Product: [Retired] Red Hat Linux Beta Reporter: Felipe Alfaro Solana <felipe_alfaro>
Component: fontconfigAssignee: Owen Taylor <otaylor>
Status: CLOSED WORKSFORME QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: beta1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-09-19 19:41:18 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 Felipe Alfaro Solana 2003-07-23 15:26:32 UTC
Description of problem: 
The configuration file "/etc/fonts/fonts.conf" references the "local.conf" file for 
additional configuration information, but does so without specifying a pathname. 
Thus, fontconfig is unable to locate the file and the resulting net effect is that any 
changes made to "/etc/fonts/local.conf" are ignored. 
 
I have fixed this by editing "/etc/fonts/fonts.conf" and modying the following lines: 
 
<!-- 
  Load local system customization file 
--> 
        <include ignore_missing="yes">local.conf</include> 
 
to look like this: 
 
<!-- 
  Load local system customization file 
--> 
        <include ignore_missing="yes">/etc/fonts/local.conf</include> 
 
Version-Release number of selected component (if applicable): 
fontconfig-2.2.1-4 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. Make sure fontconfig-2.2.1-4 is installed. 
2. Take a look at "/etc/fonts/fonts.conf" and make sure the file "local.conf" is 
specified with no associated pathname. 
3. Make a change to "/etc/fonts/local.conf" 
4. Restart X 
5. The changes won't have any effect until you perform the modification described 
above. 
     
Actual results: 
Modifications to "/etc/fonts/local.conf" are ignored due to a missing pathname. 
 
Expected results: 
"/etc/fonts/fonts.conf" should reference "local.conf" by using an absolute 
pathname. 
 
Additional info:

Comment 1 Owen Taylor 2003-09-19 19:41:18 UTC
Both reading the code and testing on my system confirm that 
/etc/fonts is used as a prefix for non-absolute filenames
in an <include> statement.

Not sure why it isnt' working for you.