Mailinglist Archive: opensuse-bugs (4688 mails)

< Previous Next >
[Bug 580217] Deskjet F2400 series devices not supported by the HPLIP version in openSUSE
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 18 Feb 2010 08:32:37 +0000
  • Message-id: <20100218083237.3AECCCC7CE@xxxxxxxxxxxxxxxxxxxxxx>

--- Comment #13 from Johannes Meixner <jsmeix@xxxxxxxxxx> 2010-02-18 08:32:35
UTC ---
Regarding comment #10:

For me the explicite message
"error: Unsupported model: Deskjet_F2400_series"
makes it clear that it is actually unsupported
in HPLIP 3.0.8 and that the "Installation Wizard"
on is wrong.

Regarding "hp-check" and missing packages:
It is a terrible old issue that hp-check reports
be default both runtime and compile-time requirements
and almost any usser (and even the HP support people)
get needlessly confused, see for example

Therefore run "hp-check -r"
to test only for run-time requirements.

Regarding comment #11:

"io/hpmud/musb.c 1987: invalid usb_open: Permission denied" see
and its duplicates.

Because you did already run /usr/lib64/cups/backend/hp
as root and it didn't detect your printer (see comment #4),
read/write permissions for normal users for
the USB device node doesn't help here.

Regarding comment #12:

I wonder which printer setup tool may have set up a queue
using a non-working DeviceURI
according to 'cups_printer_dict' in attachment #342681
which cannot work at all, see comment #5.

In particular yast2-printer works in full compliance to CUPS, see
Therefore it shows only DeviceURIs to the user
which are known by CUPS i.e. which are shown in
/usr/sbin/lpinfo -v
which does in the end (via cupsd plus cups-deviced) nothing else
than to call each executable in /usr/lib[64]/cups/backend/
and collect the autodetection output of all backends.

Therefore either a backend did report the DeviceURI
but I have no idea which backend except "hp" could do it
or some broken printer setup tool did somehow
create it on its own.

It is crucial that whatever "smart" printer setup tool
does not set up print queues with random generated DeviceURIs
because this leads to nothing else but annoyance for the user.

do you perhaps remember how you got a print queue
with the non-working DeviceURI

Was the queue perhaps already somehow "magically" present
in all those printer setup tools which you tried out
or did you manually set up the queue - did you perhaps
even manually enter the above DeviceURI?

There is nothing bad with a manually entered DeviceURI
but of course then you are responsible that it is valid.

In the end I really think you need HPLIP version 3.9.10 (or later)
for a Deskjet F2400 series device.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >