Description of problem: Installing current FC-devel and booting the first time gives warnings. This patch resolves the issue: --- xfs.init 6 Apr 2005 23:11:51 -0000 1.19 +++ xfs.init 19 Apr 2005 13:29:47 -0000 @@ -36,7 +36,7 @@ buildfontlist() { # If fonts.dir does not exist, or if there are files in the # directory with a newer change time, regenerate fonts.dir, etc. # Using "-cnewer" here fixes bug #53737 - if [ ! -e fonts.dir -o -n "$(find . -maxdepth 1 -type f -cnewer fonts.dir -not -name 'fonts.cache*')" ]; then + if [ ! -e fonts.dir -o -n "$(find . -maxdepth 1 -type f -cnewer fonts.dir -not -name 'fonts.cache*' 2>/dev/null)" ]; then rm -f fonts.dir if ls | grep -iqs '\.ot[cf]$' ; then # Opentype fonts found, generate fonts.scale and fonts.dir Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What warnings?
Also, what version of xorg-x11 is installed?
This was newest FC-devel from last week, should also happen with newest FC4test release. Error message came from the xfs init script and from find. Must have been something like "file not found" or similar.
"newest from last week" doesn't mean anything. There was a bug in the script which we fixed and it's getting several dupes now. I am wondering if this is a dupe of that or something else. I want to know what the exact error and problem is, so I am sure that we're fixing it the best way. Redirecting to /dev/null, just hides the symptoms and may not fix the underlying problem depending on what the problem is. I can't make that judgement without more information though. I'll leave this here for now. Please supply the details if you can reproduce it again.
Created attachment 113960 [details] The error message from xfs initscript i can reproduce it every time on my machine by boot process The error message from xfs initscript: find: fonts.dir: No such file or directory The problem will always happen if the file fonts.dir does not exist in search directory.
the attached patch should fix this problem
fixed in 31.1/32.
Built in rawhide as 6.8.2-34
This seems still to happen with current FC-development trees. Maybe the patch from Than Ngo should still be applied? Thanks, Florian La Roche
Fixed in CVS, and will appear in rawhide during the upcoming mass rebuild.