package cups 1.4.6-5ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cups (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
not sure, but this machine is being very problematic with the 11.04 upgrade; this bug report jumped out on the first time I was able to boot into safe-mode graphics
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: cups 1.4.6-5ubuntu1.4
ProcVersionSign
Uname: Linux 2.6.38-
Architecture: i386
CupsErrorLog:
W [04/Oct/
W [04/Oct/
W [04/Oct/
Date: Mon Oct 3 23:10:04 2011
DpkgTerminalLog:
Can not write log, openpty() failed (/dev/pts not mounted?)
Can not write log, openpty() failed (/dev/pts not mounted?)
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
Lpstat:
device for HP-PSC-1310: ipp://192.
device for Laser: ipp://192.
MachineType: HP-Pavilion GV443AA-ABA a6207c
Papersize: letter
PpdFiles:
Laser: Brother HL2270DW for CUPS
HP-PSC-1310: HP PSC 1310 Series, hpcups 3.11.1
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: cups
Title: package cups 1.4.6-5ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to natty on 2011-10-03 (0 days ago)
dmi.bios.date: 10/29/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.13
dmi.board.name: NARRA2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 2.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: GV443AA-ABA a6207c
dmi.sys.vendor: HP-Pavilion
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.