desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

Indeed, resolvconf doesn't appear to work properly here either, so cases
with one or more devices unmanaged and some devices managed by NM fails
-- there's just no easy way to know what to do with resolv.conf in such
a case, even just saving on startup and restoring that file on stop is
kind of clumsy; this case is really supposed to be covered by resolvconf
-- I'll file a separate bug for that.

As for the case with NM installed (read: running) but not managing any
devices, it really shouldn't be clobbering /etc/resolv.conf.
Fortunately, that's relatively easy to fix. I'll upload an updated
package that covers this shortly.

-- 
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/862134

Title:
  Upgrade to oneiric wiped my resolv.conf for static interface

Status in “network-manager” package in Ubuntu:
  Triaged
Status in “network-manager” source package in Oneiric:
  Triaged

Bug description:
  I have a static eth0 (ie not managed by network manager). I upgraded
  from natty to oneiric and it wiped the resolv.conf file (but only on
  the second boot, bizarrely) leaving it looking like this:

  {{{
  # Generated by NetworkManager
  }}}

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/862134/+subscriptions