package cups 1.5.2-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Thomi Richards]

Happened when doing a dist-upgrade from a newly-installed precise-desktop.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: cups 1.5.2-4
ProcVersionSignature: Ubuntu 3.2.0-17.26-virtual 3.2.6
Uname: Linux 3.2.0-17-virtual x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CupsErrorLog:

Date: Thu Feb 23 15:47:45 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120130)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
MachineType: innotek GmbH VirtualBox
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-virtual root=UUID=d953a8e6-b082-46fd-9459-d8990af801fd ro quiet splash vt.handoff=7
SourcePackage: cups
Title: package cups 1.5.2-4 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: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[Thomi Richards (thomir-deactivatedaccount)]

re-running 'sudo apt-get dist-upgrade' a second time managed to install cups without any issues.

[Apport retracing service (apport)]

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 #935154, 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.