Bug 726913

Description of problem:

An attempt to boot to level 3, which I was not trying for quite a while, instead of 'login: ' prompt on a text console brought me a blue screen with "Text Mode Setup Utility 1.19.11 ...." at the top and somewhat garbled but still readable a dialog box with a number of possible setup tools.  That in itself would be possibly not that bad, although with a remote access it could have some unpleasant side-effects, if not this detail that even if it was possible to pick up various options and choose "Run Tool" and "Quit" actions otherwise this did not seem to have any other effect (like really running something or leaving this tool).  It was also impossible to get a login prompt on another console.

A machine did boot as a over a network login was available.  Checking processes showed that ps output ended up with:
....
root      1362  0.0  0.1 120032  2080 tty1     Ss+  12:13   0:00 setup
root      1366  0.0  0.0  15272   728 ?        Ss   12:13   0:00 /bin/plymouth --wait

and that was sitting there.

Version-Release number of selected component (if applicable):
systemd-30-1.fc16

How reproducible:
On the first three attempts while trying with different kernels, just to make sure that this is not particular kernel/initrd dependent, the system was behaving like described above.  On the last attempt, when I was trying to figure out how to get out of this setup without just killing it from "outside", something ended up with replacing that screen with a plymouth splash.  Unfortunately I do not know really why that happened and that splash prevented me from seeing any possible information.  I let that sit for a while while I was trying to check if I can find anything informative.  Subsequent reboots to level 3 so far to not attempt to run 'setup' anymore.

Expected results:
Not a bad attempt to run a text setup on a machine long time in use.
As a bare minimum a "Quit" button in a text 'setup' which does that.

Additional info:
Booting to level 5, if anything else is not broken at the moment, was not a problem on a test machine.  I cannot tell when really an issue with booting
to level 3 showed up as I do not remember when I was doing that last time.

This box is updated all the time to the current rawhide so "the firstboot" happened on it in an ancient prehistory.

I am not entirely sure where is the bug but systemd is currently responsible for a startup sequence.