Hi,
On 2020-05-19 12:07 p.m., [email protected] wrote:
home-E7250:~$ SANE_DEBUG_NET=50 SANE_NET_HOSTS=192.168.0.15 scanimage -L
[sanei_debug] Setting debug level of net to 50.
[net] sane_init: authorize != null, version_code != null
[net] sane_init: SANE net backend version 1.0.14 (AF-indep+IPv6) from
sane-backends 1.0.27
[net] sane_init: Client has little endian byte order
[net] sane_init: searching for config file
[net] sane_init: trying to add 192.168.0.15
[net] add_device: adding backend 192.168.0.15
[net] add_device: backend 192.168.0.15 added
[net] sane_init: done reading config
[net] sane_init: evaluating environment variable SANE_NET_HOSTS
[net] sane_init: trying to add 192.168.0.15
[net] add_device: adding backend 192.168.0.15
[net] add_device: already in list
[net] sane_init: evaluating environment variable SANE_NET_TIMEOUT
[net] sane_init: done
[net] sane_get_devices: local_only = 0
[net] connect_dev: trying to connect to 192.168.0.15
[net] net_avahi_browse_callback: CACHE_EXHAUSTED
[net] connect_dev: [0] connection succeeded (IPv4)
[net] connect_dev: sanei_w_init
[net] connect_dev: net_init (user=vicki, local version=1.0.3)
[net] connect_dev: freeing init reply (status=Success, remote version=1.0.3)
[net] connect_dev: done
[net] net_avahi_browse_callback: ALL_FOR_NOW
[net] sane_get_devices: finished (0 devices)
No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[net] sane_exit: exiting
[net] net_avahi_cleanup: stopping thread
[net] net_avahi_cleanup: done
[net] sane_exit: closing dev 0x55c0d67b3ca0, ctl=124
[net] sane_exit: finished.
OK, now we're getting somewhere.
Still unsure why the config file entry is not being picked up, but we
can see that the laptop is connecting to your main machine at
192.168.0.15 and it reports no devices.
So the problem is there. I'm thinking it is permissions-related after all.
On the main machine, stop the saned service:
sudo systemctl stopstop saned.socket
Run saned manually, as a user that can access scanners locally there
(probably your login would suffice), capturing the output:
SANE_DEBUG_XEROX_MFP=50 saned -l -d50 -e
... and try to connect again from the laptop.
If it connects, and finds the scanner, see if you can scan something on
the laptop using your favourite frontend.
You might have to set SANE_NET_HOSTS in the environment for the moment.
Cheers,
Ralph
