simple-scan on Ubuntu 18.04 does not find wireless scanner

[Dave Goldsbrough]

Scanner is combined with all-in-one device CANON TS8000 series.
Scangearmp is able to find scanner and scan the document.

Both simple-scan and xsane fails to detect scanner.

apt-cache policy simple-scan
simple-scan:
  Installed: 3.28.0-0ubuntu1
  Candidate: 3.28.0-0ubuntu1
  Version table:
 *** 3.28.0-0ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

From the logs app I notice this when using simple-sacan:-
io/hpmud/model.c 532: no on_ts8000_series attributes found in /usr/share/hplip/data/models/models.dat

The exact same but with 543 instead of 532 and then the exact same log when using x-sane

They are mentioned in the "Security" logs and "Applications" logs

[Smittie (smittie)]

Ubuntu 18.04 LTS clean install
SANE & XSANE latest versions as of 05Jun2020

Simple Scan cannot find the Canon MF731C/733C multi-function printer/copier/scanner.
The same computer prints to the Canon MF731C/733C without issue.

If I make an entry in pixma.conf specific to the MF731C/733C, XSANE says it cannot read the MAC address and then that is cannot read the make and model.

smittie@ranchhacks-1:~$ xsane
[bjnp] udp_command: ERROR - no data received (timeout = 5000)
[bjnp] bjnp_init_device_structure: Cannot read mac address, skipping this scanner
[bjnp] udp_command: ERROR - no data received (timeout = 5000)
[bjnp] add_scanner: ERROR - Cannot read scanner make & model: bjnp://192.168.30.18:8612/timeout=5000
s

avahi-discover can see the scanner including manufacturer and model when it does the _scanner._tcp scan.

Service data for service 'RanchHacks-Printer' of type '_scanner._tcp' in domain 'local' on 2.0:
 Host RanchHacks-Printer.local (192.168.30.18), port 8610, TXT data: ['scannerAvailable=1', 'mdl=MF731C/733C', 'mfg=Canon', 'UUID=f80d60ea4433', 'ty=Canon MF731C/733C', 'adminurl=http://RanchHacks-Printer.local:80/airprint.html', 'note=', 'txtvers=1']

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.