Red Hat Bugzilla – Bug 230920
Update creates unusable xfs config
Last modified: 2008-03-26 12:22:43 EDT
Description of problem:
After running "yum update", xfs configuration was ruined. Presumably
fonts-japanese added ":unscaled". Current xfs stops working if it
Version-Release number of selected component (if applicable):
Steps to Reproduce:
0. Use a config like the attached
1. Update from a previous verion of fonts-japanese
Duplicate entries for font paths, ":unscaled" is present.
The xfs starts and seems to work, but X aborts with ``unable to open
Created attachment 149213 [details]
Broken config after update
You've missed comma after line 17. BTW :unscaled is automatically added by
chkfontpath though, have you modifed your xfs config file by the hand? I'm quite
not sure why it happened anyway.
s/it/missing :unscaled for 75dpi and 100dpi as well/
I see. The "unscaled:" was not relevant. The font "cursor" got missing
because of the missing comma.
I do not edit anything by hand as a rule. I think that some other program
modifying the configuration made the paths flush with the left side at
some point. Then, the post-installation of fonts-japanese was confused
Hmm, then there are nothing else I can do on fonts-japanese. adding the font
path into xfs config really relies on chkfontpath and have never done any
Should I reassign this to chkfontpath? or what exactly is "some other program"?
Yes, please reassign as appropriate. I'm wholly ignorant about what program
actually edits the file.
Ok. if you can provide any info when it happened and what packages were updated,
it would be helpful. AFAIK chkfontpath is only one to update xfs's config file
as the program. so I'm reassigning this to chkfontpath so far.
We no longer use chkfontpath or xfs, font packages are now required to drop
symlinks in fontpath.d. Which fonts-japanese does, so I'm closing this. Thanks
to everybody involved ;)