Comment # 1 on bug 1160097 from Johannes Meixner

The YaST2 module Service.rb belongs to YaST2
so I change the Bugzilla component accordingly.

>From what I can read in comment #0
I only see some "Warning" messages but no error which indicates
that "systemctl stop cups.service" had actually failed.

So from my current point of view I think things had worked
and those "Warning" messages can be ignored, cf.
https://blog.schlomo.schapiro.org/2015/04/warning-is-waste-of-my-time.html

See also
https://en.opensuse.org/openSUSE:Report_a_YaST_bug

FYI some background information:

On a from scratch installed openSUSE Tumbleweed
(i.e. not an upgrade from a previous Tumbleweed version)
not any CUPS service should be enabled or started
because by default services get only enabled/started
when the user had explicitly confirmed that he wants
to use a particular service.

So on a from scratch installed openSUSE Tumbleweed
neither cups.service nor cups.socket nor cups.path
should be enabled/started (i.e. all are disabled/stopped).

As far as I know the YaST printer module only
supports cups.service but neither cups.socket nor cups.path.

As far as I know there is nothing in the YaST printer module
that would enable/start cups.socket or cups.path
so cups.socket and cups.path should stay disabled/stopped.

So I cannot imagine the reason behind why there are
those "Warning" messages which indicate that in this case
cups.socket and cups.path seem to be enabled/started.