On Sun, Apr 10, 2011 at 11:30:49PM -0000, Stéphane Graber wrote: > I'm guessing it'd be better if apparmor could show its status then show > blacklist information on separate lines.
Indeed, though that's sort of separate from this bug I think. > Now, the real problem seems to be that both console output and upstart > information are being written to boot.log at the same time by plymouth. No - Plymouth is just taking what it finds on the console and writing it to boot.log. In the case where multiple processes are writing to the console at the same time and interleaving their output, it doesn't have enough information to pick this apart. The reason I asked Clint to file this on lsb in the first place is that, in order for Plymouth to have enough information to ensure that everything is displayed coherently, the lsb-base logging code needs to use the plymouth client program to send messages rather than just writing text to the console. That way, the messages are structured rather than just being a raw stream of text, and plymouth can ensure that they appear in the proper order on the console (it may or may not actually do this already, but at least it would be theoretically able to do so). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/752393 Title: lsb init scripts show line buffering problems on bootup -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
