package resolvconf 1.44ubuntu1 failed to install/upgrade:

[Lucky75]

Binary package hint: resolvconf

So, I was trying to upgrade from Januty to Karmic, but I got an error about knetworkmanager not found or downloaded, and then resolvconf failed to upgrade so the upgrade was aborted.

Any suggestions?

ProblemType: Package
Architecture: i386
Date: Sun Nov 8 06:33:55 2009
DistroRelease: Ubuntu 9.10
ErrorMessage:
 ErrorMessage: subprocess installed post-installation script returned error exit status 1
NonfreeKernelModules: nvidia
Package: resolvconf 1.44ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
SourcePackage: resolvconf
Title: package resolvconf 1.44ubuntu1 failed to install/upgrade:
Uname: Linux 2.6.28-16-generic i686

[Lucky75 (lucky7-500)]

To add..

I seem to have set "chattr +i" on my resolv.conf. Removing that allowed me to at least do an upgrade, but I'm worried that the full install of 9.10 didn't fully complete. It seems to have partially worked though.

Anyone have suggestions for ensuring that my upgrade to 9.10 isn't broken?

Thanks

[Mathieu Trudel-Lapierre (cyphermox)]

Lucky75,

You should be able to ensure that everything is installed as it should by issuing the 'sudo apt-get -f install' and 'sudo dpkg --configure -a'.

When you mean you set "chattr +i" on resolv.conf, is this because you had explicitly run this command at some point, or something that is the result of other packages/changes on the system?

[Lucky75 (lucky7-500)]

Thanks, I ended up just doing a full reinstall of everything. I had originally made it immutable to fix some problem I was having, but I can't remember what it was. It was an explicit change though, so nothing that needs to be worried about. It did cause some issues when doing an upgrade though. Thanks for the response.

[Simon Huerlimann (huerlisi)]

As this has been triggered by some explicit, quite special change, it probably won't get a fix.

Closing this bug, for now. Thank you for reporting, anyway!

[Simon Huerlimann (huerlisi)]

Mmh, while doing some more bug triaging on this package, there seem to be another report having trouble with an immutable resolv.conf. While this bug has 2 affected, the other one brings in 6. So looks like this is a real issue for some.

Will re-open but mark as duplicate.