Ubuntu
resolvconf package

package resolvconf 1.78ubuntu2 failed to install/upgrade: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')

Bug #1747104 reported by kiruthika
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

dpkg: error processing package ubuntu-minimal (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 resolvconf
 ubuntu-minimal

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 resolvconf: Configure
 ubuntu-minimal: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jan 31 10:03:58 2018
DpkgTerminalLog:
 dpkg: error processing package resolvconf (--configure):
  package resolvconf is not ready for configuration
  cannot configure (current status 'half-installed')
ErrorMessage: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-10-29 (96 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt 1.2.24
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: package resolvconf is not ready for configuration cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
kiruthika (kiruthi1012) wrote :
Revision history for this message
kiruthika (kiruthi1012) wrote :

i need to solve this problem

Revision history for this message
Steve Beattie (sbeattie) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.