https://bugzilla.novell.com/show_bug.cgi?id=473679
User jsmeix@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=473679#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Johannes Meixner 2009-02-09 23:56:40 MST ---
You need a printer setup using the hp:/... CUPS DeviceURI
but not e.g. a socket:/ or lpd:/ DeviceURI,
see what "lpstat -v" reports.
I assume you don't have a hp:/... CUPS DeviceURI.
The reason is that there is some magic in HPLIP
that the printer DevicURI is needed to derive
the SANE device from it so that hp-* tools know
the right SANE device, compare
http://hplipopensource.com/node/212
Best is to run as root "hp-setup" to do the setup
because currently there is no special support for
HP all-in-one network devices in YaST.
For HP all-in-one USB devices a hp:/... CUPS DeviceURI
is used by default but for HP all-in-one network devices
YaST would have to run "hp-probe -bnet" for correct
autodetection which is not yet implemented (currently
YaST relies on CUPS network printer autodetection
via "lpinfo -v" which results socket:/ DeviceURIs).
If you like you could file an enhancement request that
yast2-printer should additionally run "hp-probe -bnet".
The kooka issue is known.
kooka simply works only for devices which show
up automatically via "scanimage -L".
It does not work for kooka to specify the SANE device
on the commandline.
When kooka does not find a scanner, it shows the
misleading nonsense message about "no SANE installation",
see bug #141079
If you like, you could file a bug reagarding kooka
but kooka is an "outdated" KDE3 application
(the KDE4 scanner frontend is skanlite)
so that I assume it would not be fixed.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
