package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
yes
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth-
ProcVersionSign
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
BootLog:
Scanning for Btrfs filesystems
UBUNTU: clean, 264727/29794304 files, 4160586/119152384 blocks
Date: Sat Dec 2 14:25:03 2017
DefaultPlymouth: /usr/share/
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-07-28 (127 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 8087:0a2a Intel Corp.
Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 14-3462
ProcCmdLine: BOOT_IMAGE=
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1
apt 1.2.10ubuntu1
SourcePackage: plymouth
TextPlymouth: /usr/share/
Title: package plymouth-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.0
dmi.board.name: 06N1P9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 14-3462
dmi.product.
dmi.sys.vendor: Dell Inc.
tags: | removed: need-duplicate-check |
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.