package cups 1.5.2-5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
dpkg crashes trying to configure cups.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-5
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CupsErrorLog:
Date: Tue Feb 28 23:49:50 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 064e:a110 Suyin Corp. HP Webcam
MachineType: Hewlett-Packard HP Pavilion dv9700 Notebook PC
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: cups
Title: package cups 1.5.2-5 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: 11/29/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.name: 30D1
dmi.board.vendor: Quanta
dmi.board.version: 85.24
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv9700 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #942771, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.