This bug was split from bug #115888 (item 2 there):

The cupsd was stopped after YaST printer config had finished.
This leads to a problem when at the very end of the installation
the YaST scanner config is started (via YaST control center).
If the user selects the SANE hpoj backend for a HP all-in-one device
then the hplip service must be stopped and disabled and the ptal
service must be used instead.
There is a test in the scanner module whether or not the CUPS hp
backend is used (using /usr/bin/lpstat -v | /bin/grep -q ': hp:/'
see /usr/share/YaST2/modules/Scanner.ycp).
When no cupsd runs this test fails in any case and then it is
assumed everything is o.k. and then hplip would be silently
deactivated.
Michal,
Why is cupsd stopped in this particular case?
Wouldn't it be better to simply let it run?

To make it more clear what I meant above:
I talked about what happened during installation.
If I remember correctly the following happened:
Near the end of the installation after the hardware setup,
the cupsd was stopped. I don't know why it was stopped or what
it stopped (perhaps YaST2-printer?).
If I remeber correctly the cupsd was re-started at the very end
of the installation when the runlevel 5 (or 3) is reached.
The problem which I described happens only when the 
the YaST scanner config is started (via YaST control center)
after the cupsd was stopped but before it was re-started again.
For me it makes no sense to stop and re-start it.
Therefore I suggest to simply keep it running (except the user
has explicitely selected in YaST2-printer during hardware setup
that it should be stopped - e.g. for a "client-only" setup).