--- Comment #5 from Johannes Meixner <jsmeix(a)novell.com> 2010-02-17 08:56:15 UTC
What results when you run
rpm -qa | grep cups
Because of whatever reason HPLIP's "hp" backend
fails to detect the printer in your particular case.
You may have a look at /var/log/messages for 'hp' related
(error)-messages e.g. via calling as root the command
grep -i 'hp' /var/log/messages | tail -n50
In contrast the generic CUPS "usb" backend
detects the printer.
Therefore in your particular case your printer cannot work
with the "hp" backend but should work with the "usb" backend.
Because of whatever reason according to 'cups_printer_dict'
in attachment #342681 it seems system-config-printer
(or whatever other printer setup tool) did set up a queue
with the "hp" backend which is used via the DeviceURI
but this print queue cannot work.
To set up a queue with the "usb" backend
use YaST (run as root "yast2 printer") and you may have to click
[More Connections] to get also the "usb:/..." connection shown
(by default YaST prefers the "hp:/..." connection for HP devices)
and use the "usb:/..." connection to set up the print queue
(see also the help text in YaST).
You can still use the hpijs driver for the queue.
I.e. you can get the same printout quality.
The crucial point is that the data transfer to the printer
happens via the "usb" CUPS backend.
In contrast to the "hp" backend which privides bidirectional
communication (e.g. for scanning and for device status info)
the generic CUPS "usb" backend does only unidirectional
data transfer to the printer so that device status information
and scanning for all-in-one devides is no longer possible
with the generic CUPS "usb" backend.
Note that a few low-end HP devices require bidirectional
communication in any case even for normal printing.
I hope that a Deskjet F2400 series device is sufficiently
normal to print also with unidirectional communication.
See bug #462048 in particular
and for basic information regarding CUPS backends see
Please report if printing via the generic CUPS "usb" backend works.
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.