Bug 860834 - After update openSUSE-2014-73 - update for cups (bnc#857372) CUPS doesen't start at boot time.
Summary: After update openSUSE-2014-73 - update for cups (bnc#857372) CUPS doesen't st...
Status: RESOLVED DUPLICATE of bug 857372
Alias: None
Product: openSUSE 12.3
Classification: openSUSE
Component: Printing (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 12.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: Johannes Meixner
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-28 15:04 UTC by Tiziano Ceccarini
Modified: 2014-01-28 16:09 UTC (History)
1 user (show)

See Also:
Found By: ---
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 Tiziano Ceccarini 2014-01-28 15:04:48 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.77 Safari/537.36

After update openSUSE-2014-73 - update for cups (bnc#857372) CUPS doesn't start at boot time.

cups.socket terminates with error:
systemd[1]: Starting CUPS Printing Service Sockets.
systemd[1]: cups.socket failed to listen on sockets: Cannot assign requested address
systemd[1]: Failed to listen on CUPS Printing Service Sockets.

In order to make CUPS to start at boot time I modified the original file at /etc/systemd/system/sockets.target.wants/cups.socket as follow:

[Unit]
Description=CUPS Printing Service Sockets

[Socket]
ListenStream=/var/run/cups/cups.sock
ListenStream=631
ListenDatagram=0.0.0.0:631
BindIPv6Only=ipv6-only

[Install]
WantedBy=sockets.target






Reproducible: Always
Comment 1 Dr. Werner Fink 2014-01-28 15:50:18 UTC
Q: *Why* should cups start at boot time and not on demand?

This question because if cups.socket would work as it should then cups would be started on demand.
Comment 2 Johannes Meixner 2014-01-28 16:09:13 UTC
I reopened bnc#857372 and assigned it to me.

I will try to clean up the mess - regardless that my
knowledge regarding systemd unit files is very limited.

For the full story see bnc#857372 ... ;-)

*** This bug has been marked as a duplicate of bug 857372 ***