I added the extra lines to /etc/network/interfaces to define a virtual interface lo:0 for the 127.0.1.1 address and have it auto-created early in kernel initialisation. I suspect this solution will apply to any services that need to listen on their own loopback interfaces.
I have just resolved a problem with cups not starting about 50% of the time on one of my lucid systems by implementing the circumvention described in https:/ /bugs.launchpad .net/ubuntu/ +source/ ifupdown/ +bug/604283.
I added the extra lines to /etc/network/ interfaces to define a virtual interface lo:0 for the 127.0.1.1 address and have it auto-created early in kernel initialisation. I suspect this solution will apply to any services that need to listen on their own loopback interfaces.