Red Hat Bugzilla – Bug 195475
[RHEL4] rhgb should kill itself before letting gdm start
Last modified: 2010-10-22 01:10:18 EDT
Description of problem:
When going from gdm or a VT and changing to runlevel 3 we are sent to V8 where
the various service are shutdown. Since there is no getty running on VT8, in
order to get to a functional console you have to use Alt + Fn. To the layman it
appears as though the console is hung.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log into gdm or a VT, execute 'init 3'
2. We are sent to VT8 where the various services are shutdown.
3. VT8 has no getty running on it so it appears hung. Alt + Fn is required to
get to a usable console.
We are sent to VT8 where no getty is running.
Return to VT 5 or what ever VT we executed the 'init 3' from. Or just sent to a
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
there ended up being another component to this fix. Namely, rhgb needed to
waitpid() on the x server before exiting and the X server needed to block on the
vt change before exiting (with a VT_WAITACTIVE ioctl)
I'll clone this bug for the X half.
For reference, the X half of this is filed as bug 223074
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.