Bug 5532 - gdm does not start
gdm does not start
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1999-10-04 18:49 EDT by Yil-Kyu Kang
Modified: 2008-05-01 11:37 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-11-02 11:09:19 EST
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 Yil-Kyu Kang 1999-10-04 18:49:13 EDT
during the installation process. If you selct graphical
login and customize button. It will start in runlevel 3
instead of runlevel 5.
Comment 1 Jay Turner 1999-10-20 12:36:59 EDT
This issue has been forwarded to a developer for further action.
Comment 2 Jay Turner 1999-10-20 12:41:59 EDT
*** Bug 6007 has been marked as a duplicate of this bug. ***

Using the graphical installer to do a full install, if
both "use graphical login" and "customize X" are selected,
the resulting /etc/inittab incorrectly sets the default
runlevel to 3 (instead of the intended runlevel 5).  If the
"customize X" button is not selected during the install,
the installer correctly sets a default runlevel 5.
Comment 3 Jay Turner 1999-10-20 12:45:59 EDT
*** Bug 5541 has been marked as a duplicate of this bug. ***

I checked the option to use graphical login during the
install, but my system was still set for runlevel 3.
Comment 4 Jay Turner 1999-11-02 11:08:59 EST
*** Bug 6627 has been marked as a duplicate of this bug. ***

Even though I selected the graphical login option during the
X configuration, the default run level in /etc/inittab was
set to 3, not 5.
Comment 5 Jay Turner 1999-11-02 11:09:59 EST
This issue is resolved with the latest errata and boot images
available at support.redhat.com/errata

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