https://bugzilla.novell.com/show_bug.cgi?id=857372
https://bugzilla.novell.com/show_bug.cgi?id=857372#c47
--- Comment #47 from Johannes Meixner 2014-01-24 14:33:30 CET ---
It is also my experience that cups.socket does not work well.
What I try to do is to "just use only the real thing"
(i.e. I use only the cupsd directly) which is what works
and what had worked all the time in the past, cf. comment#29.
What I usually do to make it working as usual for me is something like:
--------------------------------------------------------------------------
# systemctl list-units | grep cups
cups.path loaded active waiting CUPS Printer Service Spool
cups.service loaded active running CUPS Printing Service
cups.socket loaded active running CUPS Printing Service Sockets
# systemctl stop cups.path
# systemctl stop cups.socket
# systemctl stop cups.service
# systemctl list-units | grep cups
#
# systemctl list-unit-files | grep cups
cups.path enabled
cups.service enabled
cupsd.service enabled
cups.socket enabled
# systemctl disable cups.path
rm '/etc/systemd/system/multi-user.target.wants/cups.path'
# systemctl disable cups.socket
rm '/etc/systemd/system/sockets.target.wants/cups.socket'
# systemctl list-unit-files | grep cups
cups.path disabled
cups.service enabled
cupsd.service enabled
cups.socket disabled
# systemctl start cups.service
# systemctl list-units | grep cups
cups.service loaded active running CUPS Printing Service
--------------------------------------------------------------------------
I do not know if other systemd "print" stuff might interfere
with my intention to have only the plain cupsd active:
--------------------------------------------------------------------------
# systemctl list-units | grep -i print
cups.service loaded active running ...
system-configure\x2dprinter.slice loaded active active ...
printer.target loaded active active ...
--------------------------------------------------------------------------
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.