[Bug 1442405] Re: plymouth locks console termios, breaking serial consoles
Steve Langasek
steve.langasek at canonical.com
Fri Apr 10 01:06:27 UTC 2015
> I have /etc/init/ttyS1.conf that's more or less the same as all the standard /etc/init/ttyN.conf files.
What does "more or less the same" mean? What is the exact content of this file?
The /etc/init/ttyN.conf files are *not* all the same, precisely because
plymouth and tty1 conflict with each other in the graphical VT case.
The answer to the question, "what is supposed to tell pymouth to dismiss
its splash screen", is /etc/init/plymouth-stop.conf. Your
/etc/init/ttyS1.conf probably has a race with this upstart job.
** Changed in: plymouth (Ubuntu)
Status: New => Incomplete
** Changed in: upstart (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth 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
More information about the foundations-bugs
mailing list