Bug 15984 - X won't start after upgrade from 6.1 (xfs won't start)
X won't start after upgrade from 6.1 (xfs won't start)
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: XFree86 (Show other bugs)
7.0
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Preston Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-11 09:48 EDT by whampton
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:
Environment:
Last Closed: 2000-08-11 10:29:43 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)

  None (edit)
Description whampton 2000-08-11 09:48:33 EDT
After my aborted first install (no functional CD2), I restarted the upgrade
(see previous bugs).  The upgrade was from 6.1 to 7.0 beta.  The upgrade
finished without error.  After the upgrade and a reboot, the X server would
not start (runlevel 3, login as user, type startx).  The error was no
default font and could not contact "unix:/7200", i.e., the fontserver. 
Attempting to run /etc/rc.d/init.d/xfs start failed, it could not find the
file "functions" (I will need to copy this file from a working install).  

Note, the system had Corel Office 2K installed, which includes an
additional font server.
Comment 1 Bill Nottingham 2000-08-11 09:57:59 EDT
Are you *sure* there were no errors in the upgrade log?

It sounds like you have an incomplete initscripts install.
Comment 2 whampton 2000-08-11 10:29:39 EDT
I'll have to check the upgrade log (system is at another location).   I'll
reload initscripts and see if the problem goes away.  Prior to finishing the
run, it might be a good idea to run an rpm verify on a few things to validate
the install?
Comment 3 Preston Brown 2000-10-04 15:16:55 EDT
user must have had a screwed up initscripts, this problem is not present in RHL
7 final.

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