package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed

Bug #1754371 reported by Oli
52
This bug affects 11 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

i was just trying to upgrade from 17.10 to 18.04 with do-release-upgrade -d

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
Uname: Linux 4.16.0-041600rc3-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
BootLog: /dev/sdb1: clean, 514969/7815168 files, 5180565/31258368 blocks
Date: Thu Mar 8 16:24:15 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-mate-logo/ubuntu-mate-logo.plymouth
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-11-04 (124 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 2548:1002
 Bus 001 Device 003: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600rc3-generic root=UUID=1a38371d-cf4f-49ca-9afe-a04f9585a598 ro quiet splash i915.alpha_support=1 vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600rc3-generic root=UUID=1a38371d-cf4f-49ca-9afe-a04f9585a598 ro quiet splash i915.alpha_support=1 vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt 1.5.1
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-mate-text/ubuntu-mate-text.plymouth
Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to bionic on 2018-03-08 (0 days ago)
dmi.bios.date: 11/28/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: Z370 Gaming-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd11/28/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Oli (olze) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
paul summers (paulsum) wrote :

well i am/was "affected" by this bug...(i am using the 4.15 kernel, and lsb_release -rd reports
Ubuntu Bionic Beaver (development branch); release 18.04)

 but it is more an operational inconsistency IMO because after doing

sudo apt --fix-broken install (which was need before the sudo apt update)

which installed the missing apps, that were removed by the do-upgrade...

then did the standard sudo apt upgrade...
 that installed the 850+ upgrades and the 4.15 kernel...

everything went smoothly after that...

well i had to remove deja-dup because of errors...(but i digress)

Revision history for this message
Markus Birth (mbirth) wrote :

Same here while upgrading my Raspberry Pi 2 (armhf) from 17.10 to 18.04. Upgrader finished with "Upgrade complete" but left hundreds of packages in their old versions. I had to fix that with aptitude and now it's actually finishing the upgrade.

Revision history for this message
Felix Oxley (felix-oxley) wrote :

This bug happened for me on 18/03/2018.

Upgrading from Ubuntu Mate 17.10

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.