touch-packages team mailing list archive

[Andy Lutomirski <1442405@xxxxxxxxxxxxxxxxxx>]

>> The official docs [1] say to do:
>
> Dangling reference here; I don't know which doc you got this from.

Whoops.

https://help.ubuntu.com/community/SerialConsoleHowto

> 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.

Sorry, I read that wrong.  You're right.

I do have lightdm installed, which is odd, since I don't have any of the
xorg packages installed.  I wonder if that's somehow related.  I don't
have a /var/log/upstart/plymouth-stop.log.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1442405

Title:
  plymouth locks console termios, breaking serial consoles

Status in plymouth package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  I have a more or less standard non-graphical Ubuntu 14.04 server
  installation.  I boot with console=ttyS1,115200, and I have
  /etc/init/ttyS1.conf that's more or less the same as all the standard
  /etc/init/ttyN.conf files.

  The serial console login doesn't work because plymouth seems to think
  it's showing its bootsplash and it locks the termios settings using
  TIOCSLCKTRMIOS.  This completely breaks /bin/login, which *requires*
  working buffered mode.

  I have no idea what mechanism is supposed to tell Plymouth to dismiss
  its splash screen when boot up is done, but it's clearly broken.  What
  gives?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1442405/+subscriptions