gnome-cups-manager does not accept HPLIP printer setup

Giving back bug, I don't have an hplip printer to test

please recheck after a dist-upgrade to dapper 20060414, removal and reinstallation of the printer, or please recheck with a current daily live CD (20060415)

Used live CD 20060414, there is no 20060415. My LAN printer is HP DeskJet 5850 with static IP 192.168.1.63. It is not detected by Gnome Printing Manager (GPM) when checking Detect LAN Printers in the Global Settings. Installing manually in GPM is still not possible, as the option AppSocket/HPJetDirect is not available; in Breezy I was able to circumvent GPM by installing the printer in localhost:631 as AppSocket/HPJetDirect with URI socket://192.168.1.63:9100, then choosing either HP or HPLIP as manufacturer, and DeskJet 5850 among the hpijs drivers.

In Dapper, only the HPJetDirect option is present, and it is not the same as the AppSocket/HPJetDirect option.
I have tried as URI all sorts of combinations: the IP with and without socket:// prefix, and with and without :9100 postfix. I've also tried, with the CUPS (IPP) printer option the URI with ipp:// and http:// prefixes and :9100 postfixes.

Impossible to say if one of these works, because the hpijs drivers are not present in Dapper either; I've used DeskJet series and New DeskJet series.

Anyway, whatever I do, there is no new printer appearing. I've not tried to circumvent GPM (as I did in Breezy), because the way to do that in /etc/cups/cupsd.conf has been made much more difficult and opaque in Dapper... we have regression here, not progress.

I have been able to successfully install an AppSocket/HPJetDirect printer with Gnome-Cups-Manager using Dapper AMD64 Live-CD Flight 6 (dated 31 March 2006). I selected type HPJetDirect (obviously), typed in the IP of the printer under URI (without socket:// prefix), chose HP (HPLIP) and the driver for HP DeskJet 5850, and everything was OK. Printed a correct Ubuntu test page.

Now , why would the live-CD 386 of 20060414 mess all of this up again, I wonder...

It worked in Dapper Flight 6 (see previous message), but fails again in Dapper Beta. This is what I did in Dapper Beta:
0. Hit New Printer.
1. Select Network Printer, type HP JetDirect.
2. URI: 192.168.1.63 (Port: 9100)
3. Manufacturer: HP
    Model: DeskJet 5850
    Recommended driver: hpijs (from HPLIP)
4. When hitting Apply button, nothing happens.
5. When trying to repeat the installation by hitting New Printer, the window freezes with a message: "...application quit suddenly...".

Again, the very same procedure was successful in Flight 6...

It appears that this bug can be closed.

I installed Dapper Beta2 today (7 May 2006) and did an apt-get update. My network printer installs OK: as an HP JetDirect printer, using as URI its LAN address (192.168.1.63) without any prefix (like socket:// or hp:/), and chose the HP DeskJet 5850 recommended hpijs driver. The test page is just perfect.

Now hoping that g-c-m isn't messed up between now and final Dapper release...

Marking as fixed then, feel free to reopen if you get the issue again

Henk Koster, could you check which URI type was configured, please?

You can check it through the CUPS webinterface (http://localhost:631 and then Printers).

Alternatively, in the past if you launched gnome-cups-manager from a terminal, it used to show the URI of each printer, something similar to:

** (gnome-cups-manager:17640): WARNING **: connect = 'socket://192.168.0.1:9100'

I just entered the regular IP address of the printer (in my case 192.168.1.63), without any prefix like socket:// or hp:/net/deskjet_5800?ip=192.168.1.63. The port 9100 was already indicated.

This printer now works for me, but -- admittedly -- it is still not the HPLIP setup; so commands like hp-info and hp-levels do not work.

Another computer is located next to the same printer and connected to it via USB. I've been able to connect it the HPLIP way following the instructions in the wiki HpPrinterInstallationAndMaintenance, first in Breezy and now also in Dapper (Beta2) plus updates.

I thought we might as well cose this bug as there is already another similar one still open (yours, I believe).

Henk, I understand how you did it. I would like to know how CUPS has been configured by g-c-m. Please, open a terminal, write "gnome-cups-manager 2>&1 | grep connect", then right-click in the printer and in Properties.

Could you copy the output of the terminal and paste it here? Thanks.

You may do it also for the USB printer, so we can check the difference.

Configured as network printer in Dapper:

** (gnome-cups-view:4956): WARNING **: connect = 'socket://192.168.1.63:9100'

and configured as USB printer in Breezy:

** (gnome-cups-manager:26208): WARNING **: connect = 'hp:/usb/deskjet_5800?serial=MY3951N10RTQ'

In both cases perfect test page out-of-the-box.

Many thanks! This confirms my guess that g-c-m was just doing the same as before. The only difference is that now it hides the URI.

I am glad that your printer works, however, that had nothing to do with changes in gnome-cups-manager. Surely, a new version of CUPS or of some of the PPD's packages has fixed the issue with your particular printer.

That, however, is not the point of the bug report. The point is that HPLIP printers (those starting with "hp:/" ) cannot be configured from gnome-cups-manager. So I reopen the bug. Maybe this should be considered a feature request...

Aren't upstream links transferred when a bug is marked as a duplicate of another?
Should I transfer manually the upstream bug report from bug 25630 to this one?

Added upstream gnome bug watch.

I am not sure if I this adds any useful information, but I seem to be running across the exact same problem with my HP OfficeJet K80. I am running the latest Dapper from the main repositories. I am able to print test pages fine from the localhost:631 setup, and I am also able to print from KDE apps (e.g., kpdf), but I can't seem to print normally from Gnome (e.g., gpdf). I'm pretty sure that it's due to the same issue. As metioned, I am unable to add the URI for my printer in g-c-m because it keeps on prepending ipp:// .

We have changed the default print management system in Ubuntu from gnome-cups-manager to system-config-printer because g-c-m is no longer maintained. Please open a new bug against system-config-printer if you still have this problem with Gutsy or Hardy. Thanks!

jochoa@(none):~$ gnome-cups-manager 2>&1 | grep connect
** (gnome-cups-manager:6813): WARNING **: connect = 'smb://lxproimi/biblioteca/hp1020'
Did anybody know about this g-c-m printer problem? I installed g-c-m again because the hal-system-printer does not work on Ubuntu Gusty
I will very appreciate any comments?