I also agree that this bug is important, and am treating it seriously. However, flip-flopping the upstart config will only bring back the real bug that this upload was meant to solve: that for users who *do* have a correctly configured /etc/network/interfaces, some services would fail to start at boot because upstart would try to start them before bringing up the lo interface.
The real bug here is that some users have broken /etc/network/interfaces that prevent the loopback interface from *ever* being brought up. We should not be relying on network manager to bring up the loopback interface; that's not a robust design, and the failures people are seeing here are a result of me not anticipating that users would have such configurations. So the correct fix (*not* a workaround) is to populate /etc/network/interfaces with the configuration for the loopback interface. Caution is needed when doing this automatically on package upgrade, however, so it will be a bit yet before I can have a fix ready to be pushed to karmic-proposed. (BTW, Scott, while I did mention to you I had seen a problem where rc had not been run on my system, this problem was not reproducible afterwards and doesn't seem to have coincided with the upstart change in lucid; so I don't think there's any evidence that this issue is an instance of bug #447654. Please correct me if I'm wrong.) -- upstart not starting init-scripts (event net-device-up IFACE=lo missing) https://bugs.launchpad.net/bugs/497299 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
