touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #69354
[Bug 1442405] Re: plymouth locks console termios, breaking serial consoles
> Correction: I didn't have lightdm, but I still had lightdm.conf. I did
> aptitude purge lightdm, and now everything's okay.
Aha, that explains. Plymouth assumes that if lightdm is installed, it
will handle the stopping of plymouth as part of the flicker-free
transition to X. If lightdm is removed but not purged, the upstart job
triggers, causing plymouth-stop to skip stopping plymouth itself; and
since the lightdm job won't actually start lightdm, nothing stops
plymouth.
So it seems the lightdm upstart job should be adjusted to also detect
the case where the package is purged, and call 'plymouth quit'.
** Package changed: plymouth (Ubuntu) => lightdm (Ubuntu)
** Changed in: lightdm (Ubuntu)
Status: Incomplete => Triaged
** Summary changed:
- plymouth locks console termios, breaking serial consoles
+ when lightdm is removed but not purged, plymouth is not stopped on boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1442405
Title:
when lightdm is removed but not purged, plymouth is not stopped on
boot
Status in lightdm package in Ubuntu:
Triaged
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/lightdm/+bug/1442405/+subscriptions
References