package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13.1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Trying to upgrade from 16LTS to 18LTS
do-release-upgrade fails with "too many errors"
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: plymouth-
ProcVersionSign
Uname: Linux 4.4.0-210-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
BootLog: Error: [Errno 2] No such file or directory: '/var/log/boot.log'
Date: Mon Dec 20 19:05:58 2021
DefaultPlymouth: Error: command ['readlink', '/etc/alternati
ErrorMessage: Abhängigkeitspr
InstallationDate: Installed on 2019-10-14 (798 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel Corporation NUC7i3BNK
ProcCmdLine: BOOT_IMAGE=
ProcFB: 0 inteldrmfb
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.19
SourcePackage: plymouth
TextPlymouth: /usr/share/
Title: package plymouth-
UpgradeStatus: Upgraded to bionic on 2021-12-20 (0 days ago)
dmi.bios.date: 02/22/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.
dmi.board.name: NUC7i3BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J22859-313
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.
dmi.modalias: dmi:bvnIntelCor
dmi.product.name: NUC7i3BNK
dmi.product.
dmi.sys.vendor: Intel Corporation
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.