From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
When rhgb is set to start on boot, all daemon start/stop messages show
up on vt8.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. go to vt1
2. press ctrl-alt-del
Actual Results: The "Shutting down <daemon> [ OK ]" messages do not
show. Switching to vt8 shows them.
Expected Results: All the messages should appear on the current
This is not that serious but it is annoying.
This also causes some confusion when rebooting/shutting down from
X/GDM. The user gets a black screen with nothing more that "Sending
all processes the TERM signal.." for a while, looking like the machine
has frozen. Then all the "[ OK ]" messages flash for a second and the
machine reboots/powers down.
Bug is still present in FC4. I'm not convinced this is rhgb-related as it
still seems to occur in FC4 when booting without rhgb.
Boot seems to leave vt8 as the console somehow. Logging in to vt1 at some
stage (and maybe issuing telinit or shutdown from there) returns things to
Sorry, it is rhgb related!
I checked the source and did some experimenting. rhgb has changed to enable a
smooth transition from graphical boot to login screen. It waits until the
display manager has started before exiting.
A side-effect of this is that X deems vt8 to be the terminal from which is was
started, so this is where it returns on exit. Shutdown/runlevel change messages
then go to vt8. (I'm not sure why the screen is blank before pressing a key.
To return messages to vt1, I editied /etc/X11/prefdm, adding:
after the lines shutting down rhgb. However, this will probably make the text
login visible between graphical boot and login as was the case in FC1 and 2.
I'm not sure if this is a "bug". It would be nice if messages were visible on
shutdown instead of just a blank screen - can something be done to make them
show up without a key-press, even if they are one vt8? Of course, a graphical
shutdown is another alternative.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Highly suspect that this was fixed in rhgb-0.16.4-3, as the changelog reads:
"kill rhgb before gdm starts to prevent weird vt switching
behavior (bug 211848)"
Definitely seems to address Comment 3. Bug 211848, however, is a protected bug
that I am not authorized to see.