package plymouth (not installed) failed to install/upgrade: conflicting packages - not installing plymouth
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
bug on "do-release-
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth (not installed)
ProcVersionSign
Uname: Linux 4.2.0-35-generic i686
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
Date: Sun Apr 24 15:01:57 2016
DuplicateSignature: package:
ErrorMessage: conflicting packages - not installing plymouth
RelatedPackageV
dpkg 1.18.2ubuntu5.1
apt 1.0.10.2ubuntu2
SourcePackage: plymouth
Title: package plymouth (not installed) failed to install/upgrade: conflicting packages - not installing plymouth
UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago)
tags: | removed: need-duplicate-check |
Changed in apt (Ubuntu): | |
importance: | Undecided → High |
The error in your log is:
Selecting previously unselected package plymouth. 0.9.2-3ubuntu13 _i386.deb containing plymouth:
dpkg: regarding .../plymouth_
plymouth conflicts with console-common
console-common (version 0.7.88) is present and installed.
dpkg: error processing archive /var/cache/ apt/archives/ plymouth_ 0.9.2-3ubuntu13 _i386.deb (--unpack):
conflicting packages - not installing plymouth
This is correct, plymouth does conflict with console-common; this is not an accident.
The question is, why did the package manager not remove console-common in order to let plymouth be installed? Later on in your DpkgHistory.txt, we see that console-common *is* being removed. So this looks like a package manager bug for not correctly removing the package earlier.