I had this problem on one of my systems after upgrading to lucid - about 50% of boots left cups not running and nothing meaningful in the logs. It would always start manually. I have several other lucid systems that never encounter this problem.
I applied the circumvention from my own bug report https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/604283 (adding lo:0 to /etc/network/interfaces as described) and since then, the cups has started on the system 5 out 5 boots. If anyone has this problem, please try the same circumvention and update both bug reports with your observations. -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
