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 Desktop
Packages, which is subscribed to network-manager in 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
Status in “network-manager” package in Ubuntu:
In Progress
Status in “network-manager” source package in Precise:
Triaged
Status in “network-manager” source package in Quantal:
In Progress
Bug description:
It's been reported by users on IRC that network-manager in some cases spawns
a dnsmasq process that doesn't listen on anything.
This only happens at boot time and disappears after reconnecting.
The problem was tracked down to network-manager.conf triggering before
the loopback interface is ready.
Adding "and static-network-up" to the start condition ensures that
/etc/network/interfaces was parsed and all interfaces in there have
been ifup'ed, fixing the race.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
