On Wed 31 Jul 2019 at 00:35:51 +0200, Pierre Frenkiel wrote: > On Tue, 30 Jul 2019, Brian wrote: > > > The outputs of 'scanimage -L' from each machine were asked for. They > > provide information you have not given. > > > > -- > > Brian. > > > hi brian, > I thought that they don't provide more information than what I wrote > previously,
The outputs provide the URIs seen by scanimage (and xsane), how the URIs have been formed and the names of the devices. All essential information. > (on my desktop(buster) and my laptop (amd64/stretch), both devices are > listed. > on my wife's laptop(amd64/stretch), only the laserjet) Being listed is not sufficient; a URI also has to be correct. > but if you want them, here they are > > my desktop: > device `hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41' is a > Hewlett-Packard HP_LaserJet_MFP_M227-M231 all-in-one > device `hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false' is > a Hewlett-Packard laserjet_mfp_m227-m231 all-in-one I think that scanimage (and xsane) use the first offered URI. Test: scanimage -d hpaio:/net/HP_LaserJet_MFP_M227-M231?ip=192.168.1.41 > out.dat scanimage -d hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false > out.dat > device `hpaio:/net/envy_photo_7100_series?ip=192.168.1.200&queue=false' is > a Hewlett-Packard envy_photo_7100_series all-in-one > > my laptop: > device `hpaio:/net/laserjet_mfp_m227-m231?ip=192.168.1.41&queue=false' is > a Hewlett-Packard laserjet_mfp_m227-m231 all-in-one > device `hpaio:/net/envy_photo_7100_series?ip=192.168.1.200&queue=false' is > a Hewlett-Packard envy_photo_7100_series all-in-one > > my wife's laptop: > device `hpaio:/net/HP_LaserJet_MFP_M227-M231?zc=NPIBDD3AA' is a > Hewlett-Packard HP_LaserJet_MFP_M227-M231 all-in-one > > I would be glad if that helps you to explain what happens. > I specially don't understand why she doesn't see the envy. The URIs with "queue=false" indicate that your desktop and laptop have discovered the MFDs from their DNS-SD (Bonjour) broadcasts. Your wife's laptop does not do such a discovery. This implies that there is some issue with avahi-daemon on this machine. What do you get for avahi-browse -rt _uscan._tcp and avahi-browse -rt _ipp._tcp avahi-browse is in the avahi-utils package. -- Brian.