Comment # 4 on bug 1151174 from Johannes Meixner

Mindaugas Baranauskas,
thank you for your feedback - it is much appreciated!
It helps a lot to better understand how by default enabled
"nice to have" stuff could make things completely fail
in this or that unusual case.

My guess in this case here with a HP USB printer that needs
firmware upload is that udev-configure-printer interferes
with the firmware upload which lets things completely fail.

Regarding automated printer setup in general see the section
"Automated Printer Configuration" in
https://en.opensuse.org/YaST_Printer

FWIW:
On my systems with a USB printer I remove udev-configure-printer
because I prefer my personal manual static setup over automatisms.

Martin Wilck,
FYI see in particular
https://bugzilla.opensuse.org/show_bug.cgi?id=1151174#c2

This issue here is yet another example where automated actions
when pug-in a USB printer (here what udev-configure-printer does)
could cause more harm than good in some cases.

Since udev-configure-printer exists it is known to sometimes cause
weird inexplicable issues in this or that case.

It seems in general HP USB printers that need firmware upload
behave somewhat fragile during their startup phase.

For my own experience a longer time ago
with that kind of devices see
https://bugs.launchpad.net/hplip/+bug/187049
therein see in particular comment #3
for my I experience with a HP printer that needs firmware upload
which behaved very fragile during its startup phase.
What worked most reliably for me was manual firmware upload.
When firmware upload was succesful those HP USB printers work
as reliable as normal USB printers do according to my experience.