Bug#788374: system-config-printer-udev: systemd service fails with "failed to connect to CUPS"

[Laurent Bigonville]

On Wed, 10 Jun 2015 21:07:01 +0200 =?utf-8?b?VG9tYcW+IMWgb2xj?= 
<tomaz.solc at tablix.org> wrote:

Hi,

 >
 > systemd service "configure-printer" fails on boot with the following 
messages
 > in the journal:
 >
 > jun 10 19:37:26 orion udev-configure-printer[733]: add usb-005-002
 > jun 10 19:37:26 orion udev-configure-printer[733]: device devpath is 
/devices/pci0000:00/0000:00:1d.1/u
 > jun 10 19:37:26 orion udev-configure-printer[733]: 
MFG:HEWLETT-PACKARD MDL:DESKJET 940C SERN:MY18S6D186
 > jun 10 19:37:27 orion udev-configure-printer[733]: failed to connect 
to CUPS server; giving up
 >
 > This causes systemd to mark the host status as "degraded":
 >
 > $ systemctl --failed
 > UNIT LOAD ACTIVE SUB DESCRIPTION
 > ● configure-printer at usb-005-002.service loaded failed failed 
Configure Plugged-In Printer
 >
 > It looks like configure-printer gets started before CUPS. At least 
according to
 > this systemd output, cups.service only started 3 seconds after the error
 > message above:
 >
 > $ systemctl status cups
 > ● cups.service - CUPS Printing Service
 > Loaded: loaded (/lib/systemd/system/cups.service; enabled)
 > Active: active (running) since sre 2015-06-10 19:37:30 CEST; 1h 24min ago
 >
 > Otherwise as far as I can see, CUPS is configured and working 
correctly on my
 > machine.

Could you please also check if the cups.socket is active? The systemd 
service file is explicitly requiring it:

Requires=cups.socket
After=cups.socket

Laurent Bigonville