package resolvconf 1.63ubuntu11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I locked resolv.conf to prevent my DNS from changing by using the command:
sudo chattr +i /etc/resolv.conf
When I recieved the error initially i unlocked the file and tried running an update ... this did not resolve the problem. Since this file is only a config file, should I have locked it in the first place to prevent further edits?
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: resolvconf 1.63ubuntu11
ProcVersionSign
Uname: Linux 3.2.0-24-generic i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Tue May 1 09:25:26 2012
DpkgHistoryLog:
Start-Date: 2012-05-01 09:24:57
Commandline: apt-get upgrade
Upgrade: smbclient:i386 (3.6.3-2ubuntu2, 3.6.3-2ubuntu2.1), libsmbclient:i386 (3.6.3-2ubuntu2, 3.6.3-2ubuntu2.1), unity-scope-
DuplicateSignature:
Setting up resolvconf (1.63ubuntu11) ...
resolvconf.
dpkg: error processing resolvconf (--configure):
subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitec
SourcePackage: resolvconf
Title: package resolvconf 1.63ubuntu11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago)
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #989585, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.