Package: sane-utils
Version: 1.0.22-6
I can't get saned to work, and I think the behaviour is buggish.
First, let's see a description of three situations.
(1) Here is what happens on newton :
root@newton:/etc/sane.d# saned -d
[saned] main: starting debug mode (level 2)
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.22 starting up
[saned] do_bindings: [0] bind failed: Address already in use
[saned] check_host: access by remote host: ::ffff:192.168.0.7
[saned] init: access granted to jpuydt@::ffff:192.168.0.7
[saned] bailing out, waiting for children...
[saned] bail_out: all children exited
and on the box 192.168.0.7, simple-scan which made the request, has worked.
(2) Now, here is a similar situation on newton :
root@newton:/etc/sane.d# saned -d
[saned] main: starting debug mode (level 2)
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.22 starting up
[saned] do_bindings: [0] bind failed: Address already in use
[saned] check_host: access by remote host: ::ffff:127.0.0.1
[saned] init: access granted to saned-user@::ffff:127.0.0.1
[saned] bailing out, waiting for children...
[saned] bail_out: all children exited
and on localhost, I am still 'jpuydt' though the log says 'saned-user',
and simple-scan says :
** (simple-scan:10735): WARNING **: Unable to get open device: Access to
resource has been denied
(3) Finally, on newton :
root@newton:/etc/sane.d# saned -d
[saned] main: starting debug mode (level 2)
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.22 starting up
[saned] do_bindings: [0] bind failed: Address already in use
[saned] check_host: access by remote host: ::ffff:127.0.0.1
[saned] init: access granted to saned-user@::ffff:127.0.0.1
and on localhost, "scanimage > image.pnm" worked!
Now, why do I think the bug is in saned and not in simple-scan?
First, simple-scan is the same version on both systems (both
debian/unstable with amd64 port), so the fact that it works on one and
not the other makes me think the server is to blame.
Second, I configured saned to run standalone and accept connections from
the local network with the following in saned.conf :
::ffff:192.168.0.1/29
::ffff:127.0.0.1
but still, I have to run "saned -d" as root from command line or
everyone (both machines and both scanimage and simple-scan) fails with
"Access to resource has been denied".
It did work perfectly some months ago, but I'm unable to pinpoint
exactly when things started to fail (I didn't scan from june to
september... approximately).
I'd gladly make more tests and provide more information to get that
strange matter settled...
Snark on #gnome-hackers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
