package qemu-kvm-extras-static 0.12.3 noroms-0ubuntu9.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu-kvm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Attempted to clean (apt-get clean) and uninstall then reinstall package. The error shows everytime I update or install/uninstall a package. /var/log/
Setting up qemu-kvm-
update-binfmts: warning: /var/lib/
start: Job failed to start
invoke-rc.d: initscript procps, action "start" failed.
dpkg: error processing qemu-kvm-
subprocess installed post-installation script returned error exit status 1
Not a show-stopper, but certainly annoying.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: qemu-kvm-
ProcVersionSign
Uname: Linux 2.6.32-32-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Jun 29 22:07:13 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 147e:2016 Upek Biometric Touchchip/
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: CLEVO M980NU
ProcCmdLine: BOOT_IMAGE=
SourcePackage: qemu-kvm
Title: package qemu-kvm-
dmi.bios.date: 10/16/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 2006Q4
dmi.board.name: M980NU
dmi.board.vendor: CLEVO
dmi.board.version: REFERENCE
dmi.chassis.type: 3
dmi.chassis.vendor: CLEVO
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: M980NU
dmi.product.
dmi.sys.vendor: CLEVO
Thanks for reporting this bug. I can trivially reproduce it, though not quite sure why it's happening yet. I'm marking this a duplicate of bug 799858, and will track the issue there.