Robbie just pointed me as this bug, so I'm glad to see it's got a fix.
Just wanted to confirm that while some of our issues in Lucid *were* plymouth/X interaction issues, we discovered that many of them were - as debugged above - caused by the isig flag being reapplied to /dev/console.
We had to patch a few different things, including Upstart, which all felt they had the right to reset /dev/console. If apache is doing "stty sane", that is almost certainly the culprit - anything doing that is going to cause issues because the console is *not* supposed to ever be sane (it's graphical at all points)
Robbie just pointed me as this bug, so I'm glad to see it's got a fix.
Just wanted to confirm that while some of our issues in Lucid *were* plymouth/X interaction issues, we discovered that many of them were - as debugged above - caused by the isig flag being reapplied to /dev/console.
We had to patch a few different things, including Upstart, which all felt they had the right to reset /dev/console. If apache is doing "stty sane", that is almost certainly the culprit - anything doing that is going to cause issues because the console is *not* supposed to ever be sane (it's graphical at all points)