the problem here is that if networkmanager is already running and hasnt
found a resolvconf managed resolv.conf (or resolvconf isnt installed)
and you then install resolvconf package, networkmanager will not notice
that on shutdown and just think it should wipe the resolv.conf file.

so stopping NM before installing (or dpkg-reconfigure resolvconf to fix
this post-mortem) does the trick. So the bug is that NM doesn't
reconsider his idea to not-use resolvconf on shutdown. I will check if
we can do this better.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

** Changed in: network-manager (Ubuntu)
       Status: Confirmed => Triaged

** Changed in: network-manager (Ubuntu)
     Assignee: (unassigned) => Alexander Sack (asac)

** Summary changed:

- kubuntu 8.10 - Network Manager 0.7 - DHCP/resolvconf Problem
+ Network Manager 0.7 doesn't use resolvconf on shutdown if it didn't use it on 
startup - this causes /etc/resolv.conf link to be wiped on shutdown

** Summary changed:

- Network Manager 0.7 doesn't use resolvconf on shutdown if it didn't use it on 
startup - this causes /etc/resolv.conf link to be wiped on shutdown
+ Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it 
didn't use it to add that information - this causes /etc/resolv.conf link to be 
wiped on shutdown and makes migrating a running system to resolvconf tricky

** Summary changed:

- Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it 
didn't use it to add that information - this causes /etc/resolv.conf link to be 
wiped on shutdown and makes migrating a running system to resolvconf tricky
+ Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it 
didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf 
link

-- 
Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it 
didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf 
link
https://bugs.launchpad.net/bugs/324233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to