From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461) Description of problem: When starting xfs via services xfs start, get error message that fonts.dir is bad/missing. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Upgrade system from 7.2 with updates to 7.2.90 2.service xfs start 3. Actual Results: Get error message that fonts.dir bad/missing Expected Results: xfs should start error free Additional info: This is from a 7.2 install w/updates, no extra XFree86 packages. Then updated to 7.2.90. I commented out the two chmod lines for the fonts.dir and that stops it from looking. I've attached my xfs script file.
Created attachment 45182 [details] xfs script, lines causing the problem are around 201 and 206
Hmm. Odd. Could you stop xfs, then uncomment those lines, and add a line to the top of the xfs initscript right underr the umask line that says: set -vx then start xfs back up with: service xfs start &> xfsinit.log Then attach the resultant log file for me to ponder. Thanks Mike.
Created attachment 46160 [details] xfs start log, search for "attributes" [runlevel 3, X installed but no configured]
*** Bug 59972 has been marked as a duplicate of this bug. ***
*** Bug 60232 has been marked as a duplicate of this bug. ***
Please try the XFree86-4.2.0-6.39 package from rawhide and let me know if the problem goes away or not.
Tested with beta2 and recieved expected behavior. Please test again with beta2.
Agree. Appears to be fixed in beta 2. Will let mike close bug if he agrees.
Don't know about the XFree packages in beta 2, as I had problems with that version for voodoo3. But the ones in rawhide fixed that and don't see any problems with the fonts.dir so I'll close it as rawhide.