[Bug 346013] Re: [jaunty amd64] autoconf fails to incporate NetworkManager-supplied dynamic data

Alois Hammer aloishammer at casearmour.net
Wed May 6 03:26:30 UTC 2009


I did eventually get resolvconf and NM working together, at the same
time, on the laptop (I didn't and don't have time to worry about the
desktop)-- but in my quest, it was clear that resolvconf had never been
working or configured in the first place.

Unfortunately, I have no idea what the actual fix was.  It eventually
started working sometime after I started [un/re]installing both packages
at various times, with and without running dpkg-reconfigure.
Apparently, all the cursing, shaking, and waving the bones over the
laptop jarred something loose, software-wise.  At this point, I'd just
appreciate a confirmation that resolvconf is the package equivalent of a
null loop; that's certainly how it appears here.

(And an explanation and fix for NM's insistence on acquiring an IP,
immediately discarding it, and finally holding on to an IP on the second
try.  Reproducible on two radically different networks with radically
different infrastructure (Windows at work, dhcpd on Gentoo here at
home); the only commonality is autoneg 1000FDX on both.)

-- 
[jaunty amd64] autoconf fails to incporate NetworkManager-supplied dynamic data
https://bugs.launchpad.net/bugs/346013
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs




More information about the universe-bugs mailing list