On Tue, Apr 24, 2012 at 06:11:48PM -0000, Scott James Remnant wrote: > The correct upstream fix obviously would be to conditionally set up the > system console in some manner, dependent on whether or not it's already > "owned" by a running process or whether init is truly the first process > to be run.
Sounds like the correct fix would indeed be to check whether the console is locked as James suggested, and do the setup only if it's not. And for an Ubuntu-specific fix, it seems it would still be correct to treat the console as owned by plymouth. Thanks for the insight, Scott. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876626 Title: Unlocking the second crypto disk (/home) echos password on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/876626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
