Problem with CUPS daemon

English Network/Internet
#1

I have two desktop PCs and a netbook, all running up-to-date versions of 13.1 and KDE 4.11.5.

One PC is connected to an HP printer by USB cable and works fine. The other PC and the netbook are connected to a separate HP printer by WiFi. Every time I reboot them, I have to go to Yast>system>services manager where I find that cups and cupsd daemons are shown as enabled/inactive. The printer won’t print until I set them to active.

Is there a way to make them automatically active after booting?

#2

Check that CUPS is running with

systemctl status cups

and for completeness, please report the output of

cat /usr/lib/systemd/system/cups.service
#3

BTW, for most users CUPS uses socket-activation, so it is normal to show as enabled and inactive until a print job invokes it. (However, it is possible to disable socket-activation and have cupsd listening actively if preferred.)

#4

Hello Deano, thanks for your reply. Requesting a print doesn’t seem to activate the daemons. Anyway, here are the results of your code:
After rebooting, I get:

code
XXXXXXX:~> systemctl status cups
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: inactive (dead)

XXXXXXX:~> cat /usr/lib/systemd/system/cups.service
[Unit]
Description=CUPS Printing Service

[Service]
ExecStart=/usr/sbin/cupsd -f

[Install]
Alias=cupsd.service
Also=cups.socket cups.path
WantedBy=printer.target
code

After manually starting the daemons, I get:

code
XXXXXXX:~> systemctl status cups
cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: active (running) since Sat 2014-05-17 09:01:51 BST; 52s ago
Main PID: 7032 (cupsd)
CGroup: /system.slice/cups.service
└─7032 /usr/sbin/cupsd -f

XXXXXXX:~> cat /usr/lib/systemd/system/cups.service
[Unit]
Description=CUPS Printing Service

[Service]
ExecStart=/usr/sbin/cupsd -f

[Install]
Alias=cupsd.service
Also=cups.socket cups.path
WantedBy=printer.target
code

I didn’t have this problem with 12.3. Is it perhaps a systemd thing? Sorry, don’t seem to have got the hang of this code thing!

#5

Yes, so you say :slight_smile:

Your output confirms that you have systemd configured to provide socket-activation (which dies work for most). I’m curious to know how others with network printers get on.

I didn’t have this problem with 12.3. Is it perhaps a systemd thing? Sorry, don’t seem to have got the hang of this code thing!

Actually, there was a bug discussed here (and there have been updates to the CUPS package that supposedly resolved the issue). For the record, I disabled socket-activation, (by disabling cups.socket) and editing cups.service to look like

# cat /usr/lib/systemd/system/cups.service
[Unit]
Description=CUPS Printing Service
After=network.target

[Service]
ExecStart=/usr/sbin/cupsd -f

[Install]
WantedBy=multi-user.target

This appraoch could work for you but there may be other methods of attack. You may also consider subscribing to the printing repo

http://download.opensuse.org/repositories/Printing/openSUSE_13.1/

and updating CUPS from that. Then check the ‘printing on demand’ behaviour again.

#6

Sorry, don’t seem to have got the hang of this code thing!

The advanced editor has the ‘#’ symbol which creates the

[/CO..] tags (or you can type them manually as I often do).
#7

Thanks again. I think I’ll try the cups repo approach first, then report back.

#8

On 2014-05-17 11:06, deano ferrari wrote:
>
>> Sorry, don’t seem to have got the hang of this code thing!
> The advanced editor has the ‘#’ symbol which creates the
> Code:
> --------------------
> [/CO…] tags (or you can type them manually as I often do).
>

See photo

–
Cheers / Saludos,

Carlos E. R.

(from 13.1 x86_64 “Bottle” (Minas Tirith))