package qemu-user-static 1:2.2+dfsg-5expubuntu9.7 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
when boot or reboot or install software , this will occur.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: qemu-user-static 1:2.2+dfsg-
ProcVersionSign
Uname: Linux 3.19.0-93-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
Date: Sat Mar 17 22:28:11 2018
DpkgTerminalLog:
正在设置 qemu-user-static (1:2.2+
update-binfmts: warning: current package is qemu-user-static, but binary format already installed by qemu-user-binfmt
update-binfmts: exiting due to previous errors
dpkg: 处理软件包 qemu-user-static (--configure)时出错:
子进程 已安装 post-installation 脚本 返回错误状态 2
DuplicateSignature: package:
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 2
InstallationDate: Installed on 2016-01-01 (806 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
KvmCmdLine:
COMMAND STAT EUID RUID PID PPID %CPU COMMAND
qemu-system-i38 Sl 0 0 1793 1 0.0 /usr/bin/
MachineType: LENOVO 33511N1
ProcKernelCmdLine: placeholder root=UUID=
SourcePackage: qemu
Title: package qemu-user-static 1:2.2+dfsg-
UpgradeStatus: Upgraded to vivid on 2017-09-28 (171 days ago)
dmi.bios.date: 01/11/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: H6ET90WW (2.08 )
dmi.board.
dmi.board.name: 33511N1
dmi.board.vendor: LENOVO
dmi.board.version: 0B98413 STD
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 33511N1
dmi.product.
dmi.sys.vendor: LENOVO
information type: | Private Security → Public |
tags: | removed: need-duplicate-check |
Thanks for filing this bug in Ubuntu.
I'm sorry, but the Ubuntu release you reported this bug against, Vivid 15.04, is no longer maintained. Please try again with a supported release like Xenial 16.04 LTS, Artful 17.10 or even the upcoming Bionic 18.04 LTS. If the problem happens there again, then please open a new bug in that release.