Hi Henk, you can check out which URI type was used to configure the printers through the CUPS webinterface (http://localhost:631 and then Printers).
Also, if you launch gnome-cups-manager from a terminal, it gives the URI of each printer. Since you used the JetDirect backend, you will see something similar to: ** (gnome-cups-manager:17640): WARNING **: connect = 'socket://192.168.0.1:9100' As said before, one issue is being able to configure the HPLIP backend from gnome-cups-manager and another issue is that the printer actually works (or not) with HPLIP. I guess you are saying that with Dapper Beta2 there is no way to configure a printer to use the HPLIP backed from gnome-cups-manager. That is the relevant part for this bug report. Now, as an off-topic, the reasons why your printer may not work under HPLIP may be: * Your printer is not supported. This does not seem to be the case http://hplip.sourceforge.net/supported_devices/index.html. * Support for your printer is not available in HPLIP's version in Dapper (0.9.8). You may try the latest version HPLIP 0.9.10 from http://sourceforge.net/project/showfiles.php?group_id=149981 (installation instructions available at http://hplip.sourceforge.net/install/step2/ubuntu510.html) * A bug in HPLIP. You should report it to one of the HPLIP mailing lists, or send an email to [EMAIL PROTECTED] (http://hplip.sourceforge.net/faqs.html). I would recommend you include the output of whatever command fails adding the option -ldebug, such as, "hp-info -ldebug". * Another reason...? -- Cannot configure HPLIP network printers in gnome-cups-manager https://launchpad.net/bugs/25630 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
