Comment 4 for bug 1797501

Hi Brian,

Given your mdns responses, it looks like the query on _scanner._tcp would fail too, as the first three bytes of the "ty=" TXT record are skipped, giving "Y 4500 series". Do you see any failure in the logs from that?

However, your _uscan._tcp response would be OK; as it has this:

   "ty=HP ENVY 4500 series"

so that +3 skips over the "HP " characters; which would match the entry in models.dat:

  [envy_4500_series]

I'm assuming that the _uscan._tcp response is the one that allows the mdns discovery code to pick up your scanner.

I don't see any responses for the _uscan service from my device, only _scanner.

  [jk@pecola ~]$ avahi-browse -tr _uscan._tcp
  [jk@pecola ~]$ avahi-browse -tr _scanner._tcp
  + br0 IPv4 Officejet 6500 E710n-z [55F97F] _scanner._tcp local
  = br0 IPv4 Officejet 6500 E710n-z [55F97F] _scanner._tcp local
     hostname = [officejet.local]
     address = [192.168.0.155]
     port = [9500]
     txt = ["feeder=T" "flatbed=T" "button=T" "note=" "adminurl=http://officejet.local." "mdl=Officejet 6500 E710n-z" "mfg=HP" "ty=Officejet 6500 E710n-z" "txtvers=1"]