package plymouth 0.8.2-2ubuntu30 failed to install/upgrade: dependency problems - leaving unconfigured

Bug #1077598 reported by Toni Rohas on 2012-11-11
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Undecided
Unassigned

Bug Description

12.04

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu30
ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
Uname: Linux 3.2.0-33-generic i686
ApportVersion: 2.0.1-0ubuntu15
Architecture: i386
Date: Sun Nov 11 01:33:13 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ErrorMessage: dependency problems - leaving unconfigured
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
MachineType: ASUSTeK Computer INC. 900
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-33-generic root=UUID=1876e21b-5aae-4d12-a61a-71f73628618a ro quiet splash vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-33-generic root=UUID=1876e21b-5aae-4d12-a61a-71f73628618a ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: package plymouth 0.8.2-2ubuntu30 failed to install/upgrade: dependency problems - leaving unconfigured
UpgradeStatus: Upgraded to precise on 2012-11-11 (0 days ago)
dmi.bios.date: 07/07/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 900
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd07/07/2008:svnASUSTeKComputerINC.:pn900:pvr0802:rvnASUSTeKComputerINC.:rn900:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 900
dmi.product.version: 0802
dmi.sys.vendor: ASUSTeK Computer INC.

Toni Rohas (toni-rohas) wrote :
Steve Langasek (vorlon) wrote :

The error in the log is:

Setting up initramfs-tools (0.99ubuntu13) ...
Installing new version of config file /etc/initramfs-tools/initramfs.conf ...
Installing new version of config file /etc/initramfs-tools/update-initramfs.conf ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-45-generic
E: /usr/share/initramfs-tools/hooks/casper failed with return 1.
update-initramfs: failed for /boot/initrd.img-2.6.32-45-generic with 1.
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools

This is probably a known (and since-fixed) bug in the casper hook. There is no reason to have the casper package on an installed system unless you're using a live image (which doesn't appear to be the case here); you should be able to work around this by removing the casper package.

affects: plymouth (Ubuntu) → casper (Ubuntu)
Launchpad Janitor (janitor) wrote :

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

Changed in casper (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers