First, disabling plymouth is not supported; plymouth is necessary for arbitrating boot-time I/O. If you have a reason to disable plymouth, you should disable this job as well.
Second, adding 'and' conditions has a tendency to cause upstart deadlocks. I don't see that this would come into play in this instance, but if we can avoid adding an 'and' here, we probably should. Third, in reading the code, it doesn't look like a 'started' event will be emitted at all for plymouth if plymouth runs from the initramfs, so any users of cryptsetup would lose the boot logging entirely as a result of this change. So I think the job is written correctly as-is and shouldn't be changed. -- plymouth-log upstart should start only if plymouth starts https://bugs.launchpad.net/bugs/534126 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
