package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

Bug #1576179 reported by Timo Järventausta
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This pops up every time I reboot.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu13
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Wed Apr 27 22:08:05 2016
DefaultPlymouth: /lib/plymouth/themes/tux-color/tux-color.plymouth
DuplicateSignature:
 Processing triggers for plymouth-theme-ubuntu-text (0.9.0-0ubuntu9) ...
 sed: can't read /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth.in: No such file or directory
 dpkg: error processing package plymouth-theme-ubuntu-text (--unpack):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationDate: Installed on 2015-07-20 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=f6f440ae-27fb-4c01-84c6-cceb2fd7ee15 ro quiet splash vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=f6f440ae-27fb-4c01-84c6-cceb2fd7ee15 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.207:bd02/05/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Timo Järventausta (timpelit) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Steve Langasek (vorlon) wrote :

The error in your log is:

Processing triggers for plymouth-theme-ubuntu-text (0.9.0-0ubuntu9) ...
sed: can't read /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth.in: No such file or directory
dpkg: error processing package plymouth-theme-ubuntu-text (--unpack):
 subprocess installed post-installation script returned error exit status 2

But the bug report shows an error configuring plymouth-theme-ubuntu-text version 0.9.2-3ubuntu13, not 0.9.0-0ubuntu9. Version 0.9.0-0ubuntu9 of the package included this file. Version 0.9.2-3ubuntu13 does not. But if 0.9.2-3ubuntu13 had been unpacked, you should not see messages from the triggers of the older version.

Please paste the output of the following command on your system:

dpkg -l '*plymouth*'

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]

Changed in plymouth (Ubuntu):
status: Incomplete → Expired
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.