@Toby: Thanks for your info. You didn't include the output of "cat /etc/resolv.conf" but I reckon it's the same as /etc/resolvconf/resolv.conf.d/original.
Based on the information we have so far I can only guess where the bug might be. It would be useful if we could rule out the possibility that the initial answer to the "resolvconf/linkify-resolvconf" debconf question was "false" and so I repeat what I said in comment #26: let's change the postinst so that it doesn't fiddle with the answer to linkify- resolvconf; instead let'd create a new question, resolvconf/linkify- done, which gets changed from "false" to "true" on linkification and whose value being "true" prevents linkification being repeated on subsequent postinst runs. Having said this, I think it's more probable that the initial answer to "linkify-resolvconf" was "true", that resolvconf.postinst correctly created the symlink and set the answer to "false", and that some other package subsequently replaced the symlink with a file. In Toby's case the finger of suspicion points toward the Cisco AnyConnect client. Anyone else happen to have the Cisco AnyConnect client installed? Is Toby or anyone else connecting to the VPN before resolvconf is (fully) installed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
