Ubuntu
cups-pdf package

package cups-pdf 2.4.6-3ubuntu6 failed to install/upgrade: subprocess post-installation script returned error exit status 1

Bug #147801 reported by Vangelis Tasoulas on 2007-10-01

This bug report is a duplicate of: Bug #147974: package cups-pdf 2.4.6-3ubuntu6 failed to install/upgrade: le sous-processus post-installation script a retourné une erreur de sortie d'état 1. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	cups-pdf (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: cups-pdf

The last dist-upgrade followed by this error.

ProblemType: Package
Architecture: amd64
Date: Mon Oct 1 22:27:33 2007
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: vmnet vmblock vmmon nvidia
Package: cups-pdf 2.4.6-3ubuntu6
PackageArchitecture: amd64
SourcePackage: cups-pdf
Title: package cups-pdf 2.4.6-3ubuntu6 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux aurora 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux

Tags:

Revision history for this message

Vangelis Tasoulas (cyberang3l) wrote on 2007-10-01:

Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (1.9 KiB, application/x-gzip)

Revision history for this message

Vangelis Tasoulas (cyberang3l) wrote on 2007-10-01:

After a second dist-upgrade (exactly after the first one) the package installed correctly.

Revision history for this message

Erik Meitner (e.meitner) wrote on 2007-10-01:

The problem seems to be in the restarting of cupsd in the postinst script. I did an apt-get upgrade again and it finished ok.

The following was logged in /var/log/cups/error_log:
E [01/Oct/2007:14:52:23 -0500] PID 19005 (/usr/lib/cups/filter/foomatic-rip) crashed on signal 9!
E [01/Oct/2007:14:52:23 -0500] PID 19006 (/usr/lib/cups/backend/hp) crashed on signal 9!

I did have a job in the print queue for a printer that was not reachable at the time. Not sure if that could have been the cause.

Revision history for this message

Frank Zimmer (frank-e-zimmer) wrote on 2007-10-01:

I had the same error messages. When I removed an old print job which was a relict of my gutsy pre-installation time I could use apt-get upgrade again and it finished without any problems. So it seems to be due to old print jobs.