Seems weird to me, but I'm not against fixing that part of the
configuration provided it provably doesn't introduce regressions (delays
in booting up, waiting for the network). NM itself should be checking
that lo is up and has some code (disabled I think in Ubuntu) that tries
to bring lo up. Maybe it's worth checking if we want that to be done by
NM... but fixing the upstart condition looks like an easy way to tackle
the issue.
** Changed in: network-manager (Ubuntu Quantal)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Precise)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Quantal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993379
Title:
Network Manager starts before the loopback device is ready, leading to
dnsmasq not listening on any interface, breaking DNS resolution
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993379/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
