Red Hat Bugzilla – Bug 89540
Upgrading from RH 7.2 to RH 8.0 , causes gdm to hang.
Last modified: 2007-04-18 12:53:16 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: When using RH 7.2, a system restart would go throught the normal boot up process, associated with run level 5 and eventually bring the user to the GUI login screen. This login screen allowed the user to enter his name and password and select a session. When i upgraded to RH 8.0, and when i reboot the system, it goes through the nomal process again associated with run level 5, but after executing all the initialization scripts in /etc/rc.d/rc5.d, it goes on to execute a number of tty's and executes prefdm (which in turn executes gdm) which hangs.. I could not fins any suitable error in any of my log files.. Version-Release number of selected component (if applicable): gdm-2.4.0.7-13 How reproducible: Always Steps to Reproduce: 1.Upgrade RH 7.2 with RH 8.0 2.Reboot the system after the upgrade is finished. 3. Actual Results: The System hangs at the console. I have to presss CNTL^C, twice to get to the console.. No GUI login screen is displayed. Expected Results: The GUI login screen should have been displayed. Additional info:
What you are describing is a "problem requiring technical support" rather than a bug report. There might actually be a bug somewhere, but it isn't clear that there is one any more than it could simply be some misconfiguration of some kind. Also, gdm is not part of XFree86, it is part of GNOME. Unless there is a specific actual bug being reported, there isn't anything really that can be investigated. The only thing that I can think of off the top of my mind, is if you were using unsupported video drivers, such as Nvidia or ATI binary drivers prior to upgrading. That would leave X configured to use drivers that don't work with the new X, and would be an unsupported configuration, rather a tech support issue than a bug. I recommend joining our mailing lists and getting some technical support on the issue, narrow down the problem and if it turns out to actually be a defineable bug, then reopen this report with the details.