Bug 861734 - systemd: "cups.socket failed to load" CUPS printing service does not start after boot
Summary: systemd: "cups.socket failed to load" CUPS printing service does not start af...
Status: RESOLVED DUPLICATE of bug 857372
: 861411 861755 (view as bug list)
Alias: None
Product: openSUSE 13.1
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: All openSUSE 13.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-02 05:00 UTC by Ulf Michel
Modified: 2014-02-11 10:43 UTC (History)
6 users (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulf Michel 2014-02-02 05:00:30 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0

cups version 1.5.4-137.1

cups has to be started manually after each boot.
Re-doing the printer installation in Yast2 starts CUPS service but the problem persists after next boot.

Message in /var/log/messages:

2014-02-02T05:24:23.859983+01:00 localhost systemd[1]: Cannot add dependency job for unit cups.socket, ignoring: Unit cups.socket failed to load: No such file or directory.

It appears that the problem is connected with a recent update of cups.

Reproducible: Always

Steps to Reproduce:
1. Reboot
2.
3.
Actual Results:  
cupsd not running after boot

Expected Results:  
cupsd should automatically be started.
Comment 1 Josef Reidinger 2014-02-03 12:01:31 UTC
Looks like cups problem according to entry in messages. Reassing to johannes as cups maintainer and adding to CC Cristian
Comment 2 Ulf Michel 2014-02-03 20:54:39 UTC
Reverting to cups 1.5.4-12.4.1 solved the problem

The newer version 1.5.4-137.1 was installed from
http://download.opensuse.org/repositories/Printing/openSUSE_13.1/
and apparently contains an error.
Comment 3 Johannes Meixner 2014-02-04 08:41:39 UTC
CUPS from the OBS "Printing" project intentionally does no longer
contain a systemd unit file cups.socket, see bnc#857372.

I don't know what in systemd causes that failure here for you now.
I am not at all a systemd expert and therefore I cannot debug
systemd issues.

For me CUPS from the OBS "Printing" project "just works", see
https://bugzilla.novell.com/show_bug.cgi?id=857372#c75
in particular note therein:
============================================================================
To make systemd using only that cups.service file one may have to do
# systemctl disable cups.service
# systemctl enable cups.service

What I have now on my openSUSE 13.1 system (after a reboot):
--------------------------------------------------------------------------
# systemctl list-unit-files | egrep -i 'print|cups'
configure-printer@.service                 static  
cups.service                               enabled 
printer.target                             static

# systemctl list-units | egrep -i 'print|cups'
cups.service   loaded active running   CUPS Printing Service
--------------------------------------------------------------------------

For me printing on my HP LaserJet 1220 USB printer still works and
I still get CUPS Browsing information from our CUPS server and
I can still print to such a remote queue.
============================================================================

Ulf Michel,
does
# systemctl disable cups.service
# systemctl enable cups.service
help in your case?

If not, a systemd expert would have to debug what goes wrong
in your particular case. I cannot do that.
Comment 4 Johannes Meixner 2014-02-04 09:21:48 UTC
*** Bug 861411 has been marked as a duplicate of this bug. ***
Comment 5 Ulf Michel 2014-02-04 09:47:46 UTC
I reinstalled 
cups version 1.5.4-137.1
with the same result: CUPS would not start.

Then I started as proposed
# systemctl disable cups.service
# systemctl enable cups.service

with no immediate change. cups can still not be called in the browser.

But after a reboot cups was working fine.
Comment 6 Ulf Michel 2014-02-04 09:51:28 UTC
and the outputs to the systemctl commands of comment 3 are identical to those reported there.

Before this change 
systemctl list-units | egrep -i 'print|cups'
would not report loaded active running
Comment 7 Johannes Meixner 2014-02-04 09:59:54 UTC
This shows that this one is actualy a duplicate of
what is currently going on under bnc#857372

*** This bug has been marked as a duplicate of bug 857372 ***
Comment 8 Johannes Meixner 2014-02-11 10:43:42 UTC
*** Bug 861755 has been marked as a duplicate of this bug. ***