Peter: the issue here is that this "error" is expected: on the very first update after boot, dnsmasq will get spawned during the update phase, but is likely not going to be ready yet -- the update will "fail" and fallback to writing the dns names directly to resolv.conf, instead of writing 127.0.1.1 and using dnsmasq. Then when dnsmasq appears on the bus the update is re-tried, and should succeed.
There's no indication of anythign wrong in the response you've given or the log excerpt. Could you have run chattr +i on /etc/resolv.conf? See what 'sudo lsattr /etc/resolv.conf' returns. Otherwise, make sure it's properly a symlink to /run/resolvconf/resolv.conf, which should contain the proper dns data already. If all this fails, then we'll need to look at NetworkManager debug logs (http://wiki.ubuntu.com/DebuggingNetworkManager) because something else might be failing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048430 Title: "dnsmasq not available on the bus" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1048430/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
