package plymouth 0.8.2-2ubuntu23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: plymouth
Update Manager.
Ubuntu 11.04 - the Natty Narwhal - released in April 2011
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: plymouth 0.8.2-2ubuntu23
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Sat May 7 05:11:35 2011
DefaultPlymouth: /lib/plymouth/
ErrorMessage: subprocess installed post-installation script returned error exit status 1
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: System manufacturer System Product Name
ProcFB: 0 nouveaufb
ProcKernelCmdLine: noprompt cdrom-detect/
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
Title: package plymouth 0.8.2-2ubuntu23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1009
dmi.board.
dmi.board.name: M3N78-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, the package installation error message that you have received is actually a failure with lzma and a generic one at that. The following steps may help resolve the issue. Please execute the following command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try performing the update again as this may resolve your issue. We plan to make lzma errors more informative and that work is being tracked in bug 691985 which I will mark this a duplicate of.