Ok. Actually, I realize now that since you ran 'dpkg-reconfigure' to fix your system, the debconf-show output is no longer useful for debugging here.
My best guess is that you had debconf configured in a way that you were asked whether to add the symlink (not shown by default), and you chose "no" (not the default). But there's no way to know for sure. I don't think there's any actionable bug here. If we get further reports of this issue we can investigate further, but I currently don't see any other way that this could have happened on upgrade except by a user override of the defaults. -- 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: resolv.conf not populated because /etc/resolv.conf symlink was not created 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
