Bug 682785

This should be working actually. Probably some weird issue with interfacing with Plymouth.

Are you testing this with or without Plymouth? Do you have "rhgb" on the kernel cmdline? Or rd_NO_PLYMOUTH?

That is with plymouth-0.8.4-0.20110304.1.fc15.i686 and rhgb. I see the plymouth KMS progress animation and then just a flashing cursor.

I guess I will see the same issue with runlevel "3" but be able to ssh to the machine and poke around. Anything particular to look for?

Hmm, this works fine here...

If you wait 3mins, for ply to timeout, does it work then? do you get a prompt then?

if you boot with "rd_NO_PLYMOUTH", does that help?

In runlevel 3 I also just see a cursor and no prompt.

ssh and ps shows that no plymouth is running - but it also shows that agetty is  running on tty1-6.

Waiting for 3 minutes makes no difference.

rpm -qV systemd systemd-units shows noting.

HOWEVER, in runlevel 3 I can switch to other VTs and get a login prompt - and I can't find the empty screen on any other VT. In runlevel 1 and s there are no such other VTs. So it seems the problem could be something related to enabling/controlling the default VT?

With rd_NO_PLYMOUTH instead of rhgb it works as expected in runlevel 1.

The system is fully updated to f15 updates-testing but kernel-PAE-2.6.38-0.rc7.git4.1.fc15.i686 .

(In reply to comment #0)
> When adding 1 or s to the boot kernel options I would expect to get something
> similar to the old runlevel 1 or singleuser mode, but the ttys are completely
> blank. The only option I have found is ctrl-alt-del for rebooting. 

Having exactly the same issue (see BZ 689090) with systemd-20-1.fc15.x86_64

> 
> If these options no longer are available I would expect some kind of visible
> error message or default behaviour.
> 
> As mentioned on Bug 682285 the ttys works fine in "runlevel 5".
> 
> systemd-19-1.fc15.i686

(In reply to comment #3)
> Hmm, this works fine here...
> 
> If you wait 3mins, for ply to timeout, does it work then? do you get a prompt
> then?
> 
> if you boot with "rd_NO_PLYMOUTH", does that help?

Seems not to be a global workaround. Omitting RHGB or using rd_NO_PLYMOUTH  does not help for me.

(In reply to comment #4)
> In runlevel 3 I also just see a cursor and no prompt.
> 
> ssh and ps shows that no plymouth is running - but it also shows that agetty is
>  running on tty1-6.

So an agetty is running on tty1 in runlevel 3, but when you switch to VT1 you do not see a prompt and the VT does not react to your keypresses?

VT2-6 work fine however?

(In reply to comment #4)
> In runlevel 3 I also just see a cursor and no prompt.

I cannot confirm this: I had this problem too, but in the meanwhile I got rid from this after having applied all updates: booting into runlevel 3 is OK for me!

Joachim Backes

> 
> ssh and ps shows that no plymouth is running - but it also shows that agetty is
>  running on tty1-6.
> 
> Waiting for 3 minutes makes no difference.
> 
> rpm -qV systemd systemd-units shows noting.
> 
> HOWEVER, in runlevel 3 I can switch to other VTs and get a login prompt - and I
> can't find the empty screen on any other VT. In runlevel 1 and s there are no
> such other VTs. So it seems the problem could be something related to
> enabling/controlling the default VT?
> 
> With rd_NO_PLYMOUTH instead of rhgb it works as expected in runlevel 1.
> 
> The system is fully updated to f15 updates-testing but
> kernel-PAE-2.6.38-0.rc7.git4.1.fc15.i686 .

Mads, is it possible you are simply running into 688661?

Mads, if there is no other problem left open with systemd 23 but 688661, are you OK if I close the bug and we track things there?

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Is this still a problem or can this bug be closed?

Closing this. 

This probably was fixed between 20 <-> 24 release of systemd.