[net] sane_open: net_open
[net] sane_open: remote open failed
scanimage: open of device net:192.168.0.102:pixma:04A91709 failed: Access to
resource has been denied
[net] sane_exit: exiting
What about the xinet (or inet ?) configuration you are using on the server:
is the user/group used for saned a
Just found out this is related to a nasty bug (#588300) in udev. Adding
the "saned" user to the "lp" seems to be a valid work-around for now,
but it sucks to have to do this. Hopefully the bug will be squashed
soon.
On Wed, 28 Jul 2010 07:20:14 -0500,
Seb wrote:
> On Wed, 28 Jul 2010 14:02:1
On Wed, 28 Jul 2010 14:02:10 +0200,
Nicolas Martin wrote:
> [net] sane_open: net_open [net] sane_open: remote open failed
> scanimage: open of device net:192.168.0.102:pixma:04A91709 failed:
> Access to resource has been denied [net] sane_exit: exiting
> What about the xinet (or inet ?) configur
[update]
I changed the clients' /etc/sane.d/net.conf to point exclusively to the
IP address of the SANE server:
192.168.0.102
and now the clients detect the scanner, but cannot use it:
------
$ scanimage -L
device `net:192.168
Hi,
My partner is about to strangle me because she can no longer scan on our
Canon Pixma MP150. Following updates to Debian sid SANE packages
several weeks ago, this scanner is only seen on the machine with the
server. We have 3 computers in a home network (on a router):
192.168.0.100
192.168.0
