wnettools.py does not interface with resolvconf correctly

Bug #1073706 reported by Thomas Hood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd (Debian)
Confirmed
Unknown
wicd (Ubuntu)
New
Undecided
Unassigned

Bug Description

If resolvconf is installed, wnettools.py uses "resolvconf -a" to add a nameserver information record. However, a grep through the code reveals that it nowhere removes that record (using "resolvconf -d"). This is a bug. When the program deconfigures the interface, or at the very least when it quits, it must delete the record that it earlier created. Otherwise this stale record remains in the system until reboot.

I am guessing that the reason that there is no "resolvconf -d" is that wicd-daemon.py backs up and restores /etc/resolv.conf and that this was thought to make it unnecessary to do "resolvconf -d". If my guess is right then please note that this is a bug. When resolvconf is installed, other software should never touch /etc/resolv.conf. At all. I will repeat that. Don't touch /etc/resolv.conf --- neither the symlink nor the contents of its target. In particular don't "restore" it. (And therefore don't "back it up", as there is no need to do so, since you won't be "restoring" it.) As just mentioned, the way for wicd to restore the original situation (as far as wicd is concerned) is to delete the resolvconf record that it created, using the "-d" option.

Changed in wicd (Debian):
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.