[sane-devel] SCX-3405W scans with usb but not when shared from Linux Mint

Ralph Little skelband at gmail.com
Wed May 20 15:53:33 BST 2020


Hi,

On 2020-05-19 12:39 p.m., vicki at thepenguin.org wrote:

> Unfortunately, it doesn't like the option -e so run without it:
>
> desktop:~# SANE_DEBUG_XEROX_MFP=50 saned -d50
> [saned] read_config: searching for config file
> [saned] read_config: done reading config
> [saned] saned (AF-indep+IPv6) from sane-backends 1.0.27 starting up
> [saned] do_bindings: trying to get port for service "sane-port" 
> (getaddrinfo)
> [saned] do_bindings: [1] socket () using IPv6
> [saned] do_bindings: [1] setsockopt ()
> [saned] do_bindings: [1] bind () to port 6566
> [saned] do_bindings: [1] listen ()
> [saned] do_bindings: [0] socket () using IPv4
> [saned] do_bindings: [0] setsockopt ()
> [saned] do_bindings: [0] bind () to port 6566
> [saned] do_bindings: [0] bind failed: Address already in use
> [saned] run_standalone: spawning Avahi process
> [saned] run_standalone: waiting for control connection
> [saned] saned_avahi_callback: AVAHI_CLIENT_S_RUNNING
> [saned] saned_create_avahi_services: adding service 'saned'
> [saned] saned_avahi_group_callback: service 'saned' successfully 
> established
> [saned] handle_connection: processing client connection
> [saned] check_host: detected an IPv4-mapped address
> [saned] check_host: access by remote host: ::ffff:192.168.0.11
> [saned] check_host: remote host is not IN_LOOPBACK nor IN6_LOOPBACK
> [saned] check_host: local hostname: vicki-desktop
> [saned] check_host: local hostname(s) (from DNS): vicki-desktop
> [saned] check_host: local hostname(s) (from DNS): (null)
> [saned] check_host: local hostname(s) (from DNS): (null)
> [saned] check_host: remote host doesn't have same addr as local
> [saned] check_host: opening config file: /etc/hosts.equiv
> [saned] check_host: can't open config file: /etc/hosts.equiv (No such 
> file or directory)
> [saned] check_host: opening config file: saned.conf
> [saned] check_host: config file line: `# saned.conf'
> [saned] check_host: config file line: `# Configuration for the saned 
> daemon'
> [saned] check_host: config file line: `'
> [saned] check_host: config file line: `## Daemon options'
> [saned] check_host: config file line: `# Port range for the data 
> connection. Choose a range inside [1024 - 65535].'
> [saned] check_host: config file line: `# Avoid specifying too large a 
> range, for performance reasons.'
> [saned] check_host: config file line: `#'
> [saned] check_host: config file line: `# ONLY use this if your saned 
> server is sitting behind a firewall. If your'
> [saned] check_host: config file line: `# firewall is a Linux machine, 
> we strongly recommend using the'
> [saned] check_host: config file line: `# Netfilter nf_conntrack_sane 
> connection tracking module instead.'
> [saned] check_host: config file line: `#'
> [saned] check_host: config file line: `# data_portrange = 10000 - 10100'
> [saned] check_host: config file line: `'
> [saned] check_host: config file line: `'
> [saned] check_host: config file line: `## Access list'
> [saned] check_host: config file line: `# A list of host names, IP 
> addresses or IP subnets (CIDR notation) that'
> [saned] check_host: config file line: `# are permitted to use local 
> SANE devices. IPv6 addresses must be enclosed'
> [saned] check_host: config file line: `# in brackets, and should 
> always be specified in their compressed form.'
> [saned] check_host: config file line: `#'
> [saned] check_host: config file line: `# The hostname matching is not 
> case-sensitive.'
> [saned] check_host: config file line: `'
> [saned] check_host: config file line: `#scan-client.somedomain.firm'
> [saned] check_host: config file line: `#192.168.0.1'
> [saned] check_host: config file line: `#192.168.0.1/29'
> [saned] check_host: config file line: `#[2001:db8:185e::42:12]'
> [saned] check_host: config file line: `#[2001:db8:185e::42:12]/64'
> [saned] check_host: config file line: `'
> [saned] check_host: config file line: `192.168.0.11'
> [saned] check_host: access granted from IP address ::ffff:192.168.0.11 
> (IPv4-mapped)
> [saned] init: access granted
> [saned] init: access granted to vicki@::ffff:192.168.0.11
> [saned] process_request: waiting for request
> [saned] process_request: got request 1
> [sanei_debug] Setting debug level of xerox_mfp to 50.
> [xerox_mfp] sane_init: Xerox backend (build 13), version != null, 
> authorize != null
> [xerox_mfp] sane_xerox_mfp_get_devices: 0x7ffd9e6d0c10, 1
> [xerox_mfp] list_one_device: libusb:010:002
> [xerox_mfp] usb_dev_open: open 0x5642a807f960
> [xerox_mfp] :: dev_command(INQUIRY[0x12], 70)
> [xerox_mfp] usb_dev_request: sanei_usb_read_bulk: Error during device I/O
> [xerox_mfp] dev_command: dev_request: Error during device I/O
> [xerox_mfp] usb_dev_close: closing dev 0x5642a807f960
> [xerox_mfp] list_one_device: dev_inquiry(libusb:010:002): Error during 
> device I/O
> [saned] process_request: waiting for request
> [saned] process_request: got request 10
> [saned] bailing out, waiting for children...
> [saned] bail_out: all children exited
>
> It appears to get part of the way and then gets a device error. Can 
> you provide any insight on that particular error?
>
Thanks for your patience with me BTW. :)

Unfortunately, that error is pretty generic.

The only plausible reasons that I can think of, given that you can scan 
directly from this machine via USB is:

1) Some weird kind of permissions issue. If the user that you are 
running saned as can scan directly, then that is unlikely to be the 
problem here as well.
I don't think that saned run in this mode drops its privileges.

2) Perhaps the device is already open by something else.
Do you have a frontend open on the main machine at all? It might be 
hogging the device.

All I can think of at this point is:

a) Check that there is no sane application running on that device at the 
moment.

b) As a last resort, try running saned as root using sudo, just to check 
out permissions.

Failing that, I will have a think.

===============
One other thing that you can do is upgrade to Rolf Bensch's excellent 
PPA (if that is possible for your setup) to get the latest and greatest 
on both machines.
There has been a tremendous amount of activity in SANE since 1.0.27:

https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git - for the 
cutting edge
https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-release - for the 
latest release.

Cheers,
Ralph



More information about the sane-devel mailing list