Bug#738801: cups: /etc/init.d/cups stop/start hang when systemd is installed

[Damyan Ivanov <dmn@debian.org>]

-=| Nye Liu, 12.02.2014 17:51:19 -0800 |=-
> Package: cups
> Version: 1.7.1-4
> Severity: important
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> running /etc/init.d/cups stop or start (for example, as root, or by
> logrotate)
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> 
> with cups running:
> # /etc/init.d/cups stop
> with cups not running:
> # /etc/init.d/cups start
> 
>    * What was the outcome of this action?
> 
> # /etc/init.d/cups stop
> [....] Stopping cups (via systemctl): cups.service
> 
> hangs indefinitely
> 
> If I kill it by hand, then
> # /etc/init.d/cups start
> [....] Starting cups (via systemctl): cups.service
> 
> hangs indefinitely
> 
>    * What outcome did you expect instead?
> 
> The cups daemon should start/stop as expected.
> 
> Also, "systemctl start/stop cups.service" acts the same.

Here's some additional info:

In my case when aptitude is truing to configure cups-daemon, there is 
a hang that lasts for some 10 minutes, then things fail:

  Setting up cups-daemon (1.7.1-4) ...
  Job for cups.service failed. See 'systemctl status cups.service' and 'journalctl -xn' for details.
  invoke-rc.d: initscript cups, action "start" failed.
  dpkg: error processing package cups-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1

If I try to start cups-daemon by hand, it fails immediately:

  $ sudo service cups-daemon start                                                                                   ~
  Failed to issue method call: Unit cups-daemon.service failed to load: No such file or directory. See system logs and 'systemctl status cups-daemon.service' for details.

  $ sudo systemctl status cups-daemon.service                                                                        ~
  cups-daemon.service
     Loaded: error (Reason: No such file or directory)
     Active: inactive (dead)

Heh, fiddling with /etc/init.d/cups I purged xprint-common and this 
seems to have fixed the cups problem:

  $ sudo dpkg -P xprint-common                                                                                       ~
  (Reading database ... 491921 files and directories currently installed.)
  Removing xprint-common (2:1.4.2-11) ...
  Purging configuration files for xprint-common (2:1.4.2-11) ...

  $ sudo dpkg --configure -a                                                                                         ~
  Setting up man-db (2.6.6-1) ...
  Updating database of manual pages ...
  Setting up cups-daemon (1.7.1-4) ...          <- this was hanging/failing before
  Setting up cups-core-drivers (1.7.1-4) ...
  Setting up cups (1.7.1-4) ...
  Updating PPD files for cups ...
  Updating PPD files for cups-filters ...
  Updating PPD files for cups-pdf ...
  Updating PPD files for foomatic-db ...
  Updating PPD files for foomatic-db-engine ...
  Updating PPD files for hpcups ...
  Updating PPD files for postscript-hp ...


I hope this helps to pinpoint the problem.

-- dam