Bug 583909

Have updated system-config-printer:
http://koji.fedoraproject.org/koji/buildinfo?buildID=167006

Disabled firewall:

]# python /usr/share/system-config-printer/check-device-ids.py

If you have not already done so, you may get more results
by temporarily disabling your firewall (or by allowing
incoming UDP packets on port 161).

Examining connected devices
Sending SNMP request to 192.168.0.3 for device-id
Skipping socket://192.168.0.3, insufficient data
No Device IDs available.

Printer is using hplip

What does 'lpinfo -l -v' say, and also 'lpstat -s'?

# lpinfo -l -v
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = scsi
        class = direct
        info = SCSI Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = https
        class = network
        info = Internet Printing Protocol (https)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = hp
        class = direct
        info = HP Printer (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 



# lpstat -s
system default destination: HP-Color-LaserJet-2605
device for HP-Color-LaserJet-2605: hp:/net/HP_Color_LaserJet_2605dn?ip=192.168.0.3

Aside: F14\Rawhide has the following with system-config-printer-1.2.1-1.fc14.x86_64

probably for the same reason as above.

dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._printer._tcp.local/

but wants to install: HP Color Laserjet 2500 -CUPS+Gutenberg v5.25 simplified reccomended.

Did not offer to install hplip, after query.

(In reply to comment #4)
> Aside: F14\Rawhide has the following with
> system-config-printer-1.2.1-1.fc14.x86_64
> 
> probably for the same reason as above.
> 
> dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._printer._tcp.local/

I'm not sure what command you used to get that, but it does tell me that the printer supports DNS-SD.  Good.

OK, this is a good opportunity to test a change I made in CUPS recently.  The CUPS dnssd backend will try to report a Device ID even if the remote printer does not, by making it up from other bits and pieces of information it has.  This is fine as a "best attempt", but is no good for collecting the actual Device IDs and so check-device-ids ignores those.

I changed cups-1.4.3-6.fc13 so that it embeds a special field indicating whether this is a correct and true Device ID or whether it has been fabricated.

So, with cups-1.4.3-6.fc13 (or .fc14), and with the firewall disabled (or packets on UDP port 5353 allowed in), what do you get from this command?:

lpinfo --include-schemes=dnssd -l -v

I'm hoping to see something like this:

Device: uri = dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._printer._tcp.local/
        class = network
        info = HP Color LaserJet 2605
        make-and-model = HP Color LaserJet 2605
        device-id = MFG:Hewlett-Packard;MDL:HP Color LaserJet 2605;CMD:POSTSCRIPT,...;FZY:0;
        location = 192.168.0.3

updated cups cup-libs f13
rebooted

# lpinfo --include-schemes=dnssd -l -v
Device: uri = dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._pdl-datastream._tcp.local/
        class = network
        info = HP Color LaserJet 2605dn (E10105)
        make-and-model = HP HP Color LaserJet 2605dn
        device-id = MFG:HP;MDL:Color LaserJet 2605dn;FZY:1;
        location = 
Device: uri = dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._printer._tcp.local/
        class = network
        info = HP Color LaserJet 2605dn (E10105)
        make-and-model = HP HP Color LaserJet 2605dn
        device-id = MFG:HP;MDL:Color LaserJet 2605dn;FZY:1;
        location =

(In reply to comment #5)
> (In reply to comment #4)
> > Aside: F14\Rawhide has the following with
> > system-config-printer-1.2.1-1.fc14.x86_64
> > 
> > probably for the same reason as above.
> > 
> > dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._printer._tcp.local/
> 
> I'm not sure what command you used to get that, but it does tell me that the
> printer supports DNS-SD.  Good.
> 
was alread installed on F14
$ rpm -qa cups\*
cups-libs-1.4.3-6.fc14.x86_64
cups-pk-helper-0.0.4-13.fc14.x86_64
cups-1.4.3-6.fc14.x86_64



> OK, this is a good opportunity to test a change I made in CUPS recently.  The
> CUPS dnssd backend will try to report a Device ID even if the remote printer
> does not, by making it up from other bits and pieces of information it has. 
> This is fine as a "best attempt", but is no good for collecting the actual
> Device IDs and so check-device-ids ignores those.
> 
> I changed cups-1.4.3-6.fc13 so that it embeds a special field indicating
> whether this is a correct and true Device ID or whether it has been fabricated.
> 
> So, with cups-1.4.3-6.fc13 (or .fc14), and with the firewall disabled (or
> packets on UDP port 5353 allowed in), what do you get from this command?:
> 
> lpinfo --include-schemes=dnssd -l -v
> 
> I'm hoping to see something like this:
> 
> Device: uri =
> dnssd://HP%20Color%20LaserJet%202605dn%20(E10105)._printer._tcp.local/
>         class = network
>         info = HP Color LaserJet 2605
>         make-and-model = HP Color LaserJet 2605
>         device-id = MFG:Hewlett-Packard;MDL:HP Color LaserJet
> 2605;CMD:POSTSCRIPT,...;FZY:0;
>         location = 192.168.0.3    

Shows this in F14 as in F13, but still won't prompt for hplip install (hplip was installe manually with yum in f13 box)

OK, the printer doesn't offer its Device ID over DNS-SD unfortunately ("FZY:1;" here means the CUPS dnssd backend just made it up based on the make-and-model information).

One last thing: can you try using the f14 package to do this?:

/usr/lib/cups/backend/snmp 192.168.0.3

(In reply to comment #8)
> OK, the printer doesn't offer its Device ID over DNS-SD unfortunately ("FZY:1;"
> here means the CUPS dnssd backend just made it up based on the make-and-model
> information).
> 
> One last thing: can you try using the f14 package to do this?:
> 
> /usr/lib/cups/backend/snmp 192.168.0.3    

# /usr/lib/cups/backend/snmp 192.168.0.3
network socket://192.168.0.3 "HP Color LaserJet 2605dn" "HP Color LaserJet 2605dn" "MFG:Hewlett-Packard;CMD:PJL,PML,POSTSCRIPT,PCLXL,PCL;MDL:HP Color LaserJet 2605dn;CLS:PRINTER;DES:Hewlett-Packard Color LaserJet 2605dn;MEM:MEM=54MB;COMMENT:RES=1200x1;" "Boise, ID, USA"

Brilliant.  This printer responds to the HP-specific SNMP OID.

Fetching driver list
└── HP Color LaserJet 2605dn (user-specified): MFG:Hewlett-Packard;MDL:HP Color LaserJet 2605dn;CMD:PJL,PML,POSTSCRIPT,PCLXL,PCL;
    (No drivers)

Hmm, the check-device-ids script didn't spot any drivers at all, but there certainly are some:

foomatic:HP-Color_LaserJet_2605-Postscript.ppd HP Color LaserJet 2605 Foomatic/Postscript

lsb/usr/HP/hp-color_laserjet_2605dn-ps.ppd.gz HP Color LaserJet 2605 Postscript

Let's say *this* bug report is for foomatic-db.  I'll file another for HPLIP.

HPLIP one is bug #583953.

Committed upstream.

foomatic-db-4.0-15.20100204.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/foomatic-db-4.0-15.20100204.fc13

Works,

found and installed correct ppd.

foomatic-db-4.0-15.20100204.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update foomatic-db'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/foomatic-db-4.0-15.20100204.fc13

foomatic-db-4.0-17.20100204.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update foomatic-db'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/foomatic-db-4.0-17.20100204.fc13

foomatic-db-4.0-17.20100204.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.