Comment # 2 on bug 1160097 from Ralf Habacker

Created attachment 827359 [details]
y2log extract

I tried to reproduce the problem, but it was not possible for cups.path in this
case.

The additional services are defined in the cups systemd service file:

ralf@localhost:~> cat /usr/lib/systemd/system/cups.service
[Unit]
Description=CUPS scheduler
documentation=man:cupsd(8)
To=network.destination

[Service]
ExecStart=/usr/sbin/cupsd -l
Type=simple
Restart=in case of error

[Installing]
Also=cups.socket cups.path
WantedBy=printer.destination

and therefore they are probably mentioned by Systemd in actions related to the
cups service. 

ralf@localhost:~> sudo systemctl stop cups
Warning: cups.service is stopped, but can still be activated:
  cups.socket

After going through a printer change, I remember some additional details:

After applying changes to the printer configuration, yast displays a message
that it will restart the Cups service. After trying to do this, it will tell
you that the service is still available (I haven't had that in the last 10
years with Suse distries). 

According to the appended log does the Yast printer module simply follows the
advice of systemctl and also tries to stop the mentioned services, which causes
the listed message to be issued again (twice in my case).

Since the user does not know about this internal behavior, it is a surprising
behavior and lets the user assume that there was a problem with the printer
change, as in my case, since I stopped the printer change and restarted it.

In case additional services are mapped to the cups service Yast printer should
stop additional services silently to not confuse users.