What is the CUPS "DeviceURI" when you set it up with YaST?
Use
lpstat -v
and report which queue was set up with YaST and which with KDE.

Note that the hp-toolbox requires the hp CUPS backend which
we don't use by default in YaST for normal printers because
this backend requires additional services to be started, see
http://en.opensuse.org/SDB:Printer_Configuration_from_SUSE_LINUX_9.3_on
"By default, the CUPS backend "hp" is only used for all-in-one devices"
and
http://en.opensuse.org/SDB:Set_up_a_HP_OfficeJet_%28%22all-in-one%22_device%29
"we prefer not to start any service that is not required."

KDE:
device for HPDeskJet6540: hp:/usb/Deskjet_6500?serial=MY47F2R23M040N

YaST:
device for deskjet6500: usb://HP/Deskjet%206500?serial=MY47F2R23M040N

It works exactly as it should.

For example I have a HP LaserJet 1220 (printer + scanner)
and a HP DeskJet 990C and I get the following DeviceURIs:
device for deskjet990c: usb://HP/DeskJet%20990C?serial=MX09R1T14QLH
device for laserjet1220: hp:/usb/HP_LaserJet_1220?device=/dev/usb/lp2

Perhaps we may think about an enhancement for YaST to let the
user choose the "hp" backend for any kind of HP printing device?

In particular YaST could use the "hp" backend by default even for
a normal HP printer, when the "hplip" services are already running
and/or when there is another queue which uses the "hp" backend?

When YaST sets up the additional "hplip" service it should inform
the user about the new service which is running on his system
which leads to a problem how to inform the user in case of
automated setup?

Michal,
what do you think?

You are the expert so you decide.

But nevertheless how can I use yast to configure my printer using the right deviceURI?

Matthias, I had set it to NEEDINFO from Michal (not from you).
He is the YaST expert ;-)

I tried to use YaST to change the CUPS backend for my DeskJet 990C
from "usb" to "hp" (via selecting the queue in YaST and the [Edit]...)
but it was not possible because I cannot select the "hp" backend
in YaST :-(

Michal,
I think that YaST printer config should really be changed
to work in full compliance to CUPS regarding the backend/DeviceURI
(i.e. use only CUPS and no "third-party" tools like hwinfo).

E.g. for printer autodetection Yast could use

for b in /usr/lib*/cups/backend/*
do $b 2>/dev/null | cut -d '"' -f 2 | grep -v Unknown
done

Note that each backend also reports the exact correct DeviceURI
and whether it is a local connected printer ("direct" or "serial")
or a network printer ("network").

I agree with this.
There is something similar for detect HplipDevices, but it seems don't work well.
Johannes, is it enought when I add "hp" value when hplip will detect any printer?

I mean this:
 - when user will choose usb device for hp printer, "DeviceURI usb:..." will be replace by "DeviceURI hp:..." if hplip is installed or will be installed corretly
 - hplip service will be inserved and user will be inform with this (it's enhancement #115888)
 - in case of autoyinstallation user will be informed when creating profile with autoyast (the same way as on running system)

Comment #8 looks o.k. for the semi-automated case
(i.e. YaST guides the user to set up the "hp" backend).

Note that the "hp" backend also supports HP parallel port devices
and HP network devices.

I have also the full-manual case in mind:
I.e. the "hp" backend should be available among the other
connection types on the "Printer Type" screens so that the user
can choose it via [Add] or [Edit] - e.g. for local connected printers:
 O Parallel Printer
 O USB Printer
 O Serial Printer
 O IrDA Printer
 O Bluetooth Printer
 O HP Printer or HP All-in-one Device
and for the "Print directly to a Network printer" case:
 O Direct TCP Port Printing
 O Remote LPD Queue
 O Remote IPP Queue
 O HP Network Printer or HP All-in-one Network Device

I reassign this enhancement request to the YaST printer module author.

So will this be fixed and backported to 10.1 soon?

I will implement it, but I can't say date.

Regarding comment #11:
It is an enhancement request for a future product
and no bug (see comment #3).
We do not provide new-feature-upgrades for released products.

At the moment I have no idea how we should handle the full-automated
setup at the end of the installation because we cannot force the user
to answer a question whether or not he likes the additional services.

*** Bug 181857 has been marked as a duplicate of this bug. ***

*** Bug 194802 has been marked as a duplicate of this bug. ***

(In reply to comment #13)
> Regarding comment #11:
> It is an enhancement request for a future product
> and no bug (see comment #3).
> We do not provide new-feature-upgrades for released products.

So this means I cannot use YaST to setup my printer but have to use CUPS, right?

At the moment you cannot use YaST to setup a plain HP printer
with the "hp" backend. For details see bug #184798

It is possible to make workarround (write uri with hp://... directly), but it's not user-friendly:
Add->Network Printers->Other Setup->Other Printer(URI)
But it needs to use console because of URI of connected printer

(In reply to comment #18)
> It is possible to make workarround (write uri with hp://... directly), but it's
> not user-friendly:
> Add->Network Printers->Other Setup->Other Printer(URI)

How do I get the actual URI I have to type in?

> But it needs to use console because of URI of connected printer

What do you mean by console? Doesn't it work under X11?

To 1&2 questions:
- In console (or terminal or whatever) start hplip service (rchplip start)
- Run hp backend and see URI of connected HP printers(/usr/lib/cups/backend/hp)
- Use this URI in YaST

move to later

reopen

fixed