This bug was fixed in the package network-manager - 0.9.4.0-0ubuntu5

---------------
network-manager (0.9.4.0-0ubuntu5) quantal; urgency=low

  * debian/network-manager.upstart: add "and static-network-up" to ensure the
    loopback device is really up before we start dnsmasq. (LP: #993379)
  * debian/patches/git_kernel_ipv6_default_route_77de91e.patch: avoid fighting
    with the kernel for what IPv6 default route should be set: let the kernel
    set his own, then add a new route with a different metric so that we can
    go back and remove it later. (LP: #988183)
  * debian/patches/nm-ip6-rs.patch: avoid disconnections due to RDNSS expiry,
    send a Router Sollicit to try and get new RDNSS data. (LP: #993571)
  * debian/patches/git_remove_ifpppstatsreq_6b64e4d.patch: remove the use of
    the ifpppstatsreq struct, which has been dropped in newer kernels: use
    ifreq and ppp_stats separately instead.
 -- Mathieu Trudel-Lapierre <mathieu...@ubuntu.com>   Wed, 23 May 2012 15:28:36 
-0400

** Changed in: network-manager (Ubuntu Quantal)
       Status: In Progress => Fix Released

-- 
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:
  Fix Released
Status in “network-manager” source package in Precise:
  Triaged
Status in “network-manager” source package in Quantal:
  Fix Released

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     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to