Hardy: HP Officejet 5600 not available in device list

Bug #229663 reported by zity
4
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Won't Fix
High
Jonathan Riddell

Bug Description

Binary package hint: hplip

I've tried to install a networked HP Officejet 5600 printer in KDE Systems Settings, but the model is not appearing in the model selection list.
It was available under Gusty and worked fine.

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

Please run hp-check -t and post the output.

A

Revision history for this message
zity (zdevai) wrote :

Attached.

Just some clarification:
- The device list is not empty, there are a lots of devices I'm just missing my OJ5600 which was in the list in Gutsy
- Connecting the printer directly via USB works fine, it got auto-detected and auto-installed without a problem

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

How are you configuring the printer for the network?

Try running

hp-setup -i ip.address.of.printer

A

Revision history for this message
zity (zdevai) wrote :

I'm trying KDE->System Settings->Printers->Add Printer/Class->Network Printer (TCP)->192.168.1.1:9100->Printer Model selection-> OJ5600 not in the list...

"hp-setup -i 192.168.1.1" asks for the connection type, when I select Network, it says 'No devices found'.

Please note that this is not a Network printer, but a USB one, connected to a router which offers standard socket TCP printing to its USB port.

Revision history for this message
zity (zdevai) wrote :

Hm. Configuring through the CUPS webinterface works (localhost:631).
I've specified the URI (socket://192.168.1.1:9100), selected HP, and there are a lot more models selectable (inclusive the OJ5600) than in the KDE printer setup.

Seems like the KDE printer setup app doesn't fetch the device list from CUPS correctly.

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

Sorry HPLIP only supports usb, parallel, and jetdirect network devices. Although your router may have the ability to share a usb network printer unless it's a jetdirect device or jetdirect enabled device HPLIP will not work correctly with it, is unsupported, and we don't test these devices.

You could look over this page: http://hplip.sourceforge.net/troubleshooting/network.html

and be sure the correct ports are open. Although more than likely this wont help..

Sorry!

Aaron

Revision history for this message
Aaron Albright (albrigha-deactivatedaccount) wrote :

Unsupported feature (using third party device to share usb printer through network device.)

Changed in hplip:
status: New → Invalid
Revision history for this message
zity (zdevai) wrote :

Sorry, but you seem to misunderstand the problem.
The printer is working fine even through the network (once configured through CUPS).

The main problem is, that the kde printer setup is not showing all the device models that are available through CUPS.
Even if i select 'Local printer', there are not all models available.

(The model names also differ: KDE shows 'Officejet xxxx', CUPS shows 'HP OfficeJet xxxx Foomatic/hpijs, hpijs 2.8.2' (as it used to be in Gutsy as well))

Changed in hplip:
assignee: nobody → jr
importance: Undecided → High
status: Invalid → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

zity, the problem you talk about was already reported by someone else (I do not remember the bug number/title, Riddell, can you help here?) and was closed as fixed.

The problem is that HPLIP switched from Foomatic to CUPS DDK for on-the-fly generation of PPDs. For printer setup tools with native CUPS interface for listing of available PPDs (which do "lpinfo -m" or the equivalent IPP request, like system-config-printer or the CUPS web interface) this does not matter, but for the KDE Printing Manager it is a problem. Maintainership for this tool stopped in CUPS 1.1.x times and so it still works by directly accessing ready-made PPD files and the Foomatic XML database. This way it does not list on-the-fly-generated PPDs done with non-Foomatic PPD generators, like the PPDs of the new HPLIP.

AFAIR the problem was fixed by taking hpijs-ppds into the seeds of Kubuntu. Riddell, am I correct with this? Or was it solved by switching to system-config-printer-kde?

Riddell, please close this bug as a duplicate if appropriate.

Revision history for this message
zity (zdevai) wrote :

Yes, you're right.
Seems like this is a duplicate of Bug #209220.
That bug says fix released on 04/19, but it's still not OK here.

Hpijs-ppds is installed, the HP ppd-s are in /usr/share/ppd/hpijs/, but kdeprint doesn't seem to care about them.

Revision history for this message
Ran.Rutenberg (ran-rutenberg) wrote :

I've also encountered the same problem on a newly installed Hardy.

Revision history for this message
Harald Sitter (apachelogger) wrote :

The configuration dialog shows both HP and Hewlett-Packard IIRC, the driver should be listed in one of them (eventually not both).
Please confirm.

Changed in kdebase:
status: Confirmed → Incomplete
Revision history for this message
Ran.Rutenberg (ran-rutenberg) wrote :

I'm afraid you're mistaken. As the attached screenshot shows, the only relevant entry is HP (there isn't a separate entry for Hewlett-Packard). The OfficeJet 5600 does not show up when HP is selected.

Revision history for this message
Harald Sitter (apachelogger) wrote :

I think the storage path of the driver file just changed to somewhere the printer database doesn't expect it to be.
This bug is a won't fix however. We ship the HP Toolbox for HP Printer configuration and management _by default_ which should work just fine. A fix for the KDEPrint system would be only usable for KDE 3, as the complete printing implementation was/and still is being changed in KDE 4.
So in order to save the Kubuntu team work of fixing an issue which is only half and issue in older releases anyway, I'd like to just advise to use the official HP tool.

Changed in kdebase:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.