[sane-devel] 03f0:4f11 sane daemon network scanning not working systemd[1]: Got more than one socket.

[Christopher M. Penalver]

Hello. I'm following up on my bug report:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442956
https://alioth.debian.org/tracker/index.php?func=detail&aid=315043&group_id=30186&atid=410366

Unfortunately, sane daemon network scanning it isn't working at all in
the two most recent releases of Ubuntu. Following
https://help.ubuntu.com/community/SaneDaemonTutorial worked in Trusty
(sane-utils 1.0.23) with my HP OfficeJet 5610v All-in-one plugged into
a USB 2.0 port.

However, with sane-utils 1.0.24, network scanning does not work. For
example, with a Windows 8.1 client using SaneTwain 1.3.6, it used to
work. Now it pops up a window:
Error
No devices found on backend.

However, in the Device drop down it notes:
hpaio:/usb/Officejet_5600_series?serial=XXXXXXXXXXXXXX

Ubuntu 15.04 client with either xsane or simple-scan doesn't find
anything. Running the following from a terminal results in either a
crash or no SANE devices found as per
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442960 :
scanimage 192.168.1.15
scanimage: no SANE devices found

scanimage 192.168.1.15
*** Error in `scanimage': double free or corruption (!prev):
0x00007f5a939fff10 ***

The scanner works fine locally on the server via simple-scan or xsane.

The issue happens in both upstart and systemd. Hence, it appears to be
a bug in sane, versus init system, or configuration (i.e. user error).

In Vivid, on the server:
scanimage --device net:localhost
scanimage: open of device net:localhost failed: Error during device I/O

/lib/systemd/system/saned.service :
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442956/+attachment/4383859/+files/saned.service

/lib/systemd/system/saned.socket :
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442956/+attachment/4383860/+files/saned.socket

sudo systemctl restart saned.service && sudo systemctl status saned.service -l
● saned.service - Scanner Service
   Loaded: loaded (/lib/systemd/system/saned.service; static; vendor
preset: enabled)
   Active: inactive (dead)

Apr 22 19:40:24 pc systemd[1]: Unit saned.service entered failed state.
Apr 22 19:40:24 pc systemd[1]: saned.service failed.
Apr 22 19:40:24 pc systemd[1]: Starting Scanner Service...
Apr 22 19:41:31 pc systemd[1]: Started Scanner Service.
Apr 22 19:41:31 pc systemd[1]: Starting Scanner Service...
Apr 22 19:41:31 pc saned[2545]: saned (AF-indep+IPv6) from
sane-backends 1.0.24 starting up
Apr 22 19:41:47 pc systemd[1]: Started Scanner Service.
Apr 22 19:41:47 pc systemd[1]: Starting Scanner Service...
Apr 22 19:41:47 pc saned[2574]: saned (AF-indep+IPv6) from
sane-backends 1.0.24 starting up
Apr 22 19:41:47 pc saned[2574]: check_host: access by remote host: localhost

    journalctl -xe
    Apr 22 20:04:41 pc sudo[2669]: pam_unix(sudo:session): session
opened for user root by USERNAME(uid=0)
    Apr 22 20:04:41 pc polkitd(authority=local)[979]: Registered
Authentication Agent for unix-process:2670:337819 (
    Apr 22 20:04:41 pc systemd[1]: Got more than one socket.
    Apr 22 20:04:41 pc systemd[1]: saned.service failed to run 'start'
task: Invalid argument
    Apr 22 20:04:41 pc systemd[1]: Failed to start Scanner Service.
    -- Subject: Unit saned.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit saned.service has failed.
    --
    -- The result is failed.
    Apr 22 20:04:41 pc systemd[1]: saned.service failed.
    Apr 22 20:04:41 pc systemd[1]: Starting Scanner Service...
    -- Subject: Unit saned.service has begun start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    --
    -- Unit saned.service has begun starting up.
    Apr 22 20:04:41 pc sudo[2669]: pam_unix(sudo:session): session
closed for user root

I've tried seeking support for this issue multiple times via the #sane
IRC channel but it's been crickets unfortunately.

Anything you could do to help is greatly appreciated.

Christopher M. Penalver
E-Mail: christopher.m.penalver at gmail.com