Comment 3 for bug 1442405

On Fri, Apr 10, 2015 at 01:40:13AM -0000, Andy Lutomirski wrote:
> The official docs [1] say to do:

Dangling reference here; I don't know which doc you got this from.

> --- cut here ---
> # ttyS0 - getty
> #
> # This service maintains a getty on ttyS0 from the point the system is
> # started until it is shut down again.
>
> start on stopped rc or RUNLEVEL=[12345]

That is certainly incorrect. There should be no 'or' here.

> --- cut here ---
> # ttyS1 - getty
> #
> # This service maintains a getty on ttyS1 from the point the system is
> # started until it is shut down again.

> start on stopped rc RUNLEVEL=[2345] and (
> not-container or
> container CONTAINER=lxc or
> container CONTAINER=lxc-libvirt)

Your version does look correct.

> But this isn't a race -- IMO it really is a bug, if only a documentation
> bug perhaps. plymouth-stop.conf has:

> start on (starting gdm
> or starting kdm
> or starting xdm
> or starting lxdm
> or starting lightdm
> or starting uxlaunch
> or starting ubiquity
> or starting oem-config
> or stopped rc RUNLEVEL=[2345]
> or starting rcS
> or starting mountall-shell)

> It never runs at all on a non-graphical system.

Why do you say that it doesn't? The 'stopped rc RUNLEVEL=2' event, when
emitted, should trigger this job to be called. This is the same event that
triggers the start of your tty job, so it certainly is being emitted.

You definitely don't have any of the gdm, lightdm, ubiquity, or oem-config
services installed, correct?

Do you have a /var/log/upstart/plymouth-stop.log on the affected system? If
so, please attach it.

Please also show the output of 'sudo initctl list | grep plymouth' on this
system.

> Please reopen.

The bug is not closed.