Your call, but I think this is going to make a lot of people's lives more difficult than they should be. Since filing the other bug about plymouth blocking boot a couple days ago, I've encountered a good 1/2 dozen people (on ubuntuforums and IRC) who had the same issue, and had removed plymouth to get the system to boot.
The workaround suggested this morning in IRC when I was debugging was to change the names of /etc/init/plymouth*.conf in order to get past it. If people do this to get past their plymouth problems, there's going to be all kinds of mess on systems. Is this standard ubuntu packaging policy? It would seem to me that the "correct" packaging hierarchy would be to make ubuntu-desktop depend on it, not e2fsprogs (which surely couldn't care less about plymouth being present.) Finally, Ian reported in IRC about 30 mins ago that the plymouth logo theme is still causing his boot to freeze. Only the text one works for him. (FWIW I booted with the text one also, not the logo one.) Thanks -- Package dependencies are too strong https://bugs.launchpad.net/bugs/553285 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
