Comment 35 for bug 497299

I have 32-bit ubuntu (I realise this isn't relevant, but I don't want people to get the idea it is a 64-bit problem).

The killer on my own system was bind - when it didn't start all my custom services on the system were completely wrecked. I am surprised bind9 wasn't mentioned by anyone else...

The system had been upgraded in place from jaunty to karmic and was apparently running well. After upgrading upstart, the system was wrecked at the next reboot. I was lucky that I could get to the machine to start the services manually - and VERY lucky someone had already posted this bug and the circumvention. I rolled back upstart and everything returned to normal.

I locked the back-level version so it wouldn't get accidentally upgraded again! I've re-instated the (automatically deleted) /etc/network/interfaces loopback definition. Can anyone say whether it is safe for me to upgrade upstart to 0.6.3-11 again, or are there other problems with this version?