Bug 155349 - xfs initscript issuing errors at firstboot
xfs initscript issuing errors at firstboot
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: xorg-x11-xfs (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2005-04-19 09:33 EDT by Florian La Roche
Modified: 2008-06-14 10:07 EDT (History)
1 user (show)

See Also:
Fixed In Version: 6.8.2-31.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-14 10:07:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The error message from xfs initscript (745 bytes, patch)
2005-05-03 08:38 EDT, Ngo Than
no flags Details | Diff

  None (edit)
Description Florian La Roche 2005-04-19 09:33:57 EDT
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:
Comment 1 Mike A. Harris 2005-04-19 10:27:26 EDT
What warnings?
Comment 2 Mike A. Harris 2005-04-19 10:29:08 EDT
Also, what version of xorg-x11 is installed?
Comment 3 Florian La Roche 2005-04-19 11:12:36 EDT
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.

Comment 4 Mike A. Harris 2005-04-19 12:01:12 EDT
"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.
Comment 6 Ngo Than 2005-05-03 08:38:12 EDT
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.
Comment 7 Ngo Than 2005-05-03 08:40:03 EDT
the attached patch should fix this problem
Comment 8 Bill Nottingham 2005-05-20 23:34:44 EDT
fixed in 31.1/32.
Comment 9 Mike A. Harris 2005-05-24 06:39:18 EDT
Built in rawhide as 6.8.2-34
Comment 10 Florian La Roche 2005-10-16 16:05:36 EDT
This seems still to happen with current FC-development trees. Maybe the
patch from Than Ngo should still be applied?

Thanks,

Florian La Roche
Comment 12 Mike A. Harris 2006-02-05 17:14:05 EST
Fixed in CVS, and will appear in rawhide during the upcoming mass rebuild.

Note You need to log in before you can comment on or make changes to this bug.