Bug 188170 - manpage of xfs shows wrong path for default config file
manpage of xfs shows wrong path for default config file
Product: Fedora
Classification: Fedora
Component: xorg-x11-xfs (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Kristian Høgsberg
Depends On:
  Show dependency treegraph
Reported: 2006-04-06 13:05 EDT by Thomas Steudten
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-25 19:06:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Thomas Steudten 2006-04-06 13:05:25 EDT
Description of problem:

From "man xfs"

       -config configuration_file
               Specifies  the configuration file the font server will use.  If
this parameter is not specified, the
               default file, /usr/X11R6/lib/X11/fs/config will be used.

But in FC5 the default file is /etc/X11/fs/config

Version-Release number of selected component (if applicable):

How reproducible:
man xfs

Steps to Reproduce:
1. man xfs 
2. see - config
Actual results:
man xfs shows: default file, /usr/X11R6/lib/X11/fs/config will be used.

Expected results:
man xfs shows: default file, /etc/X11/fs/config will be used.

Additional info:
Comment 1 Mike A. Harris 2006-06-06 05:26:17 EDT
This is something that really should be done by upstream IMHO.  At compile
time, the Makefiles should properly massage all paths in the manpages and
change them to what was specified via ./configure, rather than hard coding

If you file a bug report in X.Org bugzilla, it'll probably be fixed in the
next xfs release, and we can update to that.  Better than rolling a distro
hack to cart around.  ;)

Comment 2 Kristian Høgsberg 2006-09-25 19:06:38 EDT
This is now fixed upstream, when we rebase to newer xfs, we will get the fix. 
Closing this bug now.


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