package cups-bsd 1.3.9-17ubuntu3 failed to install/upgrade: subprocess post-installation script killed by signal (Illegal instruction)

[AlanRick]

Binary package hint: cups-bsd

Not sure if the failure to install cups-bsd is the same as the failure to install cups already reported.
But it didn't install when I updated jaunty.
I could autoremove it and install it again.

ProblemType: Package
Architecture: i386
CupsErrorLog:
 E [17/May/2009:19:02:42 +0200] [CGI] Unable to scan "@LOCAL"!
 E [18/May/2009:08:27:16 +0200] Unable to bind socket for address ::1:631 - Cannot assign requested address.
 E [18/May/2009:08:30:20 +0200] Unable to bind socket for address ::1:631 - Cannot assign requested address.
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script killed by signal (Illegal instruction)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
Lsusb:
 Bus 001 Device 002: ID 148f:2870 Ralink Technology, Corp.
 Bus 001 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 002 Device 002: ID 07cc:0201 Carry Computer Eng., Co., Ltd Mass Storage (UISDMC1S & UISDMC3S)
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTeK Computer INC. A7N8X
Package: cups-bsd 1.3.9-17ubuntu3
Papersize: letter
ProcCmdLine: root=UUID=28a71b6b-66df-48b1-a8e6-981c582d2cfe ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-12.43-generic
SourcePackage: cups
Title: package cups-bsd 1.3.9-17ubuntu3 failed to install/upgrade: subprocess post-installation script killed by signal (Illegal instruction)

[John Burkhart (jfburkhart)]

Eventually fixed it by reinstalling, but prior had to delete

/etc/init.d/cups
/etc/default/cups

Then running apt-get install cups worked.

[Bryan Quigley (bryanquigley)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

This is a package failure between currently unsupported releases so we can no longer work on this.