package plymouth-theme-ubuntu-text 0.8.2-2ubuntu31.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 install-procedure failed on wrong user command
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
When installing, i did not erase the full ssd. Remaining rests of older installations affected on the new one.
It is better installing on a "fresh" machine.
Josef Overmann
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: plymouth-
ProcVersionSign
Uname: Linux 3.8.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CurrentDmesg:
Date: Mon Feb 10 08:14:03 2014
DefaultPlymouth: /lib/plymouth/
DpkgHistoryLog:
Start-Date: 2014-02-10 08:14:00
Commandline: aptdaemon role='role-
Upgrade: base-files:amd64 (6.5ubuntu6.6, 6.5ubuntu6.7), gambas3-
DuplicateSignature: package:
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationMedia:
MachineType: Gigabyte Technology Co., Ltd. H55M-USB3
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
Title: package plymouth-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/04/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: H55M-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: H55M-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
Changed in plymouth (Ubuntu): | |
status: | Confirmed → Incomplete |
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.