/etc/init.d/cupsys force-reload fails, breaking cupsys-driver-gimpprint

[Matt Zimmerman]

During a routine dapper upgrade:

Setting up cupsys-driver-gimpprint (4.2.7-10ubuntu1) ...
No Gimp-Print PPD files to update.
 * Restarting Common Unix Printing System: cupsd cupsd: Child exited on signal 15!
invoke-rc.d: initscript cupsys, action "force-reload" failed.
dpkg: error processing cupsys-driver-gimpprint (--configure):
 subprocess post-installation script returned error exit status 3
Errors were encountered while processing:
 cupsys-driver-gimpprint

I think there are a combination of problems here; perhaps both
cupsys-driver-gimpprint and the init script should be made more robust

[Martin Pitt (pitti)]

*** Bug 27882 has been marked as a duplicate of this bug. ***

[Martin Pitt (pitti)]

*** Bug 27631 has been marked as a duplicate of this bug. ***

[Martin Pitt (pitti)]

 cupsys (1.1.99.b1.r4841-1ubuntu6) dapper; urgency=low
 .
   * debian/cupsys.init: Call stop/start in the 'restart/force-reload' section
     to make use of the much more robust 'stop' handling. This should avoid
     frequent failures of force-reload. (Ubuntu #21787)
   * debian/cupsys.postinst:
     - Set permissions of /etc/cups/interfaces to root:lpadmin 2775.
     - Make /etc/printcap writable for group lpadmin.
     - This fixes third-party printer drivers and command line tools.
     - Ubuntu #20891

Leaving open, cupsys-driver-gimpprint should be made more robust.

[Martin Pitt (pitti)]

 gimp-print (4.2.7-10ubuntu2) dapper; urgency=low
 .
   * debian/cupsys-driver-gimpprint.postinst: Fix syntax of 'cupsys
     force-reload' call, and do not fail if reloading cupsys fails. (See
     Ubuntu #21787)

[Alan Tam (at)]

I think the cupsys initscript has its own problem that it does not work for
restart/force-reload.
This has also caused bug 26404, which is still generating me one error e-mail
per day.

[Alan Tam (at)]

Oh, I think cupsys 1.1.99.b1.r4841-1ubuntu6 will have solved that problem.

[Martin Pitt (pitti)]

*** Bug 28029 has been marked as a duplicate of this bug. ***

[Smoot (smoot)]

force-reload is also stopping browse broadcast messages. I have seen this when logrotate runs nightly. It uses force-reload to send a HUP signal to cupsd. Evidently, this wedges the print server, so it stops browse broadcasts. This is with version 1.3.2-1ubuntu7.1 in gutsy.

A simple workaroud is to change the force-reload switch in /etc/logrotate.d/cupsys to restart.

[Till Kamppeter (till-kamppeter)]

Smmot, your problem is addressed in bug 173470 and an upstream fix is already supplied. Please follow the discussion there.