package plymouth-theme-ubuntu-text .09.2-3ubuntu13.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Received error when attempting to upgrade from 16.04 to 18.04
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: plymouth-
ProcVersionSign
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
Date: Tue Aug 17 17:15:04 2021
DefaultPlymouth: Error: command ['readlink', '/etc/alternati
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-05-17 (1553 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdLine: BOOT_IMAGE=
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2.3
apt 1.2.24
SourcePackage: plymouth
TextPlymouth: /usr/share/
Title: package plymouth-
UpgradeStatus: Upgraded to bionic on 2021-08-18 (0 days ago)
dmi.bios.date: 09/30/2014
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: VMware Virtual Platform
dmi.product.
dmi.sys.vendor: VMware, Inc.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1611071, so it 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. Feel free to continue to report any other bugs you may find.