Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 2840 - X Font Server failure.
X Font Server failure.
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-05-15 13:38 EDT by aeon
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-05-19 11:30:18 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 aeon 1999-05-15 13:38:33 EDT
The X Font Server (xfs) does not start up properly under the
SysV init scripts and must be started manually in order to
get X up and running.

Under the SysV init scripts, /etc/rc.d/init.d/xfs is used to
start `xfs'.  This script calls daemon() in
/etc/rc.d/init.d/functions to actually start the `xfs'
daemon.  This function executes the command:

    nice -n $nicelevel initlog $INITLOG_ARGS -c "su xfs -c
xfs -s /bin/sh"

to attempt a startup.  This command succeeds, unfortunately,
at the basic level.  The command

    su xfs -c xfs -s /bin/sh

will succeed without actually starting `xfs'.  I have to

    su xfs

in order to get the command to run.  Perhaps this is an
error in /etc/passwd where the default shell is /bin/false
(not likely) or that the home directory (configuration
directory) is listed as /etc/X11/xfs which does not exist on
my system (the most likely cause).

I did the "upgrade" path from 5.2 but was not previously
running `xfs' (why I need to run it now is a mystery).
Comment 1 Jay Turner 1999-05-19 11:31:59 EDT
Have no trouble getting xfs to start automatically here in the office
on 6.0 systems.

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