package resolvconf 1.78ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1678677 reported by Paul Rusu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
New
Undecided
Unassigned

Bug Description

Any sudo apt-get will throw following error:

Errors were encountered while processing:
 wicd-daemon
 thermald
 grub-common
 resolvconf

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 wicd-daemon: Configure
 resolvconf: Configure
 grub-common: Configure
 thermald: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Apr 3 01:14:55 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-04-02 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Paul Rusu (paulrusu) wrote :
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
tags: removed: need-duplicate-check
Revision history for this message
Paul Rusu (paulrusu) wrote :

I resolved this issue by removing a script by which I tried, in vain, to restart the network-manager at reboot time.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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